[BUG]: Error Running Script about privacy.sexy HOT 3 CLOSED

Hi @giogio33, thank you for all the context.

The logs show that:

1. Privacy.sexy is creating the script file, it's reading it back to trigger an antivirus to see if antivirus will delete it.
2. Privacy.sexy verifies that security scan was made possible and its not deleted.
3. It attempts to run the file, but can no longer find the file.

Some questions to understand whats going on:

1. Can you see any file at AppData\Roaming\privacy.sexy\runs? Which files do you see?
2. Do you run any other antivirus / security software other than Windows Defender?
3. Are you running Performance Mode docs 1, docs 2 on Defender?
4. Can you try running after turning of Real-Time protection?

from privacy.sexy.

Thank you for your reply.

In the AppData\Roaming\privacy.sexy\runs I see all generated scripts batch files.

Performance Mode I read is for Windows11 and I have Win10-22H2. Is that correct then I don't have it?

I turned off Emsi-Antivirus Software and in windows security I get the following (screenshot) without rebooting and still privacysexy won't run. I may tray something deeper but I cannot for a couple of weeks. I'll get back to you with it.

from privacy.sexy.

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 see that this can be resolved using double quotes + single quotes, double double quotes, using " instead of double quotes etc etc.

I will solve this in next patch. Thank you again for the guidance and bug report.

from privacy.sexy.