microsoft / microsoft/WindowsAppSDK

I MUST write to a unvirtualized HKLM key in my packaged app

Open
#6,410 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-PackageManagement needs-triage
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

My app needs to write to some HKLM keys for Office interop support, however I can't find a solution.

I've looked at the Registry.dat but changes made using it are not visible to Office, I've looked at Package Support Framework, but it doesn't support ARM64 (which is required for Copilot+ PCs)

Is there a solution for me, or do I need to abandon packaging?

Something I don't quite understand, is that my app is packaged and therefore shouldn't be able to write to HKLM, yet when I call StorageProviderSyncRootManager.Register() keys are written to HKLM which are later read by explorer.exe - so how is that occuring?

Steps to reproduce the bug

Try to write to HKLM

Expected behavior

No response

Screenshots

No response

NuGet package version

Latest

Packaging type

Packaged (MSIX)

Windows version

No response

IDE

No response

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the issue's references to Registry.dat, Package Support Framework, and StorageProviderSyncRootManager.Register(), focusing on packaged MSIX apps and ARM64. Determine whether an existing supported entry point addresses unvirtualized HKLM writes and what a documented solution or confirmed limitation would look like.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.