Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
UAC bypass techniques let code running as a standard administrator reach full administrative rights without showing a consent prompt, usually by hijacking a Windows binary that elevates silently.

What Are UAC Bypass Techniques?
User Account Control arrived with Windows Vista to solve a specific problem: almost everyone ran as administrator all the time. UAC splits an administrator’s logon into two tokens, a filtered one used for everyday work and a full one that requires consent to use. A UAC bypass is any technique that gets the full token without the consent prompt appearing.
Microsoft has been explicit that UAC is a convenience feature rather than a security boundary, and that bypasses are therefore not treated as security vulnerabilities. That position is defensible in design terms and unhelpful in operational terms, because attackers rely on these techniques constantly. MITRE ATT&CK tracks them as T1548.002.
Prompting for every administrative action proved unbearable, so Microsoft marked a set of signed Windows binaries as auto-elevating. These executables carry autoElevate set to true in their manifest, request requireAdministrator, live in a trusted directory such as System32, and are signed by Microsoft. When an administrator launches one, it receives the full token with no prompt.
The bypass follows directly: find an auto-elevating binary that reads something a standard user can write, and change what it reads.
The fodhelper.exe method is the canonical example and remains the one most often seen in commodity malware. The binary opens the ms-settings protocol handler, and protocol handlers are resolved from HKEY_CURRENT_USER before HKEY_LOCAL_MACHINE. An attacker creates the key HKCU\Software\Classes\ms-settings\Shell\Open\command, sets its default value to their payload, adds an empty DelegateExecute value, and runs fodhelper. The payload launches elevated, with no prompt and no administrator password.
The same shape appears repeatedly with different components:
mscfile handler under HKCU before falling back to the machine hive.%windir% from the user environment.The UACMe project catalogues more than seventy distinct methods. Microsoft fixes individual ones when they are widely abused, and new variants keep appearing because the underlying pattern, user-writable configuration consumed by an auto-elevating process, is structural.
A UAC bypass only works if the logged-on user is already a member of the local Administrators group. It converts a filtered administrator token into a full one; it does not turn a standard user into an administrator. That single fact determines the most effective defence.
What it does provide an attacker is significant: the ability to disable security tooling, install a service or driver, write to protected locations, read credentials from LSASS, and establish persistence that survives a reboot. Ransomware routinely uses one in its first minute on a host.
HKCU\Software\Classes\ for handlers such as ms-settings, mscfile, exefile, and Folder, especially with a DelegateExecute value. Sysmon events 12 and 13 cover this well and produce very few false positives.fodhelper.exe, eventvwr.exe, sdclt.exe, or computerdefaults.exe launching cmd.exe, powershell.exe, or an unsigned executable.Microsoft-Windows-UAC operational log.Three measures matter, in order of effect. First, stop issuing permanent local administrator rights to day-to-day accounts; a standard user cannot perform a UAC bypass at all, and privileged access management or just-in-time elevation gives administrators what they need without leaving the right in place. Second, set UAC to “Always notify” through the ConsentPromptBehaviorAdmin policy, which blocks many of the quieter techniques. Third, deploy application control with Windows Defender Application Control or AppLocker so the payload itself cannot run even when elevation succeeds.
Beyond that, enable Windows LAPS so local administrator passwords differ per machine, keep Windows updated so known methods stay closed, and make sure your endpoint detection product is configured to alert on the registry behaviour rather than only on known malware files. Cyber Essentials already requires that users do not routinely hold administrative privileges for ordinary work, which addresses the root of this issue directly.
Our Penetration Test Services include workstation build reviews that test exactly which of these techniques your standard image and endpoint tooling actually stop.
Microsoft does not classify it as one, on the basis that UAC is a convenience feature rather than a security boundary, and that anything running as an administrator is already on the same side of the boundary. Attackers use these techniques daily regardless, so treat them as a detection and configuration problem even though they will not receive a CVE.
No. Every technique requires the logged-on account to be a member of the local Administrators group, because the bypass converts a filtered administrator token into a full one. A standard user has no full token to reach. Removing permanent local administrator rights from everyday accounts therefore eliminates the entire technique family on those machines.
It stops many of them, including methods that rely on the auto-elevation of signed Windows binaries, because the highest setting prompts even for those. It is not complete coverage, since some COM-based and scheduled task methods behave differently. It is still worth setting as a deliberate policy rather than leaving the default, which prompts less often.
Monitoring registry writes under HKCU\Software\Classes for protocol and file handlers, particularly where a DelegateExecute value appears. Legitimate software almost never writes those keys, so the alert is high fidelity. Pair it with process creation alerts for auto-elevating binaries such as fodhelper.exe and eventvwr.exe spawning command interpreters.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.