Forum Discussion
Windows 10 2004 - MSIX Not Updating -Please check whether the Msixvc support services are installed.
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.
Microsofthi 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.Hi Sharla,
I just wanted to follow up and see if you were able to see anything or if you had a chance to look at this again yet. If you haven't, I understand. The users have been given guidance to use the bundle file until we can find a better solution regarding this, but its still a huge problem. 😞
As far as other things we have tried, I adjusted our CI/CD pipeline in Azure to apply version numbers to the .wapproj file that has a zero for the last number, but that didn't result in any changes. I was hoping it would help since the YAML we were using was adding version numbers that had a number in the last digit (one of the examples we found on MSDN showed that it was supposedly safe to do this, but the MSIX documentation says it must stay as Zero and we recalled that Visual Studio doesn't allow you to change it when creating the app installer via the wizard).
We also tried turning off the "Automatic Background Task" setting in the app installer, but that hasn't seemed to make any difference either.
I'm currently trying to see if Process Monitor or Process Explorer can provide any more details as to what may be not responding correctly in Windows when these errors occur, but unfortunately I haven't had any success yet.
Again, please let me know if you or anyone on your team have any updates.