-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Inconsistent registry virtualization in Windows Store package #90796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The build of the Store package detects whether the build PC supports disabling registry virtualisation or not when deciding whether to add it to the manifest. Because our release builds just moved from the windows-2019 image to the windows-2022 image, this setting changed and now builds have virtualisation disabled. While this is probably desirable for some users, having it happen without warning is bad. I'll check whether we can leave it unconditionally enabled for 3.11 and still install on older Windows versions. If it won't install, we'll just have to leave it disabled. |
Okay, so it doesn't install at all on 1803. However, that's out of support 1, so I guess it doesn't matter. In theory, 1809 should be the first one that supports it. I'll try that, but I think we're okay to leave this turned on for 3.11. The changes for 3.9-3.10 will be to disable the option unconditionally. |
Didn't work on 1809, but it does work on 20H2, which is the earliest update that will still be supported when 3.11 ships. I didn't try the ones in between, but I think we're okay to ignore them. Interestingly, double-clicking the MSIX on Windows 11 refuses to install because of the unvirtualised resources, but on earlier Windows it's fine. The Powershell command (Add-AppxPackage <filename>) does work fine though. I'll see if I can find out what happened. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: