How To Deactivate User Account Control (UAC) In Windows 11 And 10

Deactivating User Account Control (UAC) in Windows requires adjusting system elevation policies through the Control Panel, Local Group Policy Editor, or the Windows Registry. Modifying these settings suppresses security prompts during application installations and administrative configuration changes by altering the underlying Limited User Account (LUA) architecture. Complete deactivation via registry key adjustments bypasses Admin Approval Mode but disables specific system safeguards and Universal Windows Platform application dependencies.

System Requirements & Security Assessment for UAC Modification

Before altering User Account Control security parameters, system administrators and power users must evaluate the operational trade-offs between uninhibited administrative execution and endpoint protection. UAC acts as an essential security boundary that prevents unauthorized software from making silent background system changes.

Disabling UAC strips away the protection layer that forces malware to explicitly request elevated rights, meaning any executable running in an administrative user session automatically gains full kernel-level access privileges.

Technical Prerequisites and Operational Metrics

• Required System Permissions: Local Administrator credentials or Domain Administrator rights. Standard user accounts cannot alter elevation security settings.
• Essential Administrative Tools: Control Panel access (UserAccountControlSettings.exe), Windows Registry Editor (regedit.exe), Local Group Policy Editor (gpedit.msc available in Windows Pro, Enterprise, and Education editions), or Windows PowerShell elevated command console.
• Estimated Execution Time: 2 to 5 minutes for policy application, plus 1 minute for a required system reboot when performing complete architecture deactivation.
• Target Operating Systems: Windows 11 (all builds), Windows 10 (Builds 1507 through 22H2), and Windows Server (2016, 2019, 2022).
• System Impact Index: High risk of background security degradation; moderate impact on modern Windows infrastructure components such as Microsoft Store application runtime environments.

Comprehensive Workflows to Deactivate User Account Control

Select the configuration method that matches your environment deployment needs. Method 1 lowers notification prompts via the graphical user interface without destroying the Limited User Account architecture. Methods 2, 3, and 4 completely strip out Admin Approval Mode across the entire operating system.

Step 1: Adjust Notification Sliders via Control Panel (Standard GUI Method)

This method stops the dimming desktop background and silences pop-up elevation prompts while retaining background token virtualization for modern applications.

1. Press Windows Key + R to open the Run dialog window. Type UserAccountControlSettings.exe into the text field and press Enter.
2. Locate the vertical slider bar on the left side of the User Account Control Settings window. The slider features four distinct notification levels ranging from Always notify down to Never notify.
3. Click and drag the slider handle down to the lowest position marked Never notify.
4. Read the descriptive panel on the right side, which notes that this setting prevents programs from notifying you when they attempt to install software or make changes to the computer.
5. Click OK at the bottom of the window to confirm the policy change.
6. A final UAC elevation prompt will appear asking for confirmation to commit the change. Click Yes.

Pro-Tip: The "Never notify" GUI setting prevents confirmation pop-ups, but underlying process tokens still divide into standard and administrative privileges behind the scenes. This maintains compatibility with Universal Windows Platform (UWP) apps while eliminating user prompt interruptions.

Step 2: Disable Admin Approval Mode via Local Group Policy Editor

For enterprise deployments or domain environments, configuring system policies ensures settings remain standardized across multiple administrative users.

1. Press Windows Key + R, type gpedit.msc, and press Enter to open the Local Group Policy Editor console.
2. In the left-hand navigation pane, expand Computer Configuration, then expand Windows Settings, followed by Security Settings, Local Policies, and select Security Options.
3. Scroll through the policy list in the right-hand panel to locate the security policy named User Account Control: Run all administrators in Admin Approval Mode.
4. Double-click the policy entry to open its Properties dialog window.
5. Select the Disabled radio button option.
6. Click Apply, then click OK to save the changes.
7. Locate the policy named User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode, double-click it, set its value to Elevate without prompting, and click OK.
8. Close the Group Policy Editor window and restart the machine to enforce the security policy overhaul.

Warning: Disabling Run all administrators in Admin Approval Mode via Group Policy turns off the internal security architecture completely. This action requires a full system reboot to unload the active filtering drivers from memory.

Step 3: Turn Off UAC Completely Using the Windows Registry

If running Windows Home edition (which lacks gpedit.msc) or managing automated deployment scripts, editing the central registry hive permanently turns off Limited User Account functionality.

1. Press Windows Key + R, type regedit, and press Enter. Click Yes if prompted by UAC.
2. Navigate to the following registry key path using the address bar at the top of the Registry Editor window: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Locate the registry DWORD value named EnableLUA in the right-side detail pane.
4. Double-click EnableLUA to open its Value Data edit box.
5. Change the number inside the Value data field from 1 (Enabled) to 0 (Disabled).
6. Verify that the Base option remains set to Hexadecimal, then click OK.
7. Locate the DWORD value named ConsentPromptBehaviorAdmin within the same key folder. Double-click it and change its Value data to 0 to allow silent elevation.
8. Close the Registry Editor. A notification popup will appear in the Windows System Tray stating: Restart your computer to turn off User Account Control.
9. Reboot the computer immediately to clear active LUA security hooks.

