Windows XP reports that Windows Management Instrumentation (WMI) might be
corrupted?
http://www.jsifaq.com/SUBK/tip5200/rh5281.htm
If you run Windows Management Instrumentation (WMI), wmimgmt.msc, you
receive: Failed to connect to local computer due to WMI:Generic failure.
These errors will occur if the %SystemRoot%System32WbemRepository folder
is damaged.
I had a problem with WMI, I also had a problem deleting
%SystemRoot%System32WbemRepository. I had to run Error Checking
(Chkdsk). And then try to delete the file.
C:WINDOWSSystem32WbemRepositoryFS.
—-
winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf
WMI relies on DCOM for remoting which in turn uses RPC which then uses
TCP/IP, so there could be several reasons why it isn’t connecting initially.
This is a known issue. Basically, when the provider calls MSI, it doesn’t
necessarily cancel the initial request and attempts to finish it so
wmiprvse.exe will still show cpu usage.
To correct permission issues:
1 — In the Management ConsoleServices STOP WMI and set to manual.
2 — Go to the WMI repository %Windows%system32%wbem and delete the
repository.
3 -Set the WMI service back to Automatic
4 — From %Windows%system32%wbem run «wbemtest» and connect to your
namespace.
5 — Start/Run/Regedit and navigate to: Locate current
—
Hope this helps. Let us know.
One fine day, Hyper-v system on 2012R2 platform was running deliciously, suddenly there was a power outage that was not enough to provide horizontal server shutdown, booting up but the Hyper-V error failed.
Consequently, after the power is restored, all other related services cannot run, including the most important Hyper-V service: (. Open, the error cannot run the VM
Experience sharing when the error is related should read the windows event log and find the correct error code for the new root case to handle quickly.
In the same way, the horizontal outage causes the server to corrupt the file with the entire error VMI repository. The WMI namespace ‘root virtualization v2’ is not registered in the CIM repository
So what is VMI, it’s important that the error is always hyper-v
Windows Management Instrumentation (WMI) ?
So the error VMI means that all the events of the system setting information are also error, as you see the file corrupted.rec.
So, have identified the root case, trying to rebuild the VMI Repository is ok.
Case 1: check resync and repair
winmgmt /verifyrepository
If the repository is not corrupted, a “WMI Repository is consistent”
Case 2: Not at all
cd C:WindowsSystem32wbemfor /f %s in (‘dir /b *.mof’) do mofcomp %s
NOTE: This will take a minute or so to complete.
for /f %s in (‘dir /b en-us*.mfl’) do mofcomp en-us%s
I’m so glad that the Hyper-V bug has been resolved, and it’s gone 🙂
Good luck to you
Phương Nguyễn là chủ sở hữu trang web viettechgroup.vn, phuongnguyenit.com. Phương Nguyễn là IT Pro, MCSA, MCSE, MCITP, CCNA, VCP, LPI, Cloud Services.. Chuyên gia quản trị cao cấp trong các tập đoàn, doanh nghiệp lớn.
