Two warning messages are logged for the Resultant Set of Policy (RSoP) data when you run the "gpupdate /force" command on a computer that is running Windows Server 2008 Server Core

Applies to: Windows Server 2008 StandardWindows Server 2008 Standard without Hyper-VWindows Server 2008 Enterprise


Consider the following scenario:
  • You add a computer that is running Windows Server 2008 Server Core to a Windows Server 2008 domain.
  • You enable one or more Group Policy preferences in a Group Policy object (GPO).
  • You deploy this GPO to the computer.
  • At an elevated command prompt on the computer, you run the gpupdate /force command.

In this scenario, the Group Policy preferences are applied successfully. However, the following warning message is logged in the Application log: Additionally, the following warning message is logged in the System log:These two event logs indicate that the following files are missing on the computer:
  • %SYSTEMROOT%\system32\wbem\polprocl.mof
  • %SYSTEMROOT%\system32\wbem\en-us\polprocl.mfl
Note This problem occurs in Windows Server 2008 Service Pack 2 (SP2) Server Core and Windows Server 2008 Server Core.


This problem occurs because the Windows Server 2008 Server Core Setup program does not copy the two missing files to the computer during the installation process.


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.


To apply this hotfix, the computer must have Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 installed.

Restart requirement

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

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 Server 2008 file information note
  • The files that apply to a specific product, SR_Level (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the fileversion numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.6000.16xxxWindows VistaRTMGDR
    6.0.6000.20xxxWindows VistaRTMLDR
    6.0.6001.18xxxWindows Vista and Windows Server 2008SP1GDR
    6.0.6001.22xxxWindows Vista and Windows Server 2008SP1LDR
    6.0.6002.18xxxWindows Vista and Windows Server 2008SP2GDR
    6.0.6002.22xxxWindows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the original release of Windows Server 2008.
  • GDR service branches contain only fixes that are broadlyreleased to address widespread, critical issues. LDR service branches containhotfixes in addition to broadly released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum)that are installed for each environment are listed separately. MUM and MANIFEST files, andthe associated security catalog (.cat) files, are critical to maintaining thestate of the updated component. The security catalog files (attributes notlisted) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Polprocl.mofNot applicable28,27417-Jul-200910:50Not applicable
Polprocl.mflNot applicable67,65817-Jul-200914:35Not applicable
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Polprocl.mofNot applicable28,27417-Jul-200910:38Not applicable
Polprocl.mflNot applicable67,65817-Jul-200914:47Not applicable


To work around this problem, copy the two missing files from a computer that is running the same language version of Windows Server 2008, and then copy the files to the expected location as follows:

  • %SYSTEMROOT%\system32\wbem\polprocl.mof
  • %SYSTEMROOT%\system32\wbem\<locale>\polprocl.mfl


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

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

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

File nameFile versionFile sizeDateTimePlatform
Package_for_kb967166_sc_0~31bf3856ad364e35~x86~~ applicable19,53718-Jul-200909:02Not applicable
Package_for_kb967166_sc_1~31bf3856ad364e35~x86~~ applicable12,03318-Jul-200909:02Not applicable
Package_for_kb967166_sc~31bf3856ad364e35~x86~~ applicable1,70318-Jul-200909:02Not applicable
Package_for_kb967166_server_0~31bf3856ad364e35~x86~~ applicable15,56218-Jul-200909:02Not applicable
Package_for_kb967166_server_1~31bf3856ad364e35~x86~~ applicable8,01518-Jul-200909:02Not applicable
Package_for_kb967166_server~31bf3856ad364e35~x86~~ applicable1,71518-Jul-200909:02Not applicable
X86_microsoft-windows-g..icy-policymaker-mof_31bf3856ad364e35_6.0.6001.22474_none_ba8f297696444887.manifestNot applicable4,57717-Jul-200916:08Not applicable
X86_microsoft-windows-g..icy-policymaker-mof_31bf3856ad364e35_6.0.6002.22179_none_bc7a9cd093661c5e.manifestNot applicable4,57717-Jul-200915:39Not applicable
X86_microsoft-windows-g..maker-mof.resources_31bf3856ad364e35_6.0.6001.22474_en-us_a071fa896fca0e9e.manifestNot applicable3,27117-Jul-200915:16Not applicable

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

File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-g..icy-policymaker-mof_31bf3856ad364e35_6.0.6001.22474_none_16adc4fa4ea1b9bd.manifestNot applicable4,87417-Jul-200916:16Not applicable
Amd64_microsoft-windows-g..icy-policymaker-mof_31bf3856ad364e35_6.0.6002.22179_none_189938544bc38d94.manifestNot applicable4,87417-Jul-200917:33Not applicable
Amd64_microsoft-windows-g..maker-mof.resources_31bf3856ad364e35_6.0.6001.22474_en-us_fc90960d28277fd4.manifestNot applicable3,57217-Jul-200915:31Not applicable
Package_for_kb967166_sc_0~31bf3856ad364e35~amd64~~ applicable19,70118-Jul-200909:02Not applicable
Package_for_kb967166_sc_1~31bf3856ad364e35~amd64~~ applicable12,12518-Jul-200909:02Not applicable
Package_for_kb967166_sc~31bf3856ad364e35~amd64~~ applicable1,71318-Jul-200909:02Not applicable
Package_for_kb967166_server_0~31bf3856ad364e35~amd64~~ applicable15,69018-Jul-200909:02Not applicable
Package_for_kb967166_server_1~31bf3856ad364e35~amd64~~ applicable8,07118-Jul-200909:02Not applicable
Package_for_kb967166_server~31bf3856ad364e35~amd64~~ applicable1,72518-Jul-200909:02Not applicable