-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
[BUG]: Error Running Script #351
Comments
Hi @giogio33, thank you for all the context. The logs show that:
Some questions to understand whats going on:
|
Thank you for all of the information. It helped to eliminate other factors and I found out the problem. privacy.sexy runs this files using powershell. It sends the script path in double quotes as argument to powershell using double quotes to handle whitespaces in paths. However for some reason, PowerShell strips away double quotes when it parses arguments, and fails when you have whitespace in script path (your user name in that case). See StackOverflow thread on this. I set up a user with whitespace in its name and I can reproduce the issue. I will solve this in next patch. Thank you again for the guidance and bug report. |
This commit addresses the issue where scripts fail to execute on Windows environments with usernames containing spaces. The problem stemmed from PowerShell and cmd shell's handling of spaces in quoted arguments. The solution involves encoding PowerShell commands before execution, which mitigates the quoting issues previously causing script failures. This approach is now integrated into the execution flow, ensuring that commands are correctly handled irrespective of user names or other variables that may include spaces. Changes: - Implement encoding for PowerShell commands to handle spaces in usernames and other similar scenarios. - Update script documentation URLs to reflect changes in directory structure. Fixes #351
I disabled all antivirus and protection. Ran also as Administrator. I also tried in safe mode with networking. 80GB free on the disk.
This image was cleaned with Tweaking.com. Seems to run perfectly. It has been just upgraded from Win10-20H2 to Win10 22H2.
The only issue this image seems to have is that I have a windows security update failing after all upgrades and chose not to longer upgrade. Microsoft.
Description
I get Error Running Script, Fully Control on AppData\Roaming\privacy.sexy\runs and I tested it
OS
Win 10 Pro 22H2 (OS Build 19045.4355)
This image on 22H2 did not give me error prior upgrade to 22H2 from 20H2
I restored it to an image I had of the 20H2 prior running Privacy sexy, so it was clean
Reproduction steps
I also tried to only select Clear recently Opened application list and if gives error. This image on 22H2 did not give me error prior upgrade to 22H2
Scripts
If applicable, please attach the generated privacy.sexy file instead of copy pasting which becomes too long.
privacy-script.log
Additional information
main.log
The text was updated successfully, but these errors were encountered: