Forum Discussion
MSIX HKLM not read
I have created an MSIX application and the application does capture some registry data in: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Odyssey\Starter
Now when starting this application I see this in procmon:
When I create the required registry data 'outside' the MSIX package in the local HKLM registry, the application works fine. What is going on here? Is this default behavior or do i miss here something?
I think this is already some while ago mentioned in the following thread, but did not see any update so far: msix HKLM key not read | Microsoft Community Hub
Anyone who can clear this behavior for me and how to fix this?
When i do create the registry keys locally, I see this in procmon:
some update from my side:
When I create 'empty' keys locally, then the values will be read in the MSIX package.....is this a bug, or is this expected behavior?
Does anyone read this community, since I already expected some replies already.As I recall the issue from the past, it is like this:
- Package has key a\b
- At runtime the app creates key a\b\c successfully.
- At runtime the app then tries to create key a\b\c\d and fails.
- Including key a\b\c in the package solves the problem.
