Forum Discussion
MSIX Runtime HKCU CreateKey
If you have a package that contains the registry key
HKEY_CURRENT_USER\Software\Vendor
And you run that package and it creates a subkey under Vendor named "Settings".
If the application calls CreateKey against the "Vendor" key requesting access "MaximumAllowed", it is granted permissions "Read/Write."
If the application calls CreateKey against "Settings" key requesting access "MaximumAllowed", it is only granted permissions "Read, Write DAC".
Attached is a procmon trace showing this situation, the highlighted line being the case of opening the key from the redirected helium containerized registry. In this case, the app examined the return permissions and gives up.
8 Replies
Aniket_BanerjeeMicrosoft
Thanks for reporting this. I would love to know a little more details about this issue (like App name, expected registry details, if it was previously installed, etc.
However, I have faced similar issues in the past, and found that (the workaround of) enabling the capability of 'Run as administrator (restricted)' often resolves this issue.
In case this doesn't work, you can also try to run the (MSIX) application as an administrator, and it may resolve this issue.
The application is "ExamDiff" from PrestoSoft (a free product you can access from their website).
The image I provided in the original post shows the line in a procmon trace that is problematic as the highlighted one (click on the image to view). The test was on a clean VM that had never seen the product.
This example was taken from a package that included the PSF RegLegacyFixup (which is needed because without it the app won't store user options in the registry at all). The result shows in the details column of procmon that "Read, Write DAC" permissions were granted. Instead, the result should say that "Read/Write" permissions were granted, just like the call made against the parent key 6 lines previous.- Aniket_Banerjee
Would it be possible for you to share the config.json for the PSF RegLegacyFixup? We can try to fix this manually. We'll share the fix if it works.
