Solved wmi is corrupt

[kenpachizero]

Hello everyone,
im not sure if this is the correct place to post this,
as you know my wmi is corrupt, i have tried the wmidiag.vbs from MS but to no success,
if anyone can help me that would be great, attached is the txt file wmidiag opens View attachment WMIDIAG-V2.1_WIN7_.CLI.SP1.64_MOON_2012.08.01_12.16.12-REPORT.TXT

 

[centaur78]

Hi

Try repairing and rebuilding the WMI service...

Click on start>Run>cmd

On the command prompt run the below steps in order

1. net stop winmgmt
then go to the C:\Windows\system32\wbem directory and delete the Repository directory

2. net start winmgmt

3. cd /d %windir%\system32\wbem
4. for %i in (*.dll) do RegSvr32 -s %i
5. for %i in (*.exe) do %i /RegServer

and

6. cd /d %windir%\sysWOW64\wbem
7. for %i in (*.dll) do RegSvr32 -s %i
8. for %i in (*.exe) do %i /RegServer


reboot and let me know ...

NOTE: A word of advice... Rebuilding the WMI repository will most probably result in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository.

 

[kenpachizero]

Hey Centaur78, thanks for your help.
i have done as instructed but got the same result unfortunately

 

[kegobeer]

The report you posted has instructions on how to attempt a repair of the WMI/MOF files. Have you tried them?

Also, I notice a lot of improper shutdowns. Do you have (or have you had) BSOD problems?

 

[kenpachizero]

Hey Kegobeer,
the improper shutdowns is from my graphics card stuffing up,
i have tried the following commands:
WMIDiag CorrelateClassAndProvider
WMIDiag WriteInRepository=root

 

[kegobeer]

Have you had BSODs?

 

[kenpachizero]

once while i was editing a .txt file on my desktop

 

[kegobeer]

Follow these instructions so I can look at the minidump and also look at your system.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[cluberti]

Don't try to rebuild WMI manually on Win7, as you could make it worse. You should execute the following 2 commands from an elevated cmd prompt:

winmgmt /standalonehost
winmgmt /resetrepository

Reboot.

 

[centaur78]

You could also verify if WMI is consistent by running

winmgmt /verifyrepository at the command prompt

if it says inconsistent ... Then follow the advice by Cluberti

If nothing works ... follow this from Microsoft

If /salvagerepository or /resetrepository does not resolve the issue, then manually rebuild repository:

1. Change startup type to Window Management Instrumentation (WMI) Service to disabled
2. Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
3. Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
4. Open a CMD Prompt with elevated privileges
5. CD windows\system32\wbem
6 for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
7. Set the WMI Service type back to Automatic and start WMI Service
8. cd /d c:\ ((go to the root of the c drive, this is important))
9. for /f %s in ('dir /s /b *.mof *.mfl') do mofcomp %s
10. Reboot the server

 

[kenpachizero]

Hey everyone,
its says WMI repository is consistent
i have attached the zip with my computer details
View attachment Seven Forums.zip

 

[cluberti]

You should run /resetrepository and /standalonehost and reboot, and then try again. If you STILL have issues at that point, WMI is probably not actually your problem (because resetting the repository rebuilds the entire repository as if setup.exe had been run, for any mof that has #pragma autorecover and/or is included with Windows itself).

 

[kenpachizero]

Hey Everyone,
my wmi is now fixed, i ran the "/resetrepository and /standalonehost"
thank you to everyone how helped me