To work around these issues, you can use one of the following methods.
Method 1: Use AppLocker or Software Restriction policies instead of this legacy policy
Windows 7 and Windows Server 2008 R2 introduced AppLocker to:
- Help prevent malicious software (malware) and unsupported applications from affecting computers in your environment.
- Prevent users from installing and using unauthorized applications.
- Implement application control policy to satisfy security policy or compliance requirements in your organization.
Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 all support Software Restriction Policies (SAFER) which also control applications similiarly to AppLocker. Both AppLocker and SAFER replace the legacy policy setting "Run only allowed Windows applications", which was originally designed for Windows 95 system policies.
For more information about AppLocker, please review:
http://technet.microsoft.com/en-us/library/dd723678(WS.10).aspxFor more information about SAFER, please review:
http://technet.microsoft.com/en-us/library/bb457006.aspxMethod 2: Re-create the setting on Windows 7 or on Windows Server 2008
To work around this issue, you will have to re-create the
Run only allowed Windows applications Group Policy setting by using the Group Policy Management Editor window on a server that is running Windows Server 2008 or on a Windows 7-based computer. After the setting has been re-created, do not edit Group Policy settings on a server that is running Windows Server 2003 or on a Windows XP-based computer.
Method 3: Edit the setting on Windows Server 2003 or on Windows XP
To work around this issue, only edit the
Run only allowed Windows applications Group Policy setting on a server that is running Windows Server 2003 or on a Windows XP-based computer.