Trusted Installer Launcher is a powerful tool that allows you to run files, folders, and programs with TrustedInstaller (TI) privileges - the highest permission level in Windows systems. It offers ease of use through both drag-and-drop functionality and system integration. This file allows you to use TrustedInstaller privileges with Windows' built-in code (cmd + powershell) without needing any other application. ✨ Features Drag-and-Drop Interface: Run any file with TI privileges by dragging it onto the script System Integration: Adds "Open with Trusted Installer Privileges" option to Windows context menu Multi-Language: Turkish and English language support (automatic detection) Wide File Support: EXE, BAT, CMD, REG, PS1, MSC, CPL and more ️ Secure: Uses the original Trusted Installer mechanism User-Friendly: Easy to use with graphical popup menus What Does It Do? Some system files, folders and services in Windows cannot be edited even with Administrator privileges. These files are protected by TrustedInstaller. This tool: Allows you to edit system files Allows you to edit system services Provides access to protected folders Facilitates system registry modifications Enables operations with even higher privileges than Administrator Installation Download the Script: Download TrustedInstaller.bat Run the Script: Double-click the file Choose Install: Select "NO" (Install to System) from the menu Confirm: Approve the UAC (User Account Control) prompt After installation: Script is copied to C:\Windows\ti.bat "Open with Trusted Installer Privileges" option is added to context menu of all files and folders Usage Methods Method 1: Drag-and-Drop 1. Select the file you want to run 2. Drag it onto TrustedInstaller.bat 3. File runs automatically with TI privileges Method 2: Context Menu (After Installation) 1. Right-click any file/folder 2. Select "Open with Trusted Installer Privileges" 3. Approve the UAC prompt Method 3: Manual Launch 1. Double-click the script 2. Select "YES" option 3. Choose to open CMD or Explorer with TI privileges Supported File Types Type Description Example .exe Executable files notepad.exe .bat Batch scripts setup.bat .cmd Command files install.cmd .reg Registry files tweaks.reg .ps1 PowerShell scripts script.ps1 .msc MMC Snap-ins gpedit.msc .cpl Control Panel sysdm.cpl ⚠️ Warnings Use Carefully: TrustedInstaller privileges can modify system files Backup: Make backups before important system changes Trusted Source: Only run files you trust with TI privileges System Knowledge Required: Don't modify system files without knowing what you're doing ️ Uninstallation Run the script Select "NO" (Install to System) In "Already installed" message, select "NO" (Uninstall) All files and registry entries will be cleaned Technical Details Hybrid Script: Batch + PowerShell (minimum versiyon 2.0) combination Platform: Windows 7, 8, 8.1, 10, 11, Server (Server 2008 R2 and and above) Architecture: x86 and x64 compatible Permission System: Based on Windows TrustedInstaller service Registry Locations: HKCR\*\shell\RunAsTI HKCR\Directory\shell\RunAsTI HKCR\Directory\Background\shell\RunAsTI What's New & Improvements (26.08.2026) Added High-DPI Awareness Support: Integrated the SetProcessDPIAware API for all user interface windows (progress bars, message boxes, etc.) running at the script level. Completely resolved the issue of blurry text and UI elements on modern 2K/4K monitors or devices utilizing custom display scaling (e.g., 125%, 150%). All windows are now rendered at their native resolution with crystal-clear sharpness. Security & Privileges Activated Advanced Operating System Permissions (Process Token Privileges): All core-level account permissions that are typically "Disabled" upon execution have been forcefully switched to the "Enabled" (Active) state within the process token. Key Privileges Acquired: SeLoadDriverPrivilege: The ability to load and unload hardware device drivers in the background. SeTakeOwnershipPrivilege & SeRestorePrivilege: The absolute power to take ownership of and restore stubborn, undeletable, or locked system files and directories. SeSystemtimePrivilege: The authority to modify the system clock. SeLockMemoryPrivilege: The capability to lock memory pages in RAM. Result: The backend infrastructure is now fully empowered to operate without restrictions, utilizing the maximum extent of access rights granted by the operating system. Link: https://github.com/abdullah-erturk/Trusted-Installer-Launcher/
well, if you use stuff from aveyo github you can give credit which is more than fair Code: https://github.com/AveYo/LeanAndMean/blob/main/RunAsTI.ps1
The TrustedInstaller.bat file has been updated. ### Changes made to `TrustedInstaller.bat` - **Extended `RunAsTI` function signature** - Before: `function RunAsTI ($cmd)` - Now: `function RunAsTI { param($cmd, $targetName) }` - Purpose: Pass the file/folder being processed into the function. - **Made `PleaseWait` message dynamic based on target name** - Inside `RunAsTI`, using `$targetName`: - If the path is valid, it uses `Split-Path -Leaf` to get just the name (`setup.bat`, `Documents`, etc.). - For Turkish: - `X için Trusted Installer etkinleştiriliyor, lütfen bekleyin...` - `Bu ekran otomatik kapanacaktır.` - For English: - `Trusted Installer is being activated for X, please wait...` - `This window will close automatically.` - **Connected drag‑and‑drop / context menu calls to `RunAsTI` with the target path** - Drive (e.g. `C:\`) → `RunAsTI $driveCmd "C:\"` - Folder → `RunAsTI $folderCmd $fullPath` - File (exe/bat/cmd/ps1/reg/msc/cpl, etc.) → `RunAsTI $cmdToRun $fullPath` - In the UI, “open Explorer in script directory” → `RunAsTI "explorer.exe ... " $explorerPath`. - **Prepared dynamic `PleaseWait` text before showing the popup and kept a safety timeout** - Right before starting the popup, `$msg.PleaseWait` is updated according to the target name. - The separate timeout script that auto‑closes the popup still exists as a backup: - Final form: `Start-Sleep -Seconds 10` (so even if the payload fails, the popup closes in ~10 seconds at most). - **Added active popup closing right after the TI target program is started** - Inside the TI payload, after the target command (`cmd`, `explorer`, exe/bat, etc.) is started and a short `Start-Sleep`: - It reads `TI_WaitPopup_PID.txt`, finds the PowerShell process that shows the popup, and kills it with `Stop-Process`. - It deletes `TI_WaitPopup.ps1`, `TI_WaitPopup_Timeout.ps1`, and the PID file. - Result: Once the program is actually started with TI rights, the info popup automatically closes after a brief delay. - **Removed the extra CMD window for third‑party EXE programs** - Before: When `$ti` was true, even pure EXE commands were run via `cmd /c ...`, causing an extra console window. - Now: - If `$cmd` matches a pure EXE path (`C:\...\Program.exe`), then: `Start-Process -FilePath $exePath -WorkingDirectory $exeDir` is used to start the EXE **directly**, without CMD. - Non‑EXE or complex command lines (`.bat`, `.cmd`, `reg import`, `powershell ...` etc.) still run through `cmd` as before, because they need a shell. - **Shortened the sleep times inside the TI context** - Before: `if ($isExplorer) { Start-Sleep 3 } else { Start-Sleep 2 }` - Now: For both Explorer and other commands: `Start-Sleep -Seconds 1` - Purpose: Reduce the extra delay before the popup closes after the program is launched, especially on Windows 7, and make the experience closer to Windows 10/11. - **Updated the comment around the popup start logic** - The old wording “5 seconds timeout” was adjusted to reflect the new behavior, which is now dynamic and tied to the TI process, with the 10‑second timeout script kept only as a safety fallback.
It would be great if it could be done purely through the registry (without relying on other PS1 or BAT files)
Trusted Installer Launcher has been updated. Changes: What's New & Improvements ✨ Improvements Added High-DPI Awareness Support: Integrated the SetProcessDPIAware API for all user interface windows (progress bars, message boxes, etc.) running at the script level. Completely resolved the issue of blurry text and UI elements on modern 2K/4K monitors or devices utilizing custom display scaling (e.g., 125%, 150%). All windows are now rendered at their native resolution with crystal-clear sharpness. Security & Privileges Activated Advanced Operating System Permissions (Process Token Privileges): All core-level account permissions that are typically "Disabled" upon execution have been forcefully switched to the "Enabled" (Active) state within the process token. Key Privileges Acquired: SeLoadDriverPrivilege: The ability to load and unload hardware device drivers in the background. SeTakeOwnershipPrivilege & SeRestorePrivilege: The absolute power to take ownership of and restore stubborn, undeletable, or locked system files and directories. SeSystemtimePrivilege: The authority to modify the system clock. SeLockMemoryPrivilege: The capability to lock memory pages in RAM. Result: The backend infrastructure is now fully empowered to operate without restrictions, utilizing the maximum extent of access rights granted by the operating system.
@mephistooo2, thanks for your very good tool Trusted installer launcher. I tested your tool Trusted installer launcher in different scenarios and came across two problems: 1. If a file is written in Cyrillic - your tool does not work/does not react/nothing happens. 2. Since I wrote that I tested your tool in different scenarios - I was trying to launch an mp4 file with your tool. Your tool launches it with Windows media player. I have associated these types of files to be opened with Pot player and as an example: From the keyboard I press the Enter key once on the specific mp4 file and Pot player launches (which is the correct behavior). And here my problem is - why does Trusted installer launcher launch Windows media player without me having the opportunity to choose another player or why does Pot player not launch?! For clarification: I absolutely never use Windows media player.
Trusted installer launcher has been updated. https://github.com/abdullah-erturk/Trusted-Installer-Launcher