microsoft / microsoft/msix-packaging
MSIX HKLM not read
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
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:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Procmon traces and reproduce the MSIX application's access to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Odyssey\Starter. Compare that behavior with registry keys created outside the package, then determine whether the discrepancy is expected MSIX behavior or a packaging defect. Done means documenting the cause and an actionable fix or workaround.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100