Dec 14 2021 10:07 AM - edited Dec 14 2021 10:53 AM
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" button they now see the error below saying the protocol has been disabled. Why is this? Is this permanent? Is there a way to enable it?
There's a short mention of this in the docs but it doesn't mention why this is happening or how to enable it.
Installing Windows 10 apps from a web page - MSIX | Microsoft Docs
Is this no longer supported?
<html>
<body>
<h1> MyApp Web Page </h1>
<a href="ms-appinstaller:?source=http://mywebservice.azureedge.net/HubApp.msix"> Install app package </a>
<a href="ms-appinstaller:?source=http://mywebservice.azureedge.net/HubAppBundle.msixbundle"> Install app bundle </a>
<a href="ms-appinstaller:?source=http://mywebservice.azureedge.net/HubAppSet.appinstaller"> Install related set </a>
</body>
</html>
The ms-appinstaller protocol has been disabled. Please ask the vendor to update the weblink. For more information go to aka.ms/ms-appinstaller-disabled
Jan 13 2022 07:15 PM
Jan 13 2022 07:50 PM - edited Jan 13 2022 07:52 PM
Yes it may not satifsy your use case. I am ok with my users downloading a file instead as a work-around for now until Microsoft can restore the original functionality securely.
You can set the https://docs.microsoft.com/en-us/uwp/schemas/appinstallerschema/element-update-settings update-settings flag to OnLaunch or AutomaticBackgroundTask and the https://docs.microsoft.com/en-us/uwp/schemas/appinstallerschema/element-automatic-background-task element-automatic-background-task flag to check for updates periodically once installed.
Jan 14 2022 04:13 AM
Jan 14 2022 12:29 PM
Jan 17 2022 09:09 AM
Jan 18 2022 05:48 AM
Jan 21 2022 05:06 AM
Can you please explain what is going on with this?
My customer in Switzerland does not have this issue and can update the app in the normal manner.
Perhaps you can please reinstate the protocol and allow all our app users to update our app, even if for a limited time.
This totally unacceptable and can you please confirm this has been escalated from yourself to others who can sort out this issue.
Jan 21 2022 07:56 AM - edited Jan 21 2022 07:58 AM
This is completely unacceptable for an installation technology. MSIX team: if you’re not willing to properly support AppInstaller, please put it it out of its misery.
Jan 21 2022 10:09 AM
Jan 21 2022 10:46 AM
@hrb-2 Maybe for UWP. Our UWP line of business App is actually in the Windows Store (well Windows Store for Business), but this was such a simpler solution. And Microsoft pushed the Windows Application Packaging Platform for everything so we have been using it to sideload WPF projects, but NoooOo.. They gotta break it just when things were getting easier to deploy. Unbelievable.. lol actually totally believable.
Jan 24 2022 02:34 PM
Jan 24 2022 11:20 PM - edited Jan 24 2022 11:24 PM
@Aditi Now it has been more than a month - should MS be providing some updates on this issue???
It now has over 14,000 views - given how specific the issues is it would seem unlikely these are accidental occurrences and the impact is growing and being noticed. It is bad enough that the temporary fix of just cutting everyone off is most likely worse than the disease, but not informing folks of any progress on a fix implies a complete lack of progress and caring about the problems your customers are facing.
Jan 27 2022 04:28 PM
For anybody that is still having issues with this here is how I temporarily solved this problem.
When my application starts up it checks the version number (manually maintained in my App.xaml) against the version hosted on our webserver. If there is an updated version it downloads a zip file with msix and the generated shell scripts. It then upzips the files and runs the shell script through PowerShell to install the new version.
Note that this requires the device be in developer mode because executing the shell script is considered installing from an unknown publisher. I'm sure somebody smarter than me could find a work around that doesn't require developer mode (if so reply so I can make the changes).
Jan 27 2022 05:35 PM
Jan 28 2022 01:03 AM
@hrb-2You can see my solution here https://github.com/MicrosoftDocs/msix-docs/issues/59#issuecomment-832260691
It does not use shell scripts (which also means it does not require developer mode) but you should be able to work out how to change that.
This is a workaround for a much older bug feature but it works here too.
While we are on the subject, if you are manually editing your appinstaller file and/or your users are doing a lot of patching or installing at the moment, it is worth paying attention to this one as well: https://stackoverflow.com/questions/64381453/appinstaller-xml-issue/67390614#67390614
Jan 28 2022 07:04 AM
Mar 08 2022 03:25 PM
Apr 25 2022 11:21 AM