SOLVED

User registry inside the package?

%3CLINGO-SUB%20id%3D%22lingo-sub-234642%22%20slang%3D%22en-US%22%3EUser%20registry%20inside%20the%20package%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-234642%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20far%20we%20knew%20that%20HKCU%20entries%20are%20not%20allowed%20in%20the%20appx%20package%2C%20as%20mentioned%26nbsp%3Bin%20%3CA%20title%3D%22Desktop%20Bridge%20registry%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fuwp%2Fporting%2Fdesktop-to-uwp-behind-the-scenes%23registry%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%26nbsp%3Bdocs%20article%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EExtract%20from%20the%20article%3A%3C%2FSTRONG%3E%26nbsp%3B%3CEM%3E%3CSPAN%3EOnly%20keys%20under%26nbsp%3B%3C%2FSPAN%3EHKLM%5CSoftware%3CSPAN%3E%26nbsp%3Bare%20part%20of%20the%20package%3B%20keys%20under%26nbsp%3B%3C%2FSPAN%3EHKCU%3CSPAN%3E%26nbsp%3Bor%20other%20parts%20of%20the%20registry%20are%20not.%26nbsp%3B%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20MSIX%20package%20we've%20created%20with%20the%20new%20MSIX%20Packaging%20Tool%20we%20also%20see%20%3CSTRONG%3EUser.dat%3C%2FSTRONG%3E%20and%26nbsp%3B%3CSTRONG%3EUser.Classes.dat%3C%2FSTRONG%3E%2C%20next%20to%20the%20usual%20registry.dat%20file.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20there%20any%20updated%20docs%20that%20can%20give%20us%20more%20details%20about%20the%20changes%20in%20this%20area%3F%20Or%20basically%20all%20entries%20from%20these%20hives%20can%20now%20be%20stored%20inside%20the%20package.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239409%22%20slang%3D%22en-US%22%3ERe%3A%20User%20registry%20inside%20the%20package%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239409%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20working%20to%20update%20the%20docs%20for%20these%20prerelease%20items.%20In%20short%20it%20should%20be%20fairly%20open%2C%20but%20if%20there%20are%20any%20limitations%20as%20we%20lock%20the%20final%20release.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-806579%22%20slang%3D%22en-US%22%3ERe%3A%20User%20registry%20inside%20the%20package%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-806579%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73899%22%20target%3D%22_blank%22%3E%40John%20Vintzel%3C%2FA%3E%26nbsp%3B2%20years%20in%20and%20still%20no%20change.%20Hardly%20any%20improvement%20for%20MSIX%2C%20don't%20see%20a%20future%20for%20it%20as%20it's%20hardly%20usable%20for%20real%20environment.%20Take%207zip%20for%20example%2C%20if%20you%20package%20it%20into%20msix%20you%20cannot%20do%20file%20association%20or%20context%20menu.%20MSIX%20is%20by%20far%20not%20what%20it%20was%20promised.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-811595%22%20slang%3D%22en-US%22%3ERe%3A%20User%20registry%20inside%20the%20package%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-811595%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F380087%22%20target%3D%22_blank%22%3E%40_Florin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20appreciate%20the%20feedback.%26nbsp%3B%20MSIX%20was%20originally%20started%20as%20part%20of%20the%201809%20release%2C%20so%20we%20are%20nearing%20one%20year%2C%20not%20two%20as%20mentioned.%26nbsp%3B%20Since%20then%20we%20have%20added%20lots%20of%20new%20features%20based%20on%20customer%20feedback.%26nbsp%3B%20The%20MSIX%20Packaging%20Tool%20has%20had%20three%20major%20updates%20with%20new%20features%20and%20improved%20workflows.%26nbsp%3B%20We%20added%20support%20for%20Windows%2010%201709%20and%201803.%26nbsp%3B%20We%20launched%20the%20preview%20of%20MSIX%20core%20for%20IT%20Pros%20that%20brings%20MSIX%20to%20all%20supported%20Windows%20operating%20systems.%26nbsp%3B%20We%20added%20scripting%20support%20to%20MSIX%20with%20the%20package%20support%20framework.%26nbsp%3B%20Support%20for%20MSIX%20with%20Windows%20Services%20is%20in%20an%20insider%20preview.%20We%20also%20have%20a%20feature%20in%20preview%20that%20allows%20customers%20with%20Azure%20AD%20to%20sign%20their%20packages%20with%20a%20certificate%20unique%20to%20their%20tenant%20and%20not%20need%20to%20acquire%20an%20additional%20code%20signing%20cert%20(Thanks%20Device%20Guard%20team!).%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20a%20lot%20of%20other%20smaller%20features%20that%20have%20been%20release%20and%20others%20in%20insider%20builds.%26nbsp%3B%20I%20understand%20that%20everyone%20has%20their%20own%20asks%20for%20what%20features%20are%20important%20to%20them.%26nbsp%3B%20I%20recommend%20you%20file%20items%20in%20the%20Ideas%20section%20of%20the%20Tech%20Community%20and%20we%20can%20prioritize%20work%20based%20on%20customer%20demand.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJohn%20(%3CA%20href%3D%22http%3A%2F%2Fwww.twitter.com%2Fjvintzel%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%40jvintzel%3C%2FA%3E)%3C%2FP%3E%0A%3CP%3EPM%20Lead%2C%20MSIX%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

So far we knew that HKCU entries are not allowed in the appx package, as mentioned in this docs article.

 

Extract from the article: Only keys under HKLM\Software are part of the package; keys under HKCU or other parts of the registry are not. 

 

In the MSIX package we've created with the new MSIX Packaging Tool we also see User.dat and User.Classes.dat, next to the usual registry.dat file.

 

Are there any updated docs that can give us more details about the changes in this area? Or basically all entries from these hives can now be stored inside the package.

3 Replies
Best Response confirmed by John Vintzel (Microsoft)
Solution

We are working to update the docs for these prerelease items. In short it should be fairly open, but if there are any limitations as we lock the final release.  

@John Vintzel 2 years in and still no change. Hardly any improvement for MSIX, don't see a future for it as it's hardly usable for real environment. Take 7zip for example, if you package it into msix you cannot do file association or context menu. MSIX is by far not what it was promised.

@_Florin 

 

We appreciate the feedback.  MSIX was originally started as part of the 1809 release, so we are nearing one year, not two as mentioned.  Since then we have added lots of new features based on customer feedback.  The MSIX Packaging Tool has had three major updates with new features and improved workflows.  We added support for Windows 10 1709 and 1803.  We launched the preview of MSIX core for IT Pros that brings MSIX to all supported Windows operating systems.  We added scripting support to MSIX with the package support framework.  Support for MSIX with Windows Services is in an insider preview. We also have a feature in preview that allows customers with Azure AD to sign their packages with a certificate unique to their tenant and not need to acquire an additional code signing cert (Thanks Device Guard team!).  

 

There is a lot of other smaller features that have been release and others in insider builds.  I understand that everyone has their own asks for what features are important to them.  I recommend you file items in the Ideas section of the Tech Community and we can prioritize work based on customer demand.

 

John (@jvintzel)

PM Lead, MSIX