# How to permanently disable UAC in Windows Server

Learn how to permanently disable User Account Control in Windows Server by updating the required registry settings and rebooting safely.

blog

01 Feb 2016 fr

![How to permanently disable UAC in Windows Server](/wp-content/uploads/2016/01/img_569ca542e50a2.png)

[Voir les images (12)](#pf-content-image-1-0)

**User Account Control (UAC)** is a feature in **Windows** that can help you stay in control of your computer by informing you when a program makes a change that requires administrator-level permission. UAC works by adjusting the permission level of your user account. If you're doing tasks that can be done as a standard user, such as reading e‑mail, listening to music, or creating documents, you have the permissions of a standard user—even if you're logged on as an administrator. However for Windows Server where most of the tasks are done by **Administrators** by default it's often getting disabled by **Administrators**.

### ❓ Problem Description

Most administrators will disable **UAC (User Access Control)** using standard approach as it was standard procedure since **Windows Vista**, continued thru **Windows** **7** and other client systems. To do that you just had to:

- Press START
- Type in **msconfig **to start **System Configuration** tool

[!\[System Configuration opened from msconfig with the Tools tab selected\](/wp-content/uploads/2016/02/img_56aface9e3abe.png)](/wp-content/uploads/2016/02/img_56aface9e3abe.png)

- Switch to **Tools** Tab, and choose **Change UAC Settings**

[!\[System Configuration tool list with Change UAC Settings highlighted\](/wp-content/uploads/2016/02/img_56afad21288ff.png)](/wp-content/uploads/2016/02/img_56afad21288ff.png)

- And finally modify settings by choosing **Never Notify **

[!\[User Account Control settings slider set to Never notify\](/wp-content/uploads/2016/01/img_569ca542e50a2.png)](/wp-content/uploads/2016/01/img_569ca542e50a2.png)

While this modification has worked fairly well in **Windows** client systems (I have not seen the drawbacks of this change), this change in Windows server systems doesn't always go well. It changes some behaviour such as:

- CMD prompt gets started as Administrator

[!\[Command Prompt window launched with Administrator privileges on Windows Server\](/wp-content/uploads/2016/02/img_56afae1ceb9ef.png)](/wp-content/uploads/2016/02/img_56afae1ceb9ef.png)

- Windows PowerShell ISE starts as Administrator

[!\[Windows PowerShell ISE running as Administrator on Windows Server\](/wp-content/uploads/2016/02/img_56afaea417a35.png)](/wp-content/uploads/2016/02/img_56afaea417a35.png)

However some things do not get started that way such as:

- **Active Directory Module for Windows PowerShell**

[!\[Active Directory module shortcut showing it does not automatically run elevated\](/wp-content/uploads/2016/02/img_56afaeba0fc8b.png)](/wp-content/uploads/2016/02/img_56afaeba0fc8b.png)

You have to explicitly choose **Run as Admin** to get proper Window. And even thou you don't get the **UAC** prompt anymore the **PowerShell** module gets loaded properly with **Administrator** rights.

[!\[Run as administrator context menu used to start the Active Directory module\](/wp-content/uploads/2016/02/img_56afaf15d63f3.png)](/wp-content/uploads/2016/02/img_56afaf15d63f3.png)

This also happens in multiple other scenarios (installing Exchange, installing Exchange updates . And because it's not visible at first sight the results are often very unpredictable.

### 💡 Solution

To fully disable **UAC** one can do this via Registry or via Local Policies interface.

**Option 1**. You have the option to turn off **UAC** via registry by changing the DWORD “**EnableLUA**” from 1 to 0 in “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”, and doing system reboot.

[!\[Registry Editor showing the EnableLUA value under Windows system policies\](/wp-content/uploads/2016/01/img_569ca4db92e6e.png)](/wp-content/uploads/2016/01/img_569ca4db92e6e.png)

After which you will get prompted to restart computer to activate the change.

[!\[Windows restart prompt displayed after changing UAC registry settings\](/wp-content/uploads/2016/02/img_56afb055857ce.png)](/wp-content/uploads/2016/02/img_56afb055857ce.png)

**Option 2**. Opening **Local Security Policy **(**secpol.msc) **and changing **User Account Control: Behavior of the elevation prompt **to **Elevate without Prompting.**

[!\[Local Security Policy showing User Account Control elevation prompt behavior settings\](/wp-content/uploads/2016/01/img_569cadda37b59.png)](/wp-content/uploads/2016/01/img_569cadda37b59.png)[!\[Elevation prompt policy configured to Elevate without prompting\](/wp-content/uploads/2016/01/img_569caf101ae7a.png)](/wp-content/uploads/2016/01/img_569caf101ae7a.png)

Hopefully after applying those settings the problem of weird problems coming from not **Run As Admin** option will be past.

### 🔴 Registry file to DISABLE UAC

Save file as **DisableUAC.reg** and run it.

```powershell
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"ConsentPromptBehaviorAdmin"=dword:00000000
"EnableLUA"=dword:00000000
```

### 🟢 Registry file to ENABLE UAC

Save file as **EnableUAC.reg** and run it. Just in case you change your mind. Following reg file simply brings back default settings.

```powershell
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"ConsentPromptBehaviorAdmin"=dword:00000005
"EnableLUA"=dword:00000001
```

[!\[Registry file opened in Notepad for enabling UAC defaults again\](/wp-content/uploads/2016/02/img_56afce1771bf6.png)](/wp-content/uploads/2016/02/img_56afce1771bf6.png)

## Projets associés

Projets liés aux tags, catégories et au contenu de cet article.

[Tous les projets](/fr/projets/)

Recherche des projets associés...

[Retour au blog](/blog)

## Articles associés

- [Update-Module – PackageManagement\Install-Package : Unable to find repository](/fr/blog/update-module-packagemanagementinstall-package-unable-to-find-repository/)
- [Hyper-V – There was an error during move operation](/fr/blog/hyper-v-error-move-operation/)
- [Windows – Killing remotely hanging RDP session](/fr/blog/killing-remotly-hanging-rdp-session-for-windows/)

<!-- PowerForge markdown artifact sha256:900F80882E5E74701268591C8D4CA0B3BFD970904F14ECCA42DD2C8FC88E8360 -->
