Forum Discussion
Windows 10 2004 - MSIX Not Updating -Please check whether the Msixvc support services are installed.
We use MSIX for one of our LOB applications at my organization. We recently updated some machines to Windows 10 2004 to test it before rolling it out to the rest of the company. One problem we ha...
annaojdowska Hi, I have the same problem. Hopefully MS will fix it sometimes in this decade.
We had the same problem (with 20H2), our application's .msix was hosted on a webserver through the http (not https) protocol.
After switching to https it worked so I suspect that the Application Installer Service is using https to talk to the server, even if the url is http:// . Since the protocol is incorrect it can't download the .msix file and reports that it is corrupted.
After further testing the https switch was a red herring and the .appinstaller still fails to pick up the updated .msix.
However we have found that stopping (or restarting) the "Delivery Optimization" (DoSvc) service mitigates the problem because then we can update.So essentially we need to kill the service on all computer before updating the msix, otherwise the update will fail.
@annaojdowska This is not a great solution and it would be good to get some feedback from Microsoft on this issue
GToison
I have been told by one of the people on the app consult team that this problem should have been fixed in Windows 10 20H2, but judging from your previous comment, this is not the case. That is a shame.
It's also shame that this happened since MS put a lot of effort into promoting MSIX. We really did want to use it but after this problem, we ended up going back to MSI and creating our own app updater and we haven't had any problems. It also sped up our pipelines and all our users now prefer our in-house updater versus the app installer.- AppInstaller + MSIX worked great for us on Windows 10 1909 but broke after upgrading to 20H2.
What's particularly frustrating is the error reporting: these error codes and messages are not very helpful. For instance we tried adding the version number to the URL of the .msix but then appinstaller complained that the XML was invalid (error 0xC00CEE23).
We also had some users reporting that error when trying to update our application:
App installation failed with error message: Windows cannot perform the RegisterByPackageFamilyName operation because it could not find Microsoft.Office.C2RX_8wekyb3d8bbwe in the repository. Make sure Microsoft.Office.C2RX_8wekyb3d8bbwe has been staged or was installed by another user. (0x80070002)
Our application does not have any dependency with Office...
As you said MS put a lot of effort into it, but right now appinstaller is broken for us and these error messages are not helping
