Namespace root\cimv2 not found! Repair WMI!!!

I had some funny WMI problems yesterday. I couldn’t connect to any WMI namespace except to root. This means, the WMI service was running and had no errors. The root cause of the problem was the SCCM Eval Task, which is running on any SCCM Client in combination with Windows Management Framework 3.0.

To repair WMI problems, I used these commands in a batch file:


sc config Winmgmt start= disabled
sc stop Winmgmt

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

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

sc config Winmgmt start= auto
sc start Winmgmt

cd /d %windir%\system32\wbem
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

cd /d %windir%\sysWOW64\wbem
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

REM If you are using wmi with fixed port you have to set it again "winmgmt /standalonehost"
REM Reboot Computer and check again!!!

The key part was to reregister the mof files with the following command in the wbem directory:

for /f %%s in (‘dir /s /b *.mof *.mfl’) do mofcomp %%s

 

I hope these commands will help you too.

Thomas Kurth

Thomas Kurth

I’m a consultant, trainer and architect formodern workplace and enterprise mobility projects with Microsoft Technologies in the past eight years. I love to push and design the modern workplace based on Windows 10, EM&S and O365 for my customers which is the only answer for the current security threats, agile world and the fast-changing business requirements of my customers. Important for me is to simplify and automate the operational processes, because there are the highest costs.
Enterprise Adminstrator ExpertMCTCMCE

0 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe
Hosting sponsored by:
Archive