Virtual Registry support for Anaconda (possibly [{AppVCurrentUserSid}]

%3CLINGO-SUB%20id%3D%22lingo-sub-228084%22%20slang%3D%22en-US%22%3EVirtual%20Registry%20support%20for%20Anaconda%20(possibly%20%5B%7BAppVCurrentUserSid%7D%5D%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228084%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20package%20up%20the%20application%20Anaconda%2C%20the%20installer%20creates%20an%20entry%20under%20the%20registry%20key%20%3CSTRONG%3EHKLM%5CSystem%5CCurrentControlSet%5CServices%5Cbam%5CState%5CUserSettings%5C%7Breplace%20with%20user%20sid%20here%7D%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENOTE%3A%20The%20application%20is%20NOT%20installing%20a%20service%2C%20but%20is%20adding%20configuration%20that%20appears%20to%20be%20associated%20with%20BizTalk%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fbiztalk%2Fcore%2Fwhat-is-a-bam-definition%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fbiztalk%2Fcore%2Fwhat-is-a-bam-definition%20%3C%2FA%3E).%20So%20while%20it%20may%20be%20bad%20form%20to%20write%20user%20data%20under%20HKLM%5CSystem%2C%20it%20appears%20that%20this%20is%20what%20a%20Microsoft%20product%20documents%20to%20do!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Packaging%20tool%20list%20of%20registry%20exclusions%20does%20not%20have%20an%20entry%20for%20this%20area%20and%20if%20I%20open%20the%20package%20in%20the%20editor%20part%20of%20the%20tool%20I%20can%20see%20that%20the%20capture%20did%20occur%2C%20and%20is%20stored%20using%20the%20old%20AppV%20syntax%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3EHKLM%5CSystem%5CCurrentControlSet%5CServices%5Cbam%5CState%5CUserSettings%5C%5B%7BAppVCurrentUserSid%7D%5D%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20sure%20if%20the%20issue%20is%20the%20capture%20and%20it%20should%20have%20been%20variablized%20differently%2C%20or%20if%20the%20problem%20is%20in%20the%20MSIX%20runtime%20not%20handling%20the%20registry%20request%20to%20query%20values%20under%3C%2FP%3E%3CP%3E%3CSTRONG%3EHKLM%5CSystem%5CCurrentControlSet%5CServices%5Cbam%5CState%5CUserSettings%5C%7Breplace%20with%20user%20sid%20here%7D%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3Ebut%20a%20procmon%20trace%20shows%20the%20query%20returned%20%22Name%20Not%20Found%22.%26nbsp%3B%20At%20which%20point%20the%20app%20shuts%20down.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EInterestingly%2C%20the%20trace%20shows%20a%20regopenkey%20on%20that%20key%20succeeding%2C%20just%20not%20the%20query.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20package%20(1.9GB)%20is%20available%20upon%20request.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324728%22%20slang%3D%22en-US%22%3ERe%3A%20Virtual%20Registry%20support%20for%20Anaconda%20(possibly%20%5B%7BAppVCurrentUserSid%7D%5D%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324728%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20sounds%20like%20a%20good%20candidate%20for%20a%20fixup.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

If you package up the application Anaconda, the installer creates an entry under the registry key HKLM\System\CurrentControlSet\Services\bam\State\UserSettings\{replace with user sid here}

 

NOTE: The application is NOT installing a service, but is adding configuration that appears to be associated with BizTalk (https://docs.microsoft.com/en-us/biztalk/core/what-is-a-bam-definition ). So while it may be bad form to write user data under HKLM\System, it appears that this is what a Microsoft product documents to do!

 

The Packaging tool list of registry exclusions does not have an entry for this area and if I open the package in the editor part of the tool I can see that the capture did occur, and is stored using the old AppV syntax:

HKLM\System\CurrentControlSet\Services\bam\State\UserSettings\[{AppVCurrentUserSid}]

 

I'm not sure if the issue is the capture and it should have been variablized differently, or if the problem is in the MSIX runtime not handling the registry request to query values under

HKLM\System\CurrentControlSet\Services\bam\State\UserSettings\{replace with user sid here}

but a procmon trace shows the query returned "Name Not Found".  At which point the app shuts down.

 

Interestingly, the trace shows a regopenkey on that key succeeding, just not the query.

 

The package (1.9GB) is available upon request.

1 Reply

This sounds like a good candidate for a fixup. :)