SOLVED

MSIX COM PROGID CLSID is invalid

%3CLINGO-SUB%20id%3D%22lingo-sub-1850210%22%20slang%3D%22en-US%22%3EMSIX%20COM%20PROGID%20CLSID%20is%20invalid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1850210%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHaving%20another%20easy%20app%20called%20mRemoteNG%20that%20throws%20lots%20of%20error.%20Automated%20package%20script%20located%20here%20for%20reproduction.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fhaavarstein%2FApplications%2Ftree%2Fmaster%2FMisc%2FmRemoteNG%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fhaavarstein%2FApplications%2Ftree%2Fmaster%2FMisc%2FmRemoteNG%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1850629%22%20slang%3D%22en-US%22%3EAnd%20the%20appRe%3A%20MSIX%20COM%20PROGID%20CLSID%20is%20invalid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1850629%22%20slang%3D%22en-US%22%3E%3CP%3Eand%20the%20app%20itself%20throws%20this%20error%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1851106%22%20slang%3D%22en-US%22%3ERe%3A%20And%20the%20appRe%3A%20MSIX%20COM%20PROGID%20CLSID%20is%20invalid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1851106%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F846219%22%20target%3D%22_blank%22%3E%40xenappblog%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20what%20I%20see%2C%20the%20MSIX%20Packaging%20Tool%20is%20not%20detecting%20the%20COM%20registrations%20for%20this%20app%20correctly.%20Then%2C%20when%20you%20execute%20it%20it%20fails%20because%20the%20package%20is%20missing%20the%20needed%20COM%20registrations.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20tried%20converting%20the%20app%20and%20the%20tool%20seems%20to%20be%20having%20issues%20converting%20the%20registrations%20for%20InprocServer%20and%20registrations%20under%20the%20WOW6432Node%20key%20on%20x64.%20I'm%20not%20sure%20if%20there%20is%20a%20way%20to%20tweak%20the%20registrations%20to%20make%20the%20tool%20detect%20them%20correctly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20reporting%20this.%20We%20will%20look%20into%20fixing%20it%20for%20future%20releases%20of%20the%20tool.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1882563%22%20slang%3D%22en-US%22%3ERe%3A%20And%20the%20appRe%3A%20MSIX%20COM%20PROGID%20CLSID%20is%20invalid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1882563%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F846219%22%20target%3D%22_blank%22%3E%40xenappblog%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETrond%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20a%20working%20package%20for%20that%20app.%26nbsp%3B%20I%20had%20to%20use%20the%20MSI%20installer%20(not%20the%20portable%20one)%2C%20include%20the%20file%20redirection%20fixup%2C%20and%20oddly%20I%20had%20to%20specify%20the%20install%20folder%20(PVAD%20Style%20not%20VFS).%26nbsp%3B%20I%20also%20had%20to%20keep%20AppDataLocal%20configuration%20out%20of%20the%20package.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

Having another easy app called mRemoteNG that throws lots of error. Automated package script located here for reproduction.

 

https://github.com/haavarstein/Applications/tree/master/Misc/mRemoteNG

3 Replies

and the app itself throws this error

Best Response confirmed by xenappblog (Occasional Contributor)
Solution

@xenappblog 

 

From what I see, the MSIX Packaging Tool is not detecting the COM registrations for this app correctly. Then, when you execute it it fails because the package is missing the needed COM registrations.

 

I tried converting the app and the tool seems to be having issues converting the registrations for InprocServer and registrations under the WOW6432Node key on x64. I'm not sure if there is a way to tweak the registrations to make the tool detect them correctly.

 

Thank you for reporting this. We will look into fixing it for future releases of the tool.

@xenappblog 

 

Trond,

 

I have a working package for that app.  I had to use the MSI installer (not the portable one), include the file redirection fixup, and oddly I had to specify the install folder (PVAD Style not VFS).  I also had to keep AppDataLocal configuration out of the package.