You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
assignee='https://github.com/zooba'closed_at=<Date2022-02-09.16:15:34.156>created_at=<Date2022-02-04.16:16:10.406>labels= ['3.10', 'type-bug', '3.9', 'OS-windows', '3.11']
title='Inconsistent registry virtualization in Windows Store package'updated_at=<Date2022-02-09.16:15:34.155>user='https://github.com/zooba'
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.
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.