The "Trusted Root Certification Authorities" setting cannot be removed from a GPO in Windows 7 or Windows Server 2008 R2

Applies to: Windows 7 EnterpriseWindows 7 ProfessionalWindows 7 Ultimate More

Symptoms


Consider the following scenarios.

Scenario 1
  • On a computer that is running Windows 7 or Windows Server 2008 R2, you use the Group Policy Management Console (MMC) snap-in to connect to a domain controller.
  • You locate and then enable the following policies in a Group Policy Object (GPO):
    • Computer Configuration\Windows Settings\Security Settings\Public Key Policies\Certificate Services Client – Auto-Enrollment
    • Computer Configuration\Windows Settings\Security Settings\Public Key Policies\Certificate Path Validation Settings

  • You update the GPO and then make sure that the policies are enabled successfully.

In this scenario, the Trusted Root Certification Authorities setting is set silently and unintentionally in the background. Additionally, this setting cannot be removed from the GPO even after you set the Certificate Services Client – Auto-Enrollment setting and the Certificate Path Validation Settings setting to Not Configured.

Scenario 2
  • On a computer that is running Windows 7 or Windows Server 2008 R2, you use the Group Policy Management Console (MMC) snap-in to connect to a domain controller.
  • You locate and then enable the following policy in a Group Policy Object (GPO):
    • System\Internet Communication Management \Internet Communication settings\Turn off Automatic Root Certificates Update

  • You update the GPO and then make sure that the policies are enabled successfully.

In this scenario, the Trusted Root Certification Authorities setting is set silently and unintentionally in the background. Additionally, these settings cannot be removed from the GPO even after you set the Turn off Automatic Root Certificates Update setting to Not Configured.

Resolution


Hotfix information

A 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to 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.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 Service Pack 1 (SP1)

For information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, see Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2 .

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information