none
Windows Management Intrumentation Stopped Working And Was Closed! -Please help! RRS feed

  • Question

  •  

    I get this error message about every 10 minutes, I've had Vista for about a year and it's never done this before.  I have copied the error details and posted them in this thread- please help as soon as possible.

     

    Product

    Windows Management Instrumentation

    Problem

    Stopped working

    Date

    11/5/2008 9:34 PM

    Status

    Not Reported

    Problem signature

    Problem Event Name: APPCRASH

    Application Name: svchost.exe_Winmgmt

    Application Version: 6.0.6001.18000

    Application Timestamp: 47918b89

    Fault Module Name: FastProx.dll

    Fault Module Version: 6.0.6001.18000

    Fault Module Timestamp: 4791a69a

    Exception Code: c0000005

    Exception Offset: 00035193

    OS Version: 6.0.6001.2.1.0.768.3

    Locale ID: 1033

    Additional Information 1: 8ac2

    Additional Information 2: ba7e91ebe6e75f08cd0ba76dbcf4ce2a

    Additional Information 3: 8ee5

    Additional Information 4: 862d5b3ab1983c335905dc41ca81919c

    Files that help describe the problem

    Version.txt

    AppCompat.txt

    memory.hdmp

    minidump.mdmp

     

    Friday, November 7, 2008 12:36 AM

Answers

  • David

     

    This is an error that usually means that the WMI Repository is corrupt.

    You will need to refresh the WMI repository.

     

    Make sure you are logged in with an Administrator account.

     

    Go to Start / All Programs / Accessories.

    Right click the Command Prompt and select the Run As Administrator option.

     

    In the Command Prompt window type the following command exactly as shown, including the spaces.

     

    net stop winmgmt

     

    (Press ENTER)

     

    Minimize the command window.

     

    Open Windows Explorer and navigate down to the following folder.

     

    c:\windows\system32\wbem\repository.

     

    Select and delete all of the files in the repository folder.

    (You will need to OK the UAC prompts)

     

    Exit Windows Explorer and bring up the Command Prompt again.

    Type the following command.

     

    net start winmgmt


     

    (Press ENTER)

     

    Close the command prompt window, exit any running programs and reboot the computer.

     

    When the computer restarts, the files in the repository folder will be replaced with fresh copies.

     

    This should stop the error messages.

     


    If this post helps to resolve your issue, click the Mark as Answer button at the top of this message.

    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience
    Friday, November 7, 2008 4:06 AM
    Moderator

All replies

  • David

     

    This is an error that usually means that the WMI Repository is corrupt.

    You will need to refresh the WMI repository.

     

    Make sure you are logged in with an Administrator account.

     

    Go to Start / All Programs / Accessories.

    Right click the Command Prompt and select the Run As Administrator option.

     

    In the Command Prompt window type the following command exactly as shown, including the spaces.

     

    net stop winmgmt

     

    (Press ENTER)

     

    Minimize the command window.

     

    Open Windows Explorer and navigate down to the following folder.

     

    c:\windows\system32\wbem\repository.

     

    Select and delete all of the files in the repository folder.

    (You will need to OK the UAC prompts)

     

    Exit Windows Explorer and bring up the Command Prompt again.

    Type the following command.

     

    net start winmgmt


     

    (Press ENTER)

     

    Close the command prompt window, exit any running programs and reboot the computer.

     

    When the computer restarts, the files in the repository folder will be replaced with fresh copies.

     

    This should stop the error messages.

     


    If this post helps to resolve your issue, click the Mark as Answer button at the top of this message.

    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience
    Friday, November 7, 2008 4:06 AM
    Moderator
  • That fixed it, thanks a ton for your time!

    Saturday, November 8, 2008 12:16 AM
  • David

     

    Your welcome.

     

    I'm very glad this resolved the problem.  

     



    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience
    Saturday, November 8, 2008 5:59 AM
    Moderator
  • Ronnie Vernon, good afternoon, maybe you can help me. I have such a situation, there is a server with Windows Server 2008 R2, it has the role of terminal services, for some reason the snap-in configuration of the session node has not opened, on one site I found the reason and there as well offered to re-create the WMI repository, I did it , but it did not help me to tell you where to dig?
    Friday, June 15, 2018 6:34 PM