Reset / Reinstall "App installer"
After upgrading to Windows 10 1809, the App Installers works once again.
Related videos on Youtube
Gene
Updated on September 18, 2022Comments
-
Gene over 1 year
On my Windows 10 Pro machine (1709), double-clicking an
.appxbundle
will start the App Installer but directly show the following error message:The
Apps
event log shows the following entry:Activation for Microsoft.DesktopAppInstaller_8wekyb3d8bbwe!App failed. Error code: The remote procedure call failed.. Activation phase: COM App activation
I removed the installer app (via
Remove-AppxPackage Microsoft.DesktopAppInstaller_1.0.12894.0_x64__8wekyb3d8bbwe
) and installed it again from the Store, but the error still occurs. The error is not related to the AppXBundle being installed (VCLibs will fail as well, the same package can be installed on other machines).Installing bundles via PowerShell or the device portal works as expected.
So how to repair or reset the App Installer on Windows 10 (or further trace the issue down)?
-
magicandre1981 about 6 yearsactivate developer portal and deploy the app from the browser (127.0.0.1 ). does this work?
-
Ramhound about 6 yearsIf you are using a Enterprise version of Windows 10 edit and update your question
-
Gene about 6 years@magicandre1981: Sorry, I should have mentioned that installing bundles via PowerShell (or the portal) works, so this issue is just related to the "App Installer" app. Updated the question.
-
magicandre1981 about 6 yearsI have no idea why this fails. use device portal workaround and try again next month after Microsoft released Windows 10 1803. Maybe the issue is now fixed.
-
-
Gene about 6 yearsThanks Karen. The services are configured as mentioned. The PowerShell command did reinstall the app but the error remains the same.
-
Waka about 6 yearsWhich .appxbundle? was it your customized app? what if it on other windows 10 computer?
-
Gene about 6 yearsAn inhouse app, yes. But it doesn't matter which bundle (VCLibs fail as well). Works well on other computers. And works well via PowerShell. Therefore, I assume the "App Installer" app just fails to start (as stated by the event log message).