Error 0xC00CEE23 when Minor Version >= 10

%3CLINGO-SUB%20id%3D%22lingo-sub-1780808%22%20slang%3D%22en-US%22%3EError%200xC00CEE23%20when%20Minor%20Version%20%26gt%3B%3D%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1780808%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20a%20strange%20issue%20the%20other%20day.%20When%20the%20Minor%20version%20number%20is%20greater%20than%20or%20equal%20to%2010%2C%20Windows%2010%202004%20machines%20will%20not%20be%20able%20to%20install%20a%20package%20from%20a%20URI.%20UNC%20paths%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20the%20full%20error%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22App%20installation%20failed%20with%20error%20message%3A%20error%200xC00CEE23%3A%20The%20XML%20in%20the%20.appinstaller%20file%20is%20not%20valid%3A%20Line%2014%2C%20Column%2011%2C%20Reason%3A%20'%26gt%3B'%20expected.%20(0xc00cee23)%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEverything%20works%20fine%20when%20the%20version%20is%209%20or%20less.%20I%20just%20created%20a%203.10.X.X%20release%20for%20my%20WPF%20application%20%26amp%3B%20that's%20when%20I%20found%20the%20bug.%20For%20the%20time%20being%20I%20just%20kept%20my%20Minor%20version%209%20in%20the%20package%2C%20%26amp%3B%20increased%20the%20Build%20number.%20Not%20sure%20what's%20going%20to%20happen%20when%20build%20number%20reaches%2010.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20test%20the%20installer%20on%20my%20local%20network%20using%20a%20UNC%20path%2C%20everything%20works%20fine.%20It's%20only%20when%20I%20changed%20to%20my%20HTTPS%20URL%20that%20I%20receive%20this%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20were%20similar%20mentions%20of%20the%20error%20in%20the%20comments%20for%20this%20topic.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix-deployment%2Fwindows-10-2004-msix-not-updating-please-check-whether-the%2Ftd-p%2F1466701%23.X4c90kyouCU.link%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix-deployment%2Fwindows-10-2004-msix-not-updating-please-check-whether-the%2Ftd-p%2F1466701%23.X4c90kyouCU.link%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1829192%22%20slang%3D%22en-US%22%3ERe%3A%20Error%200xC00CEE23%20when%20Minor%20Version%20%26gt%3B%3D%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1829192%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F832469%22%20target%3D%22_blank%22%3E%40bvenhaus%3C%2FA%3E%26nbsp%3BI%20have%20the%20same%20problem%20here%20!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1834322%22%20slang%3D%22en-US%22%3ERe%3A%20Error%200xC00CEE23%20when%20Minor%20Version%20%26gt%3B%3D%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1834322%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20reporting%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F832469%22%20target%3D%22_blank%22%3E%40bvenhaus%3C%2FA%3E.%20We're%20looking%20into%20the%20issue%20and%20working%20to%20get%20it%20resolved.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3ETanaka%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2004955%22%20slang%3D%22en-US%22%3ERe%3A%20Error%200xC00CEE23%20when%20Minor%20Version%20%26gt%3B%3D%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2004955%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here%20too.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F832469%22%20target%3D%22_blank%22%3E%40bvenhaus%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I found a strange issue the other day. When the Minor version number is greater than or equal to 10, Windows 10 2004 machines will not be able to install a package from a URI. UNC paths work.

 

Here is the full error message:

 

"App installation failed with error message: error 0xC00CEE23: The XML in the .appinstaller file is not valid: Line 14, Column 11, Reason: '>' expected. (0xc00cee23)"

 

Everything works fine when the version is 9 or less. I just created a 3.10.X.X release for my WPF application & that's when I found the bug. For the time being I just kept my Minor version 9 in the package, & increased the Build number. Not sure what's going to happen when build number reaches 10.

 

When I test the installer on my local network using a UNC path, everything works fine. It's only when I changed to my HTTPS URL that I receive this error.

 

There were similar mentions of the error in the comments for this topic. 

https://techcommunity.microsoft.com/t5/msix-deployment/windows-10-2004-msix-not-updating-please-chec...

3 Replies

@bvenhaus I have the same problem here !

Thanks for reporting this @bvenhaus. We're looking into the issue and working to get it resolved.

 

Cheers,

Tanaka

Same issue here too.

@bvenhaus