Every Windows user eventually encounters restrictions when trying to edit or modify elements in the operating system, even with administrator privileges. In fact, the administrator profile is not the most 'powerful' in Windows; there is a higher path known as TrustedInstaller. TrustedInstaller usually protects the user from themselves, but sometimes it gets in the way and complicates certain tasks. The application PowerRun allows us to run specific applications under TrustedInstaller and thus avoid any blocking.
Let's assume two very important things before continuing: First, that you want to edit or delete a system file or a registry key that throws access errors, and second, that you know exactly what you are doing. Windows is sometimes a real headache, but we can't deny its ability to preserve its integrity. Of course, some errors become irreversible, leaving the user trapped between an unusable computer and the 'nuclear option'. However, there are problems that are caused by a simple permission conflict, or rather, 'who owns' the file or key in question.
Running as TrustedInstaller
The administrator profile in Windows is not like the superuser or root in Linux. While misuse of root can knock out a distro, the Windows administrator allows some things... and others not. The first barrier for an administrator with strange intentions is the TrustedInstaller user account, dependent on the Windows Modules Installer service, which usually regulates the installation of hotfixes in Windows, and other secondary functions.
Now, if TrustedInstaller becomes the 'owner' of a file, folder, or registry key, it is not so easy to convince it to release control (there is an effective but tedious manual process), unless we use a tool like PowerRun. Basically, what PowerRun does is run an application or process chosen by the user under TrustedInstaller. When we see that process in Task Manager, it does not appear started by our user, but under the label 'SYSTEM', which is equivalent to higher privileges than we can get as a normal administrator. In its factory configuration, PowerRun opens the Registry Editor, but with a small edit of its .ini file, you can change it to whatever you need, say cmd.exe.
PowerRun is lightweight, efficient, and portable, but remember: TrustedInstaller should not be taken lightly. If something is stuck in the operating system, like temporary files left behind by an Office uninstall or similar, then PowerRun can bring some order. The same applies to certain malware variants that manage to alter permissions and 'bury' themselves among system files. Personally, I hope you never need PowerRun, but if you get to that situation, the link is below.
Official site and download: PowerRun
