>_RunAsUser
GitHub

Fix "User Installer is not meant to be run as Administrator"

One-click solution. No registry edits.

Works with VS Code, Cursor, Antigravity, and other Electron apps.

Also fixes: "Updates are disabled because you are running as Administrator"

Quick Fix (Recommended)

Step 1: Download the universal fix tool

Step 2: Drag & drop your installer onto the .bat file

setup.exe
→ drag onto →
RunAsUser_Fix.bat

Works with any installer from any folder!

> How to Use

01

Place files together

Put the .bat file in the same folder as your installer

Step 1: Files in folder
02

Drag installer onto .bat

Drag the .exe file onto the RunAsUser_Fix.bat icon

Step 2: Dragging file
03

Drop & Done!

Release to run installer without admin conflicts

Step 3: Drop to run

Note: Do NOT double-click the .bat file first. Drag the .exe directly onto the .bat icon in File Explorer.

> FAQ

What error does this fix?
This User Installer is not meant to be run as an Administrator error message

This tool fixes the "This User Installer is not meant to be run as an Administrator" error that appears when running user-scope installers with elevated privileges.

What does runas /trustlevel:0x20000 do?
This command runs a program with "Basic User" privileges, even if you're logged in as an administrator. The 0x20000 trust level forces the program to run without elevated (admin) privileges, bypassing the UAC admin token inheritance.
Is this safe to use?
Yes! This uses Windows' built-in runas command. It doesn't modify any system files or registry settings. It simply tells Windows to run your installer with standard user permissions instead of administrator privileges.
Which programs does this work with?
This fix works with any "User Installer" type applications, including:
  • Visual Studio Code (User Setup)
  • Cursor IDE
  • Antigravity
  • Any Electron-based app with user-scope installer
Why does this error happen?
"User Installers" are designed to install programs in your user profile folder (like %LOCALAPPDATA%) without needing admin rights. When you run them as administrator, Windows tries to install to the Administrator's profile instead, which causes conflicts with updates and permissions.
Technical Info

$ # How it works

Windows UAC creates two tokens for admin users: an elevated token and a basic user token. The runas /trustlevel:0x20000 command forces a process to use the basic user token, effectively "de-elevating" your privileges.

$ # Trust Levels

0x20000 = Basic User (what we use)
0x40000 = Administrator