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...
Hi Sharla,
The LOB app is a WPF application using the Desktop Bridge targeting .NET Core 3.X.
Here is the feedback hub link:
https://aka.ms/AA8r372
I also noticed today that the App Installer project did not have itself set to target 2004. I am going to make this adjustment and let you know if this changes anything tonight when we run our next update for production.
Edit / Update: Unfortunately adjusting the App Installer to target 2004 did not make any changes. Also we found that if the user tries to go to the web page generated by the app installer project and clicks get the app, they get an error saying that it cannot open the MSIX Bundle. Either they have to restart their machine or they have to download the MSIX Bundle manually and run it.
@Sharla
One other addendum:
If we try to run the app installer on a computer that is on the fast ring, it gets a different, albeit misleading error:
0x8008020C. The specific error text for this failure is: error 0xC00CEE23: The XML in the .appinstaller file is not valid: Line 18, Column 13, Reason: '>' expected.
The same error shows up in the Microsoft-Windows-AppXDeploymentServer/Operational log.
However if I open up the app installer file and inspect it, it doesn't have any obvious signs of having any invalid XML, and again, it runs fine if I restart the machine or download the MSIX Bundle and run that directly.
It's almost like there's some other app installer file getting stuck somewhere and its running that instead of the one that I intend to run...?
I'm surprised I am the only one who has reported this; if you need any additional details, please let me know, this has us baffled. I think we can use a work around but I need to check a couple of different things. The obvious work around right now is to have the user restart their machine before updating, but obviously that gets old fast.
One other addendum:
If we try to run the app installer on a computer that is on the fast ring, it gets a different, albeit misleading error:
0x8008020C. The specific error text for this failure is: error 0xC00CEE23: The XML in the .appinstaller file is not valid: Line 18, Column 13, Reason: '>' expected.
The same error shows up in the Microsoft-Windows-AppXDeploymentServer/Operational log.
However if I open up the app installer file and inspect it, it doesn't have any obvious signs of having any invalid XML, and again, it runs fine if I restart the machine or download the MSIX Bundle and run that directly.
It's almost like there's some other app installer file getting stuck somewhere and its running that instead of the one that I intend to run...?
I'm surprised I am the only one who has reported this; if you need any additional details, please let me know, this has us baffled. I think we can use a work around but I need to check a couple of different things. The obvious work around right now is to have the user restart their machine before updating, but obviously that gets old fast.
- ShakersMSFT
Microsoft
hi StephenWhiteD3G,
Can you file feedback from impacted machines and the specific apps that fail to install? The feedback you filed previously doesn't have the logs we need to investigate further.
Best,
Sharla
- Hi Sharla,
I thought I did, but I'll do my best to get a repro going on one of them ASAP. Thanks for letting me know they were missing.
Hi again Sharla,I submitted another report using my organization account instead of personal account from a machine that is affected (my work PC actually). Please let me know if the diagnostics and the recording uploaded.
Here is the new feedback hub link:
https://aka.ms/AA8qzzo
Thanks again for your help, I hope we can get to the bottom of this soon.
P.S. As an experiment, I am going to remove the AutomatedBackgroundTask element in the app installer file on the next update for the org and see if that changes anything. I have a hypothesis that may be the cause of the problem, as I found earlier today that if I deployed an update locally and then quickly opened the app from the start menu, it was able to see and install the update without any problems and I was also able to uninstall and reinstall the app multiple times in a row without any errors.
