Forum Discussion
StephenWhiteD3G
Jun 15, 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...
GToison
Mar 11, 2021Copper Contributor
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
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
StephenWhiteD3G
Mar 11, 2021Iron Contributor
That sounds like what we had; it was fine for the most part on 1909, but after that it became too unreliable and a poor user experience, so we had no choice but to abandon it (roll backs / re-imaging were out of the question).
Out of curiosity, did you try the work around that LuKePicci posted up above? I didn't have a chance to try it myself since we had moved on from MSIX by the time he posted it, but it sounded promising (if you don't need to make the package an app bundle).
Out of curiosity, did you try the work around that LuKePicci posted up above? I didn't have a chance to try it myself since we had moved on from MSIX by the time he posted it, but it sounded promising (if you don't need to make the package an app bundle).
- GToisonMar 11, 2021Copper ContributorOur appinstaller file only has a <MainPackage> and the .msix is built with makeappx (and then signed with signtool). The .msix installs correctly.
It is actually a Java application so we don't build in Visual Studio.