UAC prompts stopped appearing? In most cases it’s caused by a setting, policy, corrupted system file, or a third‑party tool — not a mysterious Windows bug. This article explains why UAC doesn’t work in Windows 10, and gives step‑by‑step fixes so you can restore normal protection.
You’ll learn the eight most common causes (from simple slider settings to group policy and missing system files), how to diagnose each cause, and the exact commands, registry keys, and menus to fix them safely.
Key Takeaway
Re-enable UAC by checking the User Account Control slider, ensuring the built‑in Administrator account isn’t used, undoing Group Policy or registry changes that disable UAC (EnableLUA), repairing missing system files (SFC/DISM), and removing interfering third‑party security tweaks — then restart. Most UAC problems are fixed by restoring EnableLUA and running sfc /scannow.
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| UAC slider set to Never notify | Open Control Panel > User Accounts > Change User Account Control settings and move the slider up at least one notch. |
| Built-in Administrator account enabled | Disable the built‑in admin: net user Administrator /active:no (Admin cmd). |
| Group Policy overriding UAC | Run gpedit.msc and enable Admin Approval Mode and related policies, then gpupdate /force. |
| Registry UAC keys misconfigured | Check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and set EnableLUA = 1. |
| Third‑party antivirus/security interfering | Temporarily disable or uninstall the security tool and test UAC; check vendor docs. |
| Missing/corrupted Consent.exe or system files | Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth; restore C:\Windows\System32\Consent.exe if missing. |
| Explorer or shell running elevated | Log out and log back in (or restart) to return Explorer to normal; avoid launching shell with elevated token. |
| Tweaker tools or malware disabled UAC | Uninstall tweakers, run full malware scans (Windows Defender or Malwarebytes), and restore registry defaults. |
Detailed Fixes for “tu mets ici le problème du 8 reasons why UAC doesn’t work in Windows 10 (and how to fix it)”
This section walks through each cause with explanations and step‑by‑step solutions.
1) UAC slider set to Never notify
Why it causes the problem
The UAC slider in Control Panel controls when Windows shows consent prompts. Setting it to Never notify effectively disables prompts for most actions.
Step-by-step solution
- Open Control Panel (press Win + R, type control, Enter).
- Go to User Accounts > Change User Account Control settings.
- Move the slider up to at least the second notch (“Notify me only when apps try to make changes to my computer (default)”) or the highest notch for strictest protection.
- Click OK and restart Windows if prompted.
Notes/Tips: If the slider is greyed out, a policy or registry change may be forcing the state — continue to the Group Policy and Registry sections below.
2) Built-in Administrator account enabled
Why it causes the problem
The default built‑in Administrator account runs with full admin privileges and, by design, does not receive UAC prompts. If you’re logged into that account, UAC appears disabled.
Step-by-step solution
- Check account type: open Settings > Accounts > Your info or go to Control Panel > User Accounts.
- To disable built‑in Administrator, open an elevated Command Prompt: press Win, type cmd, right‑click Command Prompt, select Run as administrator.
- Run: net user Administrator /active:no
- Sign out and log into a standard administrative user account (one created during setup) or restart.
Notes/Tips: If you need the built‑in admin for repair work, re-enable temporarily with net user Administrator /active:yes, then disable it again.
3) Group Policy overriding UAC
Why it causes the problem
Domain or local Group Policy settings can force UAC off or change how consent prompts behave (for example, turning off Admin Approval Mode).
Step-by-step solution (local policy)
- Press Win + R, type gpedit.msc, Enter (Windows 10 Pro/Enterprise).
- Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
- Find User Account Control: Run all administrators in Admin Approval Mode and User Account Control: Behaviour of the elevation prompt for administrators in Admin Approval Mode.
- Ensure Run all administrators in Admin Approval Mode is Enabled and set prompt behavior to Prompt for consent or Prompt for credentials on the secure desktop.
- Run gpupdate /force from an elevated Command Prompt.
- Restart the PC.
If you’re in a domain environment, contact your IT admin — domain GPOs can reapply settings at next policy refresh.
Notes/Tips: Windows Home lacks gpedit; use Registry method below.
4) Registry UAC keys misconfigured (EnableLUA)
Why it causes the problem
The registry value EnableLUA controls whether UAC is enabled at all. When set to 0, UAC is disabled system‑wide.
Step-by-step solution
- Create a restore point (search Create a restore point).
- Open Registry Editor: press Win + R, type regedit, Enter.
- Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
- Double‑click EnableLUA. If it exists and is 0, change it to 1. If missing, create a DWORD (32‑bit) named EnableLUA and set value 1.
- Also verify ConsentPromptBehaviorAdmin is set to 2 (prompt for consent) and ConsentPromptBehaviorUser as appropriate.
- ConsentPromptBehaviorAdmin = 2
- ConsentPromptBehaviorUser = 3 (typical)
- Close regedit and restart Windows.
Notes/Tips: Changing EnableLUA requires a restart and may break some legacy apps that expect elevated behavior; backup registry first.
5) Third‑party antivirus/security software interfering
Why it causes the problem
Some security suites alter how elevation works (for example, by intercepting consent dialogs) or include modes that suppress UAC to avoid conflicts.
Step-by-step solution
- Temporarily disable real‑time protection from the security app’s interface (check vendor instructions).
- Test a UAC action (e.g., install a small app or open an elevated Command Prompt).
- If UAC returns, consult the product’s support to disable the compatibility feature or whitelist Consent.exe.
- If unsure, uninstall the security product via Settings > Apps, restart, and test UAC again.
- Reinstall a compatible version or switch to Windows Defender if needed.
Notes/Tips: Always download the vendor’s latest version; older versions are more likely to cause issues.
6) Missing or corrupted Consent.exe or other system files
Why it causes the problem
The UAC prompt is managed by Consent.exe; if it’s missing or corrupted, prompts won’t appear. Corrupted system files can also break UAC behavior.
Step-by-step solution
- Open an elevated Command Prompt (search cmd, right‑click Run as administrator).
- Run: sfc /scannow — wait for the scan to complete and follow on‑screen instructions.
- If SFC reports issues it cannot fix, run: DISM /Online /Cleanup-Image /RestoreHealth
- Reboot and run sfc /scannow again.
- Check C:\Windows\System32\Consent.exe exists. If missing and SFC/DISM fail, restore from a backup or perform an in‑place repair upgrade (use Media Creation Tool and choose “Upgrade this PC now”).
Notes/Tips: In‑place upgrade preserves files and apps while repairing system files.
7) Explorer or shell running elevated preventing prompts
Why it causes the problem
If explorer.exe or the shell is running elevated, child processes may inherit elevated tokens and not prompt. This can happen if you manually launched the shell as admin.
Step-by-step solution
- Sign out and sign back in (or restart the PC) — this returns Explorer to normal user token.
- Avoid running explorer.exe as administrator. If needed temporarily, use separate elevated shells (Command Prompt or PowerShell) instead.
- Check Task Manager (Ctrl + Shift + Esc) → Details, add the Elevated column to see which processes run elevated.
Notes/Tips: Some startup apps request elevation and can cause Explorer to elevate; disable suspect startup items in Task Manager > Startup.
8) Tweaker utilities or malware disabled UAC
Why it causes the problem
System optimizer/tweaker utilities and some malware explicitly disable UAC to gain elevated control without prompts.
Step-by-step solution
- Uninstall any tweaker/optimizer apps via Settings > Apps.
- Run a full scan with Windows Defender Offline or a reputable antimalware tool (e.g., Malwarebytes).
- Restore UAC via the steps above (Control Panel slider, registry EnableLUA = 1).
- If malware altered system files or policy, follow SFC/DISM and consider a system restore or in‑place upgrade.
Notes/Tips: Always avoid “one‑click” optimizers that promise to disable UAC for performance — this reduces security.
Ajoute une section que tu vois necessaire pour pour completer l’article.
Best practices, precautions, and recovery options
- Backup and restore: Always create a System Restore point or image backup before editing Group Policy or the registry. Search Create a restore point to open System Protection.
- When to use in‑place repair: If SFC/DISM and policy/registry fixes don’t work, use the Windows 10 Media Creation Tool to perform an in‑place upgrade (choose “Upgrade this PC now”) to repair system files without losing apps and data.
- Logs and diagnosis: Check Event Viewer (Windows Logs > Application/System) for errors around Consent.exe or User Account Control to get specific error codes.
- Domain environments: If your PC is joined to a domain, confirm with IT — domain GPOs may reapply settings. Local changes can be overwritten.
- Recovery environment: If you can’t sign in normally, use Windows Recovery Environment (WinRE) to perform system restore, uninstall updates, or run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows from the recovery command prompt.
FAQ
What happens if I permanently disable UAC?
Disabling UAC removes a key security layer; malware and malicious scripts can run elevated without prompting. It’s not recommended except for limited, temporary troubleshooting.
How can I test that UAC is working after fixes?
Try running Notepad as admin: press Win, type notepad, right‑click, Run as administrator — you should see a consent prompt. Or try installing a small app that requires elevation.
Can I re‑enable UAC without rebooting?
Some changes (like the slider) require a restart; registry changes to EnableLUA also require a restart. You can temporarily force policies with gpupdate /force, but restart is recommended.
Why does UAC prompt appear on some apps but not others?
Apps that request elevation (manifest contains requireAdministrator) trigger prompts. Apps running as standard user that don’t request elevation won’t prompt. Also, processes launched by a service or already elevated inherit tokens and won’t prompt.
Is there a safe command‑line way to restore default UAC settings?
Yes. From an elevated Command Prompt/PowerShell:
- Set UAC on: reg add “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System” /v EnableLUA /t REG_DWORD /d 1 /f
- Restore common prompt behavior values: reg add … /v ConsentPromptBehaviorAdmin /t REG_DWORD /d 2 /f
Then restart.
Conclusion
Most cases of UAC doesn’t work in Windows 10 are caused by settings (slider, registry, group policy), the built‑in Administrator account, interfering third‑party software, or corrupted system files; following the step‑by‑step fixes above will restore prompts in the majority of situations. If problems persist, use SFC/DISM, check Event Viewer for errors, and consider an in‑place repair or contacting IT support.
