How to Completely Disable ‘User Account Control’ (UAC) via Group Policy in Windows 11

User Account Control (UAC) is a fundamental security feature in Windows 11. By default, even if you are logged in as an Administrator, UAC forces your applications to run with standard user privileges. Whenever software attempts to make a system-level change—like modifying the registry or installing a driver—the screen dims and UAC displays a stark “Yes/No” prompt demanding explicit confirmation. While crucial for consumer security, UAC is a significant barrier to automated, unattended deployments. If you are orchestrating a server environment, executing complex login scripts, or running headless rendering nodes where an interactive prompt will permanently stall a critical workflow, UAC must be eliminated.

This guide explains how to completely disable User Account Control (UAC) via the Group Policy Editor in Windows 11.

Disable UAC via Group Policy

To bypass the UAC engine entirely and ensure administrative tokens are passed silently to all processes, we must configure a specific security policy. Note that the Group Policy Editor is only available on Windows 11 Pro, Enterprise, and Education editions.

  1. Log into Windows 11 with an Administrator account.
  2. Press the Windows Key + R to open the Run dialogue box.
  3. Type gpedit.msc and press Enter to launch the Local Group Policy Editor.
  4. In the left-hand navigation pane, carefully drill down to the following path:
    Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
  5. In the right-hand pane, scroll down to the bottom and locate the policy named User Account Control: Run all administrators in Admin Approval Mode.
  6. Double-click the policy to open its configuration window.
  7. Select the radio button next to Disabled.
  8. Click Apply, then click OK.
  9. Crucial Step: You must reboot the machine for this profound kernel-level change to take effect.

Verify the Policy Application

By disabling “Admin Approval Mode,” you are instructing the Windows kernel to immediately grant full administrative tokens to any process launched by an Administrator, completely bypassing the UAC broker.

To verify the lockdown is successful, log in after the reboot and attempt to launch an application that typically triggers UAC (such as the Registry Editor, regedit.exe, or an installer executable). The application will instantly launch and execute without the screen dimming and without presenting a confirmation prompt. Your machine is now primed for totally silent, unattended administrative execution.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.