I've not found any documentation on this yet, but it looks like each MSIX `Application` that registers for a file association (or a protocol handler) gets an `AppX...` AppID generated. Those AppIDs are then used in the regular registry locations, like: ``` Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf ``` One can find the details in the usual place, like: ``` Computer\HKEY_CLASSES_ROOT\AppX...\Application ``` and from there find package details in `AppUserModelID`, which always appears to be the package family name. I'm not sure if the generated AppID is: - per-package name (including version, etc) - per-package family name (not including version, etc) - per-device - per-installation But hopefully none of that really matters.
Bug 1742658 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I've not found any documentation on this yet, but it looks like each MSIX `Application` that registers for a file association (or a protocol handler) gets an `AppX...` AppID generated. Those AppIDs are then used in the regular registry locations, like: ``` Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf ``` One can find the details in the usual place, like: ``` Computer\HKEY_CLASSES_ROOT\AppX...\Application ``` and from there find package details in `AppUserModelID`, which always appears to be the package family name. I'm not sure if the generated AppID is: - per-package name (including version, etc) - per-package family name (not including version, etc) - per-device - per-installation But hopefully none of that really matters, and the registry entries let us figure everything out.