WMI Respository corruption on Windows Server 2008 R2

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          6/25/2014 10:57:20 PM
Event ID:      1065
Task Category: None
Level:         Error
Keywords:     
User:         Domain\Act
Computer:     server name
Description: The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object cn={72E1E5D2-987F-42D3-B41C-E2E557648747},cn=policies,cn=system,DC=xxxxxx,DC=xxxx,DC=com. This could be caused by RSOP being disabled  or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Make sure the WMI service is started and the startup type is set to automatic. New Group Policy objects or settings will not process until this event has been resolved.

This error message usually indicates that the WMI repository is corrupted, but sometimes may also indicate that some other system files are corrupted.

If you have any previous backup, I would highly suggest that you try restoring to that backup to see if the problem remains.

Or, would you please try the following steps to see if they can be of any help?

1. Disable and stop the WMI service.

     sc config winmgmt start= disabled

     net stop winmgmt

2. Run the following commands.

     Winmgmt /salvagerepository %windir%\System32\wbem      (I noticed that you have run this command, but I would suggest that you try it again)

     Winmgmt /resetrepository %windir%\System32\wbem

4. Re-enable the WMI service and then reboot the server to see how it goes.

     sc config winmgmt start= auto

If the problem remains, then try the following steps to rebuild the repository:

1. Disable and stop the WMI service.

     sc config winmgmt start= disabled     (note that there is a blank between '=' and 'disabled')

     net stop winmgmt

2. Rename the repository folder (located at %windir%\System32\wbem\repository) to repository.old.

3. Re-enable the WMI service.

     sc config winmgmt start= auto

4. Reboot the server to see if the problem remains.

If the above steps cannot help, you may also need to check if some disk sectors or system files are corrupted. You may try "chkdsk" and "sfc /scannow" commands to see if they can help. Otherwise, you may need to reinstall the whole server.

http://support.microsoft.com/kb/2705357 

http://support.microsoft.com/kb/2692929

http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx

http://higginsjrh.blogspot.in/2012/02/wmi-respository-corruption-on-windows.html