Warning: Incorrectly editing registry values inside HKEY_LOCAL_MACHINE can cause operational instability. Ensure you export a backup of the System key folder prior to making manual numerical modifications.

Step 4: Deactivate UAC Programmatically via Windows PowerShell

System administrators can automate the registry modifications across local networks using elevated PowerShell commands.

1. Press Windows Key + X or right-click the Start Menu icon and select Terminal (Admin) or Windows PowerShell (Admin).
2. Verify that the command prompt title bar displays Administrator: Windows PowerShell.
3. Execute the following command on a single line to update the EnableLUA property: Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value 0
4. Execute the secondary command to suppress administrative consent dialog prompts: Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "ConsentPromptBehaviorAdmin" -Value 0
5. Verify the registry changes executed successfully by querying the item property value using this command: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA"
6. Execute the restart command to finalize system configuration changes: Restart-Computer

Technical Specifications and System State Comparisons

The table below details the precise operational behaviors, registry key state modifications, restart mandates, and system compatibility metrics associated with each deactivation vector.

Diagnosing and Fixing UAC Deactivation Anomalies

Scenario 1: UAC Settings Revert to Default Following System Reboot

• Root Cause: Active Domain Group Policy Objects (GPO) or local third-party security software (Endpoint Detection and Response / Antivirus agents) continuously enforce centralized security baselines, overwriting local registry changes upon system startup.
• Actionable Fix: Open an elevated command prompt and run gpresult /h gpreport.html. Analyze the resulting HTML report to identify which active GPO controls the policy User Account Control: Run all administrators in Admin Approval Mode. You must unbind or edit the policy from the Active Directory Domain Controller, or add a registry exclusion rule within your third-party endpoint protection suite.

Scenario 2: Built-in Windows Apps Fail to Open After Disabling UAC

• Root Cause: Universal Windows Platform (UWP) apps—including Microsoft Photos, Calculator, and the Microsoft Store—depend on security isolation namespaces created by Limited User Access (LUA). Setting EnableLUA to 0 completely breaks this security isolation layer.
• Actionable Fix: If app functionality is required, restore the LUA architecture while keeping notification pop-ups silenced. Re-enable EnableLUA by setting its registry value back to 1, but maintain ConsentPromptBehaviorAdmin at 0 (or leave the GUI slider down at Never Notify). Restart the computer to restore application access without prompting users.

Scenario 3: "Settings Are Managed by Your Administrator" Error in GUI

• Root Cause: The graphical UserAccountControlSettings.exe tool becomes grayed out or locked when a local or group security policy manually sets explicit values inside the Windows Registry.
• Actionable Fix: Open regedit.exe, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System, and check for custom user policies. Delete any conflicting keys under HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\System, then launch gpedit.msc and set all UAC policies back to Not Configured.

Scenario 4: Black Screen or System Freeze During Elevation Attempts

• Root Cause: The Secure Desktop feature (which switches the visual system display context to an isolated desktop thread to prevent screen-scraping malware from capturing input) is failing due to corrupt graphics driver hooks or remote desktop software conflicts.
• Actionable Fix: Disable the Secure Desktop prompt switch while leaving administrative elevation operational. Navigate to policy path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and set the DWORD PromptOnSecureDesktop to 0. This forces elevation prompts to display on the active user interactive desktop without dimming or freezing the display output.

Frequently Asked Questions

Is it safe to permanently deactivate User Account Control?

Deactivating UAC increases overall system attack surfaces because malicious executables gain the ability to launch silent operations with elevated kernel privileges. For non-isolated workstation environments, keeping the slider on default settings or using the Never Notify GUI option provides better baseline security than setting EnableLUA to zero.

What is the difference between setting the UAC slider to Never Notify and setting EnableLUA to 0?

Setting the GUI slider to Never Notify leaves EnableLUA set to 1, which silences screen prompts while maintaining basic background token segregation and UWP app stability. Setting EnableLUA to 0 completely destroys the privilege separation layer, requiring a system restart and completely disabling UAC driver checks.

How do I re-enable UAC if administrative permissions are blocked?

If an account loses administrative access after altering security keys, boot Windows into Safe Mode by holding down the Shift key while selecting Restart from the Start Menu. Once in Safe Mode, log into the built-in emergency Administrator account, launch regedit.exe, set EnableLUA back to 1, and restart normally.

Why do Microsoft Store apps stop working when UAC is completely turned off?

Microsoft Store apps rely on restricted execution sandboxes enforced by the Windows Security Reference Monitor. Completely turning off UAC (EnableLUA = 0) eliminates these system containment rules, causing Windows to block store apps from running to prevent unauthorized security breaches inside standard user directories.

Can I disable UAC prompts for specific trusted programs only?

Yes, you can bypass UAC prompts for specific application executables without deactivating UAC system-wide. Create a scheduled task inside the Windows Task Scheduler configured with the option Run with highest privileges, then generate a desktop shortcut that executes the task using schtasks.exe /run /tn "TaskName".

Optimize Your Windows System Security Architecture

Properly managing User Account Control settings balances user productivity with operational security across standalone and enterprise Windows environments. If you are managing multiple enterprise endpoints, implement baseline configuration policies via Active Directory Group Policy Objects to maintain system stability without sacrificing administrative oversight.