-
Yesterday I installed WIndhawk -- awesome! -- and today I noticed in logs that something got blocked. Is this something I need to fix or be concerned about?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
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 = $sec + '(A;;GRGX;;;AU)';$task.SetSecurityDescriptor($sec, 0)}" -FFFeatureOff |
Beta Was this translation helpful? Give feedback.
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: