This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 13%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
We blocked the powershell using GPO "Don't run specified Windows applications" but if a user rename the powershell.exe to something else then he is allowed to run it. We found another method in URL "https://activedirectorypro.com/disable-powershell-with-group-policy/" , It is blocking the path "C:\Windows\System32\WindowsPowerShell\v1.0" which means user can it from a different location. Wondering if anyt=one has blocked it using group policy and which method did you use. Please suggest
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 1%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Block the hash using the same GPO entry - just select "New hash" instead of "New Path" - then browse to powershell.exe. Also do a second hash entry for powershell_ise.exe
The benefit of a hash rule is it will block the file no matter its location.
For example, if PowerShell tried to run from c:\it\ it would be blocked due to the hash rule, not the file path.
The only drawback to this is you would need a hash rule for every version of PowerShell.
Further info here: https://activedirectorypro.com/disable-powershell-with-group-policy/
We finally disabled it using Beyond Trust app