PsExec could not start powershell about windowsappsunfukker HOT 4 OPEN

At that point, it's beyond my reach. You could use Process Monitor to investigate where is PsExec trying to look and why it's not resolving it. Other people have also recommended PAExec instead, maybe give that a try.

from windowsappsunfukker.

It means Powershell cannot access the path to the script. In my experience, the usual culprit is network drives. I would say, try to move the script to a different drive.

from windowsappsunfukker.

@AgentRev Hey, thanks for responding. I don't actually have any network drives. Just two SSDs and two HDDs, all local. I have tried moving the script to different locations on every drive, but it's the exact same error every time.
If you'd like to see any log file or system information that might help you identify the issue, I'd be happy to provide it. I really have no idea what's going wrong.

from windowsappsunfukker.

It wasn't PowerShell being unable to access the path to the script; it was rather PsExec being unable to access PowerShell.

I just added the full path to powershell.exe in the command, and it ended up working.

So, instead of

.\psexec.exe -s -i powershell -ExecutionPolicy Bypass -File "C:\WindowsAppsUnfukker-main\WindowsAppsUnfukker.ps1

I used

.\psexec.exe -s -i "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -ExecutionPolicy Bypass -File "C:\WindowsAppsUnfukker-main\WindowsAppsUnfukker.ps1

(I guess my environment variables are messed up as well? Because I had to add the System32 folder to "Path" under User Variables for takeown command to work when I was manually trying to fix the permissions earlier.)

from windowsappsunfukker.