Become Trusted Installer with the power of PowerShell!
The Classic PS1 script format will soon be replaced by a in-house Engine. The rollout of BTI core 1-5 built on this new Engine has started with GUI.1.2. IN ORDER FOR THIS TO WORK, YOU HAVE TO ENABLE SCRIPT RUNNING IN THE WINDOWS DEV SETTINGS
All my Implementation in this repository is based on the fantastic research by tyrannid (https://www.tiraniddo.dev/ https://github.com/tyranid)
The executable contains all neccesary code to execute both legacy PS1 scripts and newer C# integrated PS-Actions
These work by directly injecting into PowerShell, negating the need for a file and increasing security and speed.
Most parts of the executeble are for cosmetic purposes and a wrapper for older CLI code still left within.
- create installer
- update GUI/ WinUI implementation
- pack everything into one executable
The Windows users out there will probably know the pain of wanting to delete a file in system directories only to find it protected by Microsofts dreading TrustedInstaller.
This script uses PowerShell to "impersonate" TrustedInstaller.
In order to properly use trustedinstallers permissions, we need a proper way to get information from "TrustedInstaller.exe". Also, we need to create a new (child-)process. NtObjectManager is a Powershell Library by Google to do such things. Installdependencies installs said modules version 1.1.20.
These three scripts all do pretty much the same. They use NtObjectManager to get the processname from TrustedInstaller.exe to create a child process of it. By doing so, you get a Powershell/CMD or File Explorer window/terminal with TrustedInstallers permission.
Start / Stop the TrustedInstaller Service
