PowerRun is a portable freeware to launch regedit.exe , Cmd.exe or other software with the same privileges as the TrustedInstaller / Nt Authority/system Why would you need it? Sometimes it is not enough to just be running as Administrator, Maybe it’s a file or a registry key that is locked or not editable, PowerRun a tool with this powerful privilege most likely solve that , PowerRun doesn’t require any installation process or additional dll files.
What is New (Wednesday, 17 July 2024)
1. [Added] – Interface icons enlarged and alternative icon set added.
2. [Added] – Name column added to list.
3. [Added] – Cmd parameters usage has been restricted. (against harmful Apps)
4. [Added] – /SID parameter support added.
5. [Added] – /WAIT parameter support added.
6. [Added] – Feature to run Powershell script shortcuts with double click.
7. [Added] – Many features have been rewritten and improved.
How to use : After downloading, extract PowerRun to your desired location, then run it. You can drag and drop any files on it for example ; program files , Program files shortcuts , script files , text files usw. to run a listed file in TrustedInstaller/SYSTEM privileges you can select it and use run button or right click on it and choose “Run File” feature , the file will run with Highest privileges , you can check the Task manager’s details tab to verify that the selected file running under SYSTEM Privileges.
If you’re trying to edit or delete keys from the registry , you might find that some keys won’t let you do anything with them and you’ll get an error such as “Cannot delete xxxxx: Error while deleting key“. These keys are usually protected to stop accidental deletion , You could also be the administrator on the computer, but still can’t manipulate the required key.
Even though the administrator account has a great deal of control, there are other hidden accounts and levels on the system which have even greater access and therefore standard administrator privileges are not enough. To solve this problem, you have to force the registry to allow the logged on user full control of the subkeys in such cases PoweRun can help you : use the “Launch Registry Editor” button.
Copy desired registry key and click “Open” button , PowerRun will open regedit (with Highest Privileges) and jump to the key Automatically. If you want to add any parameter to listed script or program rigt click on it and use “Edit Item” or just use wrench Button.
For automation purpose PowerRun allows you to create a vbs or bat file with necessary parameters in it , to use this feature :
1. Select the Program.
2. And use Edit – Create bat/Vbs File feature.
Don’t forget to run the script in the same folder with PowerRun.exe or PowerRun_x64.exe.
Choosing between System or TrustedInstaller Privileges
In the Options menu, you can choose between System and System + TrustedINstaller permissions.
To see all supported command line parameters of PowerRun, use PowerRun.exe ? command or click File menu and select Command Line Info.
NOTE: PowerRun can not run only with “TrustedInstaller” privileges it can also run with “Nt Authority/system” privileges.
Supported operating systems: Windows 11 , Windows 10 , Windows 8.1 , Windows 8 and Windows 7
Supported languages: English , Turkish , German , Portuguese (Brazil) , Korean , French , Greek , Russian , Japanese , Polish , Spanish , Chinese (Simplified), Lithuanian, Italian
File: PowerRun_x64.exe │ Virustotal
MD5: 687ff0af42786f77ac2300fc532b8a44
SHA1: fc1b588d7b657639ddf5882c3de77b5cb36f6acf
SHA-256: bf10fc287e43244b4ba36a0f25aa87ea5490d7247c54b008aa23afdafc6e331b
File: PowerRun.exe │ Virustotal
MD5: ae11c0c1a0a3acbd7aa1ccffa24f31ad
SHA1: 31eca50f876f17158af43b7774a29e39f9edf1b6
SHA-256: 33ca26855c2732f0e807e1d1f11fe704efb9fbe95e67d113492cc6958986038c
Program runs under the system user, therefore the corresponding locations belong to it. for example it will show following location
HKEY_CURRENT_USER -> HKEY_USERS\S-1-5-18
Under HKEY_USERS, the location of the user can be detected and the relevant variables can be specified under the (HKEY_USERS \ ??? \ Volatile Environment).
“HKEY_CURRENT_USER”、”%USERPROFILE%”or any other environment variables about current user will go crazy when I use “PowerRun.exe xxx.bat”or”PowerRun.exe Regedit.exe /S xxx.reg”
Please add pdf manuals for each program.
Please Look at the command line info
Web Link …
Hi. How do we use PowerRun in a batch file to stop and/or start a Windows Service?
Giving it a try
Thank you for the correction , The both usage is correct /WD:”C:\”or “/WD:C:\”
we have done it for escape some Quotes. for example if you use it like this “/WD:C:\”
the quotes in parameter information has been automatically removing. we will correct our samples as examples 🙂
Thanks for your comment.
Hello !
Thanks for this cool app ! Greatly reduces the time, no need to do unnecessary reboots 🙂 !
I found one small typo in command-line help, called through “File -> Command Line Info”. In “Samples:” category fourth line “PowerRun64.exe /SW:2 “/WD:C:\” notepad.exe C:\test.txt”: before command-line parameter /WD must not be quotation mark. Should be correct /WD:”C:\”, not “/WD:C:\”.
And better replace “Samples:” on “Examples:”.
Thank your in advance !
How can I access protected dirs created by installed MS Store games? I can’t copy any file from there: Denied access all the time…
I want to ask, if there is a way in commandline-mode to run dos-commands like “rd” or “del” in directly the powerrun-mode:
I use a batch to delete directories, which are sometimes generated automatically – some of this directories have higher protection.
( I look for a solution and know, what I do, so please no hints that it may have a good reason when directories are protected)
Good day!
Thank you for the great app!
I have a question, maybe not quite in this topic.
I have 2 applications. I want them to run along with the system (preferably without opening a window – right in the middle). You will say that it is easier to place from the startup folder and they will post it with the system. No, it does not work! I tried various startup options through the registry: with user rights: for all users, with the highest rights. I also tried to create bat, cmd and run using PowerR un. But nothing gives success. This works with all other applications, but not with SpeedFan and ReCrypt. These applications refuse to run from me in any version (only manually). I also played with the location of the application folders. Can you advise something?
I would like to have an application (maybe you will create one) that would allow you to regulate the launch of applications when the system boots. Yes, many applications on this topic. But there is no simple application that would allow
1) to determine the launch to choose from: applications for the current user / all users;
2) determine the sequence of launching applications (delayed by timer) to speed up the launch of the system;
3) application launch options: in tray, with active window.
Some registry key seems open on working system there are some special programs to backup registry please use one of them.
Hi,
One month ago, I did a backup of my full registry.
Today, I tried to import that backup. No way to do this – not normally, not in Safe Mode. Not as Administrator… and not via your utility. Towards the end of the process, I get an error popup, saying in substance (I translate from Dutch):
“cannot import reg file: not all data are written to the registry. Some keys are used by the system or other processes or you are not authorized to execute this operation.”
Is there a way to overcome this via powerrun and as a “trusted installer” ?
Or should I look to other possibilities.
Please check the following picture
Web Link …
If that was true, then in ProcessExplorer, I would see the processes lauched by PowerRun as having the user: NT SERVICE\TrustedInstaller, but instead I see the processes launched by PowerRun having the user as: NT AUTHORITY\SYSTEM.
This happens despite TrustedInstaller=1 in PowerRun.ini
> Author wrote:
> Powerrun working as TrustedInstaller privileges in your system.
It is normal , Powerrun working as TrustedInstaller privileges in your system.
…that is Windows 7 x64 RTM (no SP1)