Skip to content

blocked powershell command #42

Answered by m417z
shmu26 asked this question in Q&A
Discussion options

You must be logged in to vote

Looks like your PowerShell is configured to use the PowerShell Constrained Language Mode. The snippet, based on this, that failed to run during setup was supposed to allow running Windhawk without showing the UAC dialog. It's only for convenience and not very important, but if you'd like that functionality, you can disable PowerShell Constrained Language Mode, run cmd as administrator, and run the following command manually:

powershell -ExecutionPolicy Bypass -command "& {$ErrorActionPreference = \"Stop\";$scheduler = New-Object -ComObject \"Schedule.Service\";$scheduler.Connect();$task = $scheduler.GetFolder(\"\").GetTask(\"WindhawkRunUITask\");$sec = $task.GetSecurityDescriptor(0xF);$sec

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by shmu26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants