Closed pschlan closed 2 years ago
Hi,
The possible fix is in https://github.com/SoftwareNetwork/sw/commit/8e37f37068672f4aa7a861f183096d9edda4d97d You can try to download build artifacts from CI after build and try it. They will be on this page https://github.com/SoftwareNetwork/sw/actions/runs/2345978897
Just tried the CI binaries and it looks like the issue is solved. Registry keys and files are created in the proper location. Thanks for the quick fix!
Describe the bug On Windows,
sw setup
first elevates and then installs files in $HOME/.sw/ and registry keys in HKEY_CURRENT_USER. In setups where the current user and the Administrator account are different, after elevation,sw setup
incorrectly installs the files and registry keys in the Administrator's account, since the current home dir and HKEY_CURRENT_USER are now pointing to the Administrator account.As a result,
sw setup
does not work correctly. The CMake package is not installed correctly for the current user, but for the system administrator account instead.Expected behavior
sw setup
should first install things which are for the current user, and only then elevate and install system-wide things (like HKEY_CLASSES_ROOT reg keys).To Reproduce Steps to reproduce the behavior:
sw setup
and elevate using an admin accountInformation:
Paste
sw --version
output.Write OS, its version (host/target)
Windows 10 Enterprise 21H1
Describe your compiler, its version MS VC 2019 (should not be relevant, though)