Any recommendation for fixing WMI on Windows Server 2012?

[mikejramsey]

Am I correct in thinking that the repair tool doesn't work on Windows Server 2012?  If not supported, any pointers on where to look for a fix for WMI consuming all the CPU?

--Thank you,
--Mike Ramsey

[mikejramsey]

Found this at https://social.technet.microsoft.com/Forums/windowsserver/en-US/8ed26d46-9994-4052-a307-5b071805aea8/wmi-corrupt-how-to-reinstallrepair?forum=winservergen

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.

[Boggin]

Did they work ?

[Willy2]

- Correct. The "Windows Repair Tool" does not support Server software because it seems the Server system settings are different to such a degree that it "disrupts" the Server software.

- However, I know that Windows Server 2012 is largely based on the Windows 7 OS. And I also know that the author of the "tweaking repair" tool was (past tense) interested in the differences between e.g. Win 7 and Server 2012 software. This in order to extend the scope of the repair tool to Server software as well. But I don't know if the author today is still interested.

@Boggin/@Julian: Perhaps you can email Shane and ask if he is still interested ?

[Boggin]

I already have when I saw the thread, but don't know when I'll get a reply.

[Willy2]

- What's the name of the process (Task Manager) that uses such an extreme amount of CPU ? "Svchost.exe" or e.g. "WMIprv.exe" ? And you're sure it's related to WMI ?

- Yes, you can try to run "05 - Repair WMI" on your Server 2012 system. But then I would also recommend the following:
- Make a backup of the registry FIRST (See the "Step 5: Backup" tab). Because the program changes a number of things in the registry. Then you can go back to a previous state if things don't work out well.
- Only select repair #5 (Repair WMI) and nothing else !!!

- I have a pretty good idea of what kind of commands are executed for that repair and those commands seem to be the same as in the 2nd post in this thread.

[Willy2]

- Oooops. Win Server 2012 is based on Win 8, not Win 7.

[whiggs]

Try this.  I downloaded this off of the Microsoft script repository.