Microsoft calls running Windows with a standard user account the recommended and more secure method. If you must be an administrator, UAC's Admin Approval Mode still runs your apps with a standard token until you approve elevation. The risk grows when you click through prompts without reading them.
How UAC works
Microsoft says UAC reduces malware risk by limiting the ability of malicious code to execute with administrator privileges. Each application that needs the administrator access token must prompt the user for consent. Child processes inherit the token from the parent, but both must be at the same integrity level.
When an administrator signs in, two tokens are created: a standard user token and an administrator token. The standard token is used to start apps that do not perform admin tasks and to run explorer.exe. Because explorer.exe is the parent of user-started processes, everything runs as a standard user unless you approve otherwise.
Two modes
Standard user. When a task needs admin rights, you get a credential prompt and enter an administrator's credentials. Microsoft recommends this for a managed environment.
Administrator in Admin Approval Mode. You get a consent prompt and approve with a click.
The difference is what a stray click can do. A consent prompt answered by habit gives malware elevation. A credential prompt forces a pause.
Reading the prompt
Prompts are colour-coded. A gray background means a Windows administrative app or one signed by a verified publisher. A yellow background means the app is unsigned or signed but not trusted. Developer tools you compile yourself will often be unsigned, so yellow prompts are common for you, which is exactly why you should read them.
The secure desktop is on by default: the screen dims and only Windows processes can reach the prompt. Microsoft recommends keeping the policy that switches to the secure desktop enabled.
A practical setup for developers
- Use a standard account for daily work: editor, browser, terminal, builds.
- Keep a separate administrator account for installs and system changes.
- Put project work in a folder your standard user owns, so builds do not need elevation.
- When a build asks for admin rights, stop and find out why.
- Prefer per-user installs of tools where the tool supports it.
Some tools genuinely need admin for things like driver installs or virtualisation features. Handle those as one-off elevations, not as a reason to stay admin permanently.
What UAC does not do
Microsoft is clear that malware must first be on the machine for a fake prompt to matter, and that processes needing an admin token cannot silently install while UAC is on. UAC does not protect your user-level data. Anything running as you can read your repositories, your tokens and your browser profile. Keep secrets out of plain files and scan your projects. Safeguard's free scan at gold.safeguard.sh/scan can check a repository's dependencies.
Quick check
Does an administrator account run everything with full rights?
No. Microsoft says apps run with a standard user token unless the user approves elevation.
What does a yellow UAC prompt mean?
Microsoft says the app is unsigned or signed but not trusted.
Sources
Last reviewed: 19 October 2026.
