Windows 10: The ms-appinstaller protocol has been disabled? Enable it.

​

Enterprise admins can now re-enable the MSIX ms-appinstaller protocol handler that Microsoft earlier disabled after Emotet malware was used by threat actors to exploit the feature to deliver malicious Windows App Installer packages. This post describes how to enable the ms-appinstaller protocol safely again. What is the ms-appinstaller protocol handler? The ms-appinstaller protocol handler (AppX […]

This article The ms-appinstaller protocol has been disabled? Enable it. first appeared on TheWindowsClub.com.

read more...

 

AppInstaller freezes

When I attempt to install via a certain .appinstaller file (https://download.mytobiidynavox.com/Snap/installers/distribute/Snap.WindowsUWP.OEM.appinstaller) after it has already been installed/uninstalled once, I see the status message "Getting the system
ready for install...", but it never progresses from there. I can't check/uncheck the "Launch when ready" checkbox either - appinstaller appears to be frozen.

If I restart my machine, it seems to allow it to work once. But if I uninstall the app and try the .appinstaller again, it freezes again. Event Viewer doesn't have anything interesting for when it freezes. The only event logged is:

"Started deployment AddFromAppInstallerOperation operation on a package with main parameter Snap.WindowsUWP.OEM.appinstaller and Options ForceTargetApplicationShutdownOption and RequestReputationCheck. See Troubleshooting packaging, deployment, and query of Windows apps - Win32 apps | Microsoft Docs for
help diagnosing app deployment issues."

Other .appinstaller files seem to work fine with that process
(such as https://db-msixtest.azurewebsites.net/ContosoExpenses.Package.appinstaller).

 

You'll need a new app to open this ms-appinstaller

We have built an UWP package with VS2017. When we start installing the appx bundle on the user's machine, this error occurs: "You'll need a new app to open this ms-appinstaller". How to solve this problem?

 

Network Protocols Missing

"One of the fixes I had read during the insider program was to almost do what your suggestion was and that was deleting the winsock info in the registry. However, the MS response wasn't to install other info, just reinstall the TCP/IP protocol."

That was attempted here, but TCP/IP did not appear in the protocol list ... at least I did not spot it, so couldn't install it.