WMI Error popup

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I have a cable modem and Windows XP Home. I frequently get an error message:
"WMI has encountered a problem and needs to close." Occasionally, the error
also kicks me out of IE.

The error signature is as follows:
szAppname:wmiprvse.exe SzAppVer:5.1.2600.2180
szModName:kernel32.dll szModVer5.12600.2180 offset 0004b0df

One fix I tried was to open Command prompt and type
Start>Run>cmd>Enter and then
winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf

This didn't solve the problem. Any other ideas? Many thanks.
2 answers Last reply
More about error popup
  1. Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

    Delete the files in the REPOSITORY folders (..\system32\wbem) (you will have to turn off the winmanagement service to do that) 'net
    stop winmgmt'

    --
    Mark L. Ferguson
    FAQ for Windows Antispy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
    "geneandjack" <gcjstone@comcast.net(don''''tspam)> wrote in message news:C1EF25AD-9978-43F2-AE94-25BBAE4BC054@microsoft.com...
    >I have a cable modem and Windows XP Home. I frequently get an error message:
    > "WMI has encountered a problem and needs to close." Occasionally, the error
    > also kicks me out of IE.
    >
    > The error signature is as follows:
    > szAppname:wmiprvse.exe SzAppVer:5.1.2600.2180
    > szModName:kernel32.dll szModVer5.12600.2180 offset 0004b0df
    >
    > One fix I tried was to open Command prompt and type
    > Start>Run>cmd>Enter and then
    > winmgmt /clearadap
    > winmgmt /kill
    > winmgmt /unregserver
    > winmgmt /regserver
    > winmgmt /resyncperf
    >
    > This didn't solve the problem. Any other ideas? Many thanks.
  2. Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

    Windows XP reports that Windows Management Instrumentation (WMI) might be
    corrupted?
    http://www.jsifaq.com/SUBK/tip5200/rh5281.htm

    [[You may receive any of the following error messages in Windows XP:
    Unable to view network properties. Windows cannot display the properties of
    connection. Windows Management Instrumentation (WMI) might be corrupted.
    Unable to view System Information (MSinfo32).

    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%\System32\Wbem\Repository folder
    is damaged.

    To fix this problem:
    1. Use the Start menu to right-click My Computer.
    2. Press the Manage item.
    3. Double-click Services and Applications in the left-hand pane.
    4. Press Services to expand it.
    5. Scroll to Windows Management Instrumentation in the right-hand pane and
    right-click it.
    6. Press Stop.
    7. Use Windows Explorer to delete all the files in the
    %SystemRoot%\System32\Wbem\Repository folder.
    8. Shutdown and restart your computer. The Windows Management
    Instrumentation service will start and the files will be re-created.]]
    ===

    I had a problem with WMI, I also had a problem deleting
    %SystemRoot%\System32\Wbem\Repository. I had to run Error Checking
    (Chkdsk.exe). And then try to delete the file.
    C:\WINDOWS\System32\Wbem\Repository\FS.
    -------

    From http://www.kellys-korner-xp.com/xp_w.htm

    WMI
    [[WMIPRVSE hosts the provider that sends your events on WinXP. On WinXP
    providers are out of process from the actual WMI service. You can specify
    the wbemConnectFlagUseMaxWait which will cause the timeout to be 2 minutes
    instead of the default DCOM one which is up to 20 minutes. What may help is
    to ping the remote machine first before attempting a ConnectServer.

    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 Console\Services 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

    HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Class. Open the class
    key and right click on the sub key 0000 and select permissions and make sure
    that the permissions for you [administrator] are "Full".]]

    --
    Hope this helps. Let us know.

    Wes
    MS-MVP Windows Shell/User

    In news:C1EF25AD-9978-43F2-AE94-25BBAE4BC054@microsoft.com,
    geneandjack <gcjstone@comcast.net(don''''tspam)> hunted and pecked:
    > I have a cable modem and Windows XP Home. I frequently get an error
    > message: "WMI has encountered a problem and needs to close."
    > Occasionally, the error also kicks me out of IE.
    >
    > The error signature is as follows:
    > szAppname:wmiprvse.exe SzAppVer:5.1.2600.2180
    > szModName:kernel32.dll szModVer5.12600.2180 offset 0004b0df
    >
    > One fix I tried was to open Command prompt and type
    > Start>Run>cmd>Enter and then
    > winmgmt /clearadap
    > winmgmt /kill
    > winmgmt /unregserver
    > winmgmt /regserver
    > winmgmt /resyncperf
    >
    > This didn't solve the problem. Any other ideas? Many thanks.
Ask a new question

Read More

Command Prompt Windows XP