User Account Control (UAC) was introduced in Windows Server 2008 and Windows Vista, and it was intended to provide an extra layer of system security by prompting a user for permission when a service or application tries to make changes to a system or install new software, or to modify existing applications. (See also: How to Disable UAC in Windows Vista.)
The primary purpose of UAC was to restrict user access to a least privilege model, where a user operates with a limited number of system privileges until more advanced privileges are required. When a program attempts to make changes to the system, UAC triggers an administrator prompt that requires administrator permission to continue. UAC helps keep Windows more secure by requiring users permission for system changes, which can help stop the spread of malware and other malevolent software. UAC was also a bit of a user-experience headache, which led to UAC being ridiculed in the infamous Mac vs PC TV ads and led to changes in Windows 7 that made UAC less obtrusive. (See also: How to Disable UAC in Windows 7.)
The most significant change to UAC in Windows 8 is that setting UAC to “Never Notify” in User Account Control Settings (see detailed steps on how to do this below) doesn’t actually turn off UAC completely, as it did in Windows 7. In the vast majority of cases this isn’t an issue, but some legacy applications — especially those designed to work with Windows XP that may expect perpetual administrator-level access — may have issues working properly. To get more background on the the changes in Windows 8 UAC, I spoke with Chris Hallum, a Microsoft product manager who specializes in Windows 8 client security.
“When you put UAC in the never-notify position the key difference is… [that] you’ll never get a prompt to elevate and UAC will auto-approve elevation. The key thing to realize is that if the app you’re running attempts to perform a function that requires elevation and it just assumes it’s running in admin mode, the app will fail unless it properly written,” Hallum said.
“It’s critical that the app be implemented in a way where it requests elevation before executing a function that requires it. If you have a poorly written app, you could try the registry hack (Editor’s note: See below for details on how to disable Windows 8 UAC via the registry) to work around the prompts but the consequences [of changing the Windows 8 registry to disable UAC]… are pretty extreme and all but break Windows.”
Hallum continued by saying that good Windows application development practices (that have been applied since UAC was introduced) translates into newer applications not having any issues with the way UAC is handled in Windows 8.
There are a number of ways to disable UAC in Windows 8, and I describe four of them below. They include disabling the UAC using the Windows 8 GUI, disabling UAC using Windows 8 search, disabling UAC using Group Policy, and disabling UAC by editing the Windows 8 system registry (not recommended!).
Figure 1: The Windows 8 ‘All apps’ icon.
Figure 2: The Windows 8 Control Panel icon.
Figure 3: Accessing Windows 8 user account settings.
Figure 4: Selecting User Accounts.
Figure 5: Changing user account control settings.
Figure 6: Setting UAC to ‘Never Notify’ on the ‘User Account Settings’ screen.
Figure 7: Using Windows 8 search to access the UAC settings screen.
This option uses the Local Group Policy Editor (filename: gpedit.msc) to change Windows 8 UAC settings.
You can also force Windows 8 to disable UAC by modifying the system registry. To do this, edit the registry by setting the value of HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem to zero, then restart the system.
WARNING: Disabling UAC via this method also breaks many elements in Windows 8. As Hallum explains, “If you disable UAC via the reg hack the Windows 8 Start Screen and Windows Store apps will no longer function,” Hallum said. “Customers don’t want to go there.”