Share via

Cannot access the Windows Management Instrumentation software. Windows Management files may be moved or missing.

Anonymous
2011-03-11T11:06:15+00:00

Original Title: system information, can't collect information.

can't access the windows management instrumentation software, windows management files maybe moved or missing? Can anyone help.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2011-03-12T06:51:31+00:00

    Hi jesops,

    Did you make any software or hardware changes on your computer prior to this issue?

    This error occurs if Windows Management Instrumentation (WMI) service is not running or corrupted WMI repository folder.

    Let’s follow these methods and check if the issue persists.

    Method 1

    You may follow these steps and check if the issue persists.

    a. Click Start -> Type CMD -> Right click on CMD from the result -> Click Run as Administrator

    b. Run the following command one at a time and press enter to execute

    • cd /d %windir%\system32\wbem

    • for %i in (*.dll) do regsvr32 -s %i

    • for %i in (*.exe) do %i /regserver

    c. Close all windows and reboot the computer and now try opening the system information

    Method 2

    You may also try rebuilding WMI repository and check if the issue persists.

    a.        Click Start -> Type CMD -> Right click on CMD from the result -> Click Run as Administrator

    b.        Type the command ‘net stop winmgmt’ and press enter

    c.        Leave the command prompt open and click Start and type system32 -> Open the folder system32 from the result pane

    d.        From the system32 folder open Wbem and look for the folder Repository

    e.        Right click on Repository and click rename

    f.         Change the folder name from Repository to Repository.old

    g.        Switch back to command prompt and type net start winmgmt and hit enter to execute

    h.        Close all the windows and reboot the computer and now try opening the system information

    Hope the information helps.

    Please post back and let us know.

    100+ people found this answer helpful.
    0 comments

32 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-02-25T23:37:22+00:00

    I couldn't change repository to .old, it wouldn't let me.

    30+ people found this answer helpful.
    0 comments
  2. Anonymous
    2011-07-22T05:24:18+00:00

    none of them work.  I notice also when the wmi is stopped, the windows security essentials also stop...

    6 people found this answer helpful.
    0 comments
  3. Anonymous
    2013-10-05T11:57:03+00:00

    Nothing works for me. Tried:

    1. Repaired W7 Ultimate SP1 OS using the Upgrade option with a W7 Ultimate SP1 cd.
    2. Run SFC /Scannow - no errors.
    3. Checked that the WMI service is running - ok.
    4. Re-registered all the dll's in c:\windows\system32\wbem.
    5. Re-compiled all the mof and mfl files in c:\windows\system32\wbem.
    6. Ran WMIDiag.vbs. The report highlighted some 40 (WBEM_E_NOT_FOUND) errors - no different to the report from another W7 ultimate machine where WMI works ok.
    7. Registered the system.management.instrumentation.dll with: "regasm %systemdrive%\program files\reference assemblies\microsoft\framework\v3.5\system.management.instrumentation.dll".
    8. Rebuilt the Repository numerous times.
    9. SystemInfo in CMD works fine and returns all system data ok. Msinfo32.exe doesn't.
    10. Interestingly, the following script returns the correct info: *strComputer = "." Set objWMIService = GetObject("winmgmts:" & strComputer & "\root\cimv2") Set colItems = objWMIService.ExecQuery("Select * from Win32_operatingsystem") For Each objItem In colItems Wscript.Echo "Name: " & objItem.Name Next*

    but the same query doesn't work in Paessler WMITest.exe - where I get the same 0x80041013 error! So it seems WMI itself is working normally but not when called from, say, MSinfo32.

    No WMI error in Event Viewer for startup.

    Any ideas of where to go from here?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2013-10-07T07:57:58+00:00

    Ok, further investigation reveals that, for example, entering msinfo32.exe into the 'run' dialog causes the error. However, entering c:\windows\system32\msinfo32.exe in the dialog works ok. It looks as though using 'msinfo32.exe' in the dialog calls 'c:\windows\sysWOW64\msinfo32.exe' which fails with the 'Can't collect Information' error. It appears, therefore, that WMI fails when called from the c:\windows\sysWOW64 folder but not from c:\windows\system32 folder. There is no repository in c:\windows\sysWOW64\wbem so it seems that when msinfo32.exe is called from c:\windows\sysWOW64 it cannot access WMI. How do I fix this?

    Andrew

    1 person found this answer helpful.
    0 comments