Forum Discussion
Solved
The ms-appinstaller protocol has been disabled.
I just found out that users can no longer install my MSIX from my website. This is a WPF application packaged with "Windows Application Packaging Project" (wapproj). When users click the "Get the app...
bvenhaus Thank you for your question. We removed the ms-appinstaller custom scheme due to a security vulnerability. We do intend to bring this back, and are working on it. For now, you can update the link on your website by removing 'ms-appinstaller:?source='
<html> <body> <h1> MyApp Web Page </h1> <a href="http://mywebservice.azureedge.net/HubApp.msix"> Install app package </a> <a href="http://mywebservice.azureedge.net/HubAppBundle.msixbundle"> Install app bundle </a> <a href="http://mywebservice.azureedge.net/HubAppSet.appinstaller"> Install related set </a> </body> </html>
If you have a workaround which is feasible it would be good to know. I doubt a good solution exists.
The workaround is for users to download the XML file and open it. If you need the custom parameters then there's no workaround.
If you don't need custom parameters then it's worth maybe taking a deep breath and looking at the actual UX change. Before:
1. Click the link.
2. Click the yes button in "Open this link in App Installer?"
3. Click Install/Launch in App Installer.
After:
1. Click the link. It downloads.
2. Click the download in the browser. App Installer opens.
3. Click the Launch/Install button.
Same number of clicks. The URL handler _is_ better because it has more features, because the permission to open URLs is remembered per site, because URLs work in more places, because it doesn't clutter the user's downloads folder and so on. So we all hope it'll return. But, for distribution via a web page, the difference isn't that large.
If you don't need custom parameters then it's worth maybe taking a deep breath and looking at the actual UX change. Before:
1. Click the link.
2. Click the yes button in "Open this link in App Installer?"
3. Click Install/Launch in App Installer.
After:
1. Click the link. It downloads.
2. Click the download in the browser. App Installer opens.
3. Click the Launch/Install button.
Same number of clicks. The URL handler _is_ better because it has more features, because the permission to open URLs is remembered per site, because URLs work in more places, because it doesn't clutter the user's downloads folder and so on. So we all hope it'll return. But, for distribution via a web page, the difference isn't that large.
- Unfortunately not a workable solution. Where on earth is the fix Microsoft?
- MikeH Thanks for the details! How do automatic updates work with the workaround? Do they still happen automatically or does the user need to go download the installer manually?
Tom
