Forum Discussion
Windows 10 2004 - MSIX Not Updating -Please check whether the Msixvc support services are installed.
Apologies for the delay here. We've passed on your Feedback Hub submission and logs to the Dev team for further investigation. We'll let you know as soon as we get more details on the issue and any potential ways to address it.
Cheers,
Tanaka
Hello again Tanaka_Jimha!
Thanks for the update, I really appreciate it. And again, please don't interpret my last response as being upset with Sharla, after all she helped get the ball rolling on this. 🙂
I'll let the people on my end know that the issue is being looked into and will let them know we should hold off on making any chances to our CI/CD or deployment until I hear back.
Thanks again!
- and me 🙋:male_sign:
ShakersMSFT StephenWhiteD3G davidanthoff marcinotorowski I am also getting the 0xC00CEE23 errors. I see those when my Minor version number is >= 10. If I decrease the version to 9 things work perfectly. For whatever reason, App Installer may not like version numbers greater than 9.
https://techcommunity.microsoft.com/t5/msix-deployment/error-0xc00cee23-when-minor-version-gt-10/td-p/1780808#.X4dBZY6BG74.linkgug_82
I'm glad to hear it helped.
I submitted a bug for this also in Microsoft Collaborate, but it doesn't look like any significant changes have been made yet though. Also, I had a one on one with someone at Microsoft about this and a few other things a couple of weeks back and they said that this problem will only get resolved with an OS update. I had a feeling that was the case.
Also, if you have the option of keeping your users from updating to 2004, that is what they encouraged. But if not, restarting is really the only work around right now.- Hey man! I spent one day to find out why it happens on some PCs only with Windows 10, v2004. at the end of day I found your comment, and **bleep**! restarting pc helps!! Thank you!
- FWIW, I am experiencing this issue as well.
- ShakersMSFT
Microsoft
davidanthoff StephenWhiteD3G marcinotorowski
Just as an update, we are still investigating this issue. Thank you for your patience, we will continue to update you as we learn more.
Best,
Sharla
Yes, a system restart also solves this reliably for me.
To me this just looks like a bug in AppInstaller. Would be great if someone from MS could confirm that and let us know about any plans to fix this and how such a fix might be distributed. As it stands right now, this bug essentially means we can't use AppInstaller at all, this seems a pretty critical bug in a very core code path?
- That's pretty much what has been happening on my end. Seems to start happening as soon as you install an update with app installer. Like you said, after that it is like something gets cached and/or not properly cleaned up and then the only option is to restart Windows to get it to do whatever it needs to do to clean up the state.
App installation failed with error message: error 0xC00CEE23: The XML in the .appinstaller file is not valid: Line 26, Column 7, Reason: '>' expected. (0xc00cee23)
I have seen this error a few times, though not regularly nor attached to any reproducible condition I could imagine of. In my case it had nothing to do with the hosting server, the XML file of .appinstaller definition nor the application itself, which were always OK (correct downloads, MIME types, validated XML, working manual installation etc.).
For me, sadly the "simplest" workaround always did the trick - the problem was gone after rebooting the machine, no other changes done. I would say this could have been a caching issue, if not for the fact that some deliberate changes on the live .appinstaller content were reflected by the messages of the appinstaller window (changing line numbers). Anyway, I am curious to see if this behaves like this on your machine(s) - if the reboot works then there are at least two of us with exactly the same issue 🙂
I'm also getting these kinds of errors. Specifically:
App installation failed with error message: error 0xC00CEE23: The XML in the .appinstaller file is not valid: Line 26, Column 7, Reason: '>' expected. (0xc00cee23)
I get this error an a system where I had a previous version of the appinstaller installed (but now uninstalled in the meantime). If I try exactly the same link on a fresh new system in a VM, it all works.
Quick update on this one, although I am not sure if it really helps or not -
On build 20161 it now shows a different exception in the app installer when it has the issue occur:
Common::Deployment::MsixvcStagingSession::GetManifestReader in MsixvcStagingSession failed with error 0x80070570.
The AppXDeployment-Server Event Viewer Log also has this exception:
Appinstaller operation failed with error code 0x80070570. Detail: The file or directory is corrupted and unreadable.And the Microsoft-Windows-Store Event Viewer log has theses exceptions:
XvcDataSource_GetManifestStream [XBL:]\https://myAzureBlobContainer.z13.web.core.windows.net/MSIX_Test/MyApp_X64.msixbundle
Function: XvcUtilities::GetUserDataStreamFromXvc
Source: (1008)XvcDataSource_GetManifestStream [XBL:]\https://myAzureBlobContainer.z13.web.core.windows.net/MSIX_Test/MyApp_X64.msixbundle
Function: XvcUtilities::RetryOnFailure
Source: (69)
XvcDataSource_GetManifestStream [XBL:]\https://myAzureBlobContainer.z13.web.core.windows.net/MSIX_Test/MyApp_X64.msixbundle
Error: The file or directory is corrupted and unreadable.
Function: XvcDataSource::GetManifestStream
Source: (106)
