Consider the following scenario:
- You deploy an AppLocker policy together with a default rule on a Windows 7 Service Pack 1 (SP1)-based or Windows Server 2008 R2 SP1-based computer.
- The administrative users or other high privileged group’s users can run executable files that are in a whitelist that is defined in AppLocker policy without receiving a User Account Control (UAC) prompt on the computer.
- You create a user named "AdminUser" as a member of the Administrators group or other high privileged group.
- You use "AdminUser" to run an executable file that is in the whitelist.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1. For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
Registry informationTo use the update in this package, you do not have to make any changes to the registry.
Restart requirementYou do not have to restart the computer after you apply this update.
Update replacement informationThis update does not replace a previously released update.
Additional file information
- Built-In Administrators
- Power Users
- Account Operators
- Server Operators
- Printer Operators
- Backup Operators
- RAS Servers Group
- Windows NT 4.0 App Compat Group
- Network Configuration Operators
- Domain Administrators
- Domain Controllers
- Certificate Publishers
- Schema Administrators
- Enterprise Administrators
- Group Policy Administrators
Article ID: 2862565 - Last Review: Sep 10, 2013 - Revision: 1