Forum Discussion
StephenWhiteD3G
Jun 16, 2020Iron Contributor
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
Nov 09, 2020Copper Contributor
Hi,
we have the same problem. On Windows 10 2004 MSIX updates fail with errors same as mentioned in the previous comments.
This issue is critical for us because we use MSIX and .appinstaller files in production and more and more our users are switching from Windows 10 1909 to 2004.
John_Torjo
Jan 15, 2021Copper Contributor
annaojdowska Hi, I have the same problem. Hopefully MS will fix it sometimes in this decade.
- GToisonFeb 25, 2021Copper Contributor
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.
- GToisonMar 11, 2021Copper Contributor
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
- StephenWhiteD3GMar 11, 2021Iron Contributor
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.