Commands without account names
If exactly one administrator account is stored, the program command alone is enough for an elevated launch. User names and passwords then need not be included in scripts or shortcuts.
eXecute Under User Context
xucRun
xucRun launches Windows programs under an administrator account or another Windows account. Stored credentials avoid repeated password entry. Any UAC confirmation required by Windows for the specific launch remains required. Every launch using stored credentials must be covered by an active approval or confirmed in a dialog. Commands can be invoked interactively or by script.
xucRun is open-source software under development. The current state may contain defects, differ from the described behavior, and change. It is intended for experienced home users and developers on self-managed Windows PCs, not for systems requiring an elevated level of protection. Use is at the user's own responsibility. Read about intended use, protection boundaries, and liability.
PS C:\Tools> .\xucRun.exe regedit.exe
C:\Tools>xucRun.exe regedit.exe
Typical workflow
Elevated launch with account switch
Stored administrator account found
Credential checked against approval
UAC confirmation granted
Program started with elevated privileges
Windows functionsAccount switching and UAC
Separate storageNo password transfer to target programs in the intended workflow
Interactive approvalsSelected in the dialog as one-time or reusable
Purpose and functionality
Account switching and optional privilege elevation.
xucRun covers several use cases in which a program is to run with elevated privileges or under another user account, with or without elevation. A central use case is launching selected programs for administrative tasks from a standard user account. Commands can be invoked from scripts, batch files, fixed shortcuts, and custom commands in configurable file managers.
Paths and special characters
xucRun handles program paths, working directories, batch files, and common shell special characters and passes them to the target program.
Interactive dialogs
Dialogs are used to set up and select accounts and to approve program launches.
Windows functions in one workflow
xucRun uses existing Windows functions for account switching and UAC elevation in a common workflow for program launches.
Safeguards
Passwords are managed separately from normally launched programs.
xucRun uses Windows APIs to store passwords. In the intended workflow, passwords are not passed through the command line or to the target program. Password entry and approvals take place on a separate Windows desktop. A per-user security identifier helps users recognize subsequent xucRun dialogs there.
Protection boundary: On a compromised system, xucRun cannot provide comprehensive protection. In addition, calling scripts and configuration files must be trusted and protected against unauthorized modification.
UAC remains UAC
If Windows requires UAC confirmation for a specific elevation, it remains part of the launch process. xucRun does not replace it with its own approval. The UAC prompt that Windows actually displays depends on the specific launch path and Windows configuration.
Launches bound to path and hash
Approvals for a specific target program bind its final resolved path and SHA-256 hash. If the bound program file changes, the previous approval no longer matches. General approvals do not have this program binding.
Use requires approval
xucRun uses stored credentials only for a launch covered by an active approval or approved by the user in the current dialog. Without approval, the launch does not proceed.
Choose the balance between convenience and narrow scope
Longer and broader approvals avoid repeated xucRun approval decisions more often. Shorter approvals or approvals bound more precisely to a program, invocation, and target account limit how broadly they can be reused. For a reusable approval, this differentiated selection generally needs to be made only once.
Approvals with optional tighter binding
Reusable approvals can additionally be bound to the arguments, working directory, and launch visibility. Directly recognized scripts can be included in this binding; content loaded later is not included.
Installation and setup
Verify the release and set up xucRun.
The Core installer automatically creates a local xucRun certificate on your computer and uses it to sign the components to be installed. Before installation and during later use, xucRun verifies the signatures of the matching components. This makes subsequent changes detectable while keeping permanent trust limited to your computer; the developer certificate is not installed there as a trust anchor. The local-signing guide explains the details.
-
1
Install xucRun
All required xucRun components are installed locally on your Windows system.
-
2
Store a credential
Required credentials are requested on a separate Windows desktop when needed and can also be set up in advance.
-
3
Approve and launch a program
If no matching approval is active, the launch is confirmed interactively.
.\xucRun.exe regedit.exe
Usage examples
Examples of program launches.
These examples assume that xucRun is installed and the required accounts have been set up. If no matching approval exists, xucRun asks interactively before launch.
Launch Registry Editor with elevated privileges
If exactly one administrator account is stored, the target command is sufficient. Any UAC confirmation required by Windows for this elevated launch remains required.
.\xucRun.exe regedit.exe
Launch a program under a specific account
/user: selects the specified account without xucRun requesting additional elevation itself.
.\xucRun.exe /user:DOMAIN\User notepad.exe
Call a batch file from a script
Paths, arguments, and common shell special characters are passed to the batch file in a controlled way.
.\xucRun.exe "C:\Scripts\Maintenance & Check.bat"
Replace the current console
Without a target program, xucRun detects the calling console, starts the same console type in the selected account and elevation context, and preserves the current working directory. Command Prompt, Windows PowerShell, PowerShell, and TCC are supported.
.\xucRun.exe
.\xucRun.exe /user:<Account>
Integrate with other applications
xucRun can be invoked from configurable file managers, scripts, desktop shortcuts, and other applications to start programs with elevated privileges or under another account. The documentation includes, among other examples, a complete configuration example for Total Commander.
Questions before use
Management commands, backups, update behavior, and further technical details are covered in the README.
How can I review and assess xucRun?
Source code and documentation are publicly available so that the technical measures, their limitations, and remaining risks can be reviewed. Publication is neither a security guarantee nor evidence of an independent audit; xucRun has not been independently audited or certified. Before use, review the source code, SHA-256 checksums, intended use, and documented security limitations, and use xucRun only if the remaining risk is acceptable for your use case.
What data does xucRun store, and where?
xucRun uses Windows APIs to store passwords, approvals, security markers, associated metadata, and created backups on the local computer. Backups may also contain a description entered by the user. In the intended workflow, stored passwords and security markers are not passed to normally launched programs. These product data can be removed completely during uninstallation.
Why does xucRun require a Windows service?
The Windows service manages stored passwords separately from the normally launched xucRun program. It checks every requested launch and starts the program under the selected account. Required approvals and UAC prompts remain visible to the user and must still be confirmed. The service creates no additional privileges.
Which systems and runtime components are required?
xucRun supports Windows 10 and Windows 11 on x64 systems. Other Windows versions and ARM64 systems have not been tested and are not supported. The latest Microsoft Visual C++ v14 Redistributable for x64 is also required; xucRun needs no additional third-party service. If the runtime is missing, the installer offers download, selection of an existing vc_redist.x64.exe, or cancellation.
Does xucRun bypass User Account Control?
No. xucRun combines existing Windows functions, creates no additional privileges, and does not replace UAC with its own approval. For elevated cross-account launches, Windows must provide a confirmable UAC path for the selected administrator account; otherwise, the launch remains blocked. This can particularly affect the built-in Administrator account when Admin Approval Mode is disabled.
Why does xucRun use local signing?
The published package is signed with a self-signed developer certificate. Without local re-signing, this certificate would have to be installed permanently as a trusted root certification authority and trusted publisher on every target computer. Windows would then trust every file signed with the same developer certificate.
The Core installer verifies the digital signatures, creates or reuses a local certificate with a non-exportable private key, and re-signs the components. Permanent trust is thereby limited to the individual computer. Local signing does not establish the origin of the download, so the published SHA-256 checksum must be compared first. Local signing in detail
xucRun for Windows
Releases and source code.
xucRun and the optional Tray are published as open-source projects on GitHub. The Tray adds a status and control interface in the Windows notification area.
Installation files, checksums, and release notes are listed on the download page. Source code, license texts, and technical documentation are maintained in the respective GitHub repositories.
Important: Before downloading or using the software, read the information about intended use, security limitations, and potential risks.