The RSoP snap-in does not display some file security policies, and Event ID 1091 is logged on domain member computers that are running Windows Vista Service Pack 1 or Windows Server 2008

Consider the following scenario:

• In an Active Directory domain, you have member computers that are running Windows Vista Service Pack 1 or Windows Server 2008.
• You configure a file security policy to set file permissions on a folder.
• The path that you specified for the folder contains some environment variables. For example, you specify the following path for the folder:
  %ALLUSERSPROFILE%\MICROSOFT\WINDOWS\START MENU\PROGRAMS\STARTUP

In this scenario, when you run the Resultant Set of Policy (RSoP) Microsoft Management Console (MMC) snap-in on a member computer, the security file policy is missing. Additionally, the following event is logged on the domain controllers and on the member computers:

Log Name: System
Source: Microsoft-Windows-GroupPolicy
Date: Date_Time
Event ID: 1091
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: ComputerName
Description:
Windows could not record the Resultant Set of Policy (RSoP) information for the Group Policy extension Security. Group Policy settings successfully applied to the computer or user; however, management tools may not report accurately.

This problem occurs because the Group Policy engine translates the environment variables incorrectly.

To resolve this problem, apply this hotfix on the domain member computers.

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, visit the following Microsoft Web site: 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 on a Windows Vista-based computer, you must have Windows Vista Service Pack 1 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base: There are no prerequisites for installing this hotfix on Windows Server 2008-based computers.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

  Version	Product	Milestone	Service branch
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: