Forum Discussion
More registry issues on OS 2004
I am bumping this issue as it still has not been addressed and probably should be.
If a package includes registry.dat file(s) for user settings, let's say the equivalent to HKCU\Software\Vendor\App, there is a significant limitation (read bug) in the runtime registry support when the app is run inside the container:
- The app can add new registry items under the "App" key.
- The app can add a new subkey under the "App" key (let's call it "Subkey").
- The app can add new registry items under the new "Subkey".
- The app cannot add another subkey under the new "Subkey".
This is not expected behavior and cases apps to fail. I've mentioned two such apps that show this behavior when re-packaged into MSIX and I'm sure there are many more.
The only work-around is to discover every sub-subkey the app might create at runtime and include these in the package registry. This is not an acceptable long-term workaround as there is no complete discovery process possible if you don't have the source code to the app.
This behavior would also not be expected by any new, modern, apps that choose to use the registry, and if not addressed will cause some of those apps issues too.
TIMOTHY_MANGAN
We tested the Siemens JtToGo App on Win 10 and Win 11:
- App's package does not contain any predefined subkeys as mentioned "VPSearch" or sub-subkey "LocationCache".
- App successfully created subkeys(VPSearch) and sub-subkeys(LocationCache) on both OSs.
Testing environment:
Win 10 - Version: 21H2
Win 11 - Version: 22H2
Are you still seeing this issue?
- Jul 12, 2023I will go back and re-test. There was a fix I made to the RegLegFixup two weeks ago that may have been for the cause of this issue. Not all of the fixup rules were being used so it is possible that the requested permissions were not corrected in the call.
- Jul 12, 2023Confirmed: Siemens JT2Go and WinSCP no longer have this issue.