Closed MusicalAnvil closed 3 years ago
This wasn't something me or seemingly anyone else had encountered yet, even though it appears the default policy is supposed to be Restricted. Thanks for your contribution and bringing this to my attention.
I don't see anything inherently wrong with the changes here, but it got me wondering if it wouldn't be better to just explicitly run the script with "-ExecutionPolicy Bypass" to get around the restriction. The script needs to be run as an administrator in the first place so I wouldn't see it as bypassing real security rather than just removing annoying extra steps.
That actually makes a lot of sense. If it works then that should hopefully just solve the issue altogether without the need for any user troubleshooting.
Seemed to work on my end, so I just went ahead and pushed that change instead. Again, thanks for your report.
Updated readme.txt to include a potential issue with PowerShell's execution policy when troubleshooting Desktop+ elevated mode. Ran into this issue when troubleshooting my own setup, had to change mode to 'Bypass' to get the script to run, 'AllSigned' and 'RemoteSigned' would return an error stating that the file is not digitally signed. Added a short blurb about risks as well.