Windows Management Instrumentation Service cannot be started

ArticleDirectory

• How to fix Windows Management Instrumentation (Wmi)

---- 1

 

Windows Management Instrumentation Service cannot be started. solution:

 

Go to C:/Windows/system32/WBEM/Repository, delete all the files, and restart the computer. because the damaged file has been deleted, it will be created again when the computer is restarted. restart the Windows Management Instrumentation Service.

 

 

---- 2

 

What are the solutions to Windows Management Instrumentation Service failure on a local computer?

Solution
1. Double-click the service you want to enable and select the dependency tab in the pop-up panel to view the services that the service depends on. Enable all dependent services, and then manually restart the services.

2. If "error 1075: dependency service does not exist or is marked as deleted" is still encountered after step 1, it indicates that the dependency service is not started. Because the dependent services listed in step 1 are only recognized by the system and are the most basic. To view the complete list of services that a service (assuming its name is XXX) depends on, perform the following operations:
Start-> run, and press Regedit (regedit32 is recommended, if this command is available). Press enter to find HKEY_LOCAL_MACHINE/system/CurrentControlSet/XXX, double-click the dependonservice item of XXX to view the list of dependent services.

3. There are two solutions:
3.1) Launch all the dependent services like step 1 (not recommended)
3.2) delete the list of redundant dependent services in dependonservice and retain only the most basic dependent services. Note that the end of the service list should be a space or a blank line.
You can also run SC config XXX depend = YYY in "start-> Run" to set the dependency service YYY of service XXX. Similarly, "depend =" must be followed by a space.

[Example]
[Symptom] Computer poisoning: The printer disappears after virus removal. When adding a printer, the system prompts "error! Cannot add ". When printing through the network, the system prompts "error: printer backgroundProgramNot running. ".
The printer background service is generally the Print Spooler service. In "start-> Settings-> Control Panel-> management tools-> services", start Print Spooler.
However, unexpectedly, the print spooler cannot be started successfully. The error message is: "error 1075: dependency service does not exist or has been marked as deleted. "

[Solution]
1. According to step 1, we found that print spooler depends on the RPC service (RPCSS ). However, Print Spooler cannot be started after the RPCSS is started.
2. According to step 2 above, we found that the dependonservice of Print Spooler is RPCSS and lexbces (it may also be other services; this is case-insensitive ).
3. There are two solutions:
3.1) install the lexbces service and start
3.2) Remove lexbces from the service list and retain it as "RPCSS". Pay attention to the Space following it. You can also use the blank line (enter key) instead of the space (space key ).
Alternatively, run SC config Spooler depend = RPCSS, and pay attention to "depend =" instead of "depend = ".

 

 

 

 

 

--- 3

 

WMI depends on two services. One is Event Log Service and the other is RPC, which is unlikely to be started. However, you can check whether the two services have been opened.
WMI corruption may occur because the file in the % SystemRoot % system32wbemrepository folder is damaged. You can refer to the following method to fix WMI.
Http://meifazhan.blog.ccidnet.com/blog/ccid/do_showone/tid_5404.html
In fact, I think that the installation of the network and the destruction of WMI are all due to a problem, which may be caused by a problem in the network-related part of your system. RPC is also a network service.
I suggest you first kill the virus and then use the XP installation disk to repair the system. If it doesn't work, reload the network-related components in the system.

How to fix Windows Management Instrumentation (Wmi)

When you use Windows XP, you may receive one of the following error messages: Unable to view network properties. Windows cannot display the properties of this connection. Windows Management Instrumentation (Wmi) might be too upted. Unable to view system information (msinfo32) If you try to run Windows Management Instrumentation (Wmi), you may receive the following error message: failed to connectLocal ComputerDue to WMI: Generic failure. Note:: To Run WMI, enterWmimgmt. MSCAnd press Enter. [@ More @] Cause This behavior occurs when the file in the % SystemRoot % system32wbemrepository folder is corrupted. You may receive this error message repeatedly because winmgmt.exe views these files every 30 to 60 seconds. To solve this problem, delete these files and recreate them in the % SystemRoot % system32wbemrepository folder. To do this, follow these steps: ClickStart, Right-clickMy computer. On the shortcut menu, clickManagement. In the left pane of the Computer Management Console, double-click "services and applications ". Under services and applications, clickService. In the right pane of the Computer Management Console, right-clickWindows Management Instrumentation. On the shortcut menu, clickStop. Start Windows Resource Manager and find the % SystemRoot % system32wbemrepository folder. Delete all files in the % SystemRoot % system32wbemrepository folder. Restart the computer. When the computer restarts, the deleted files are created again. Note:: Windows Management Instrumentation Service automatically starts when you restart your computer. Applicable: Microsoft Windows XP Home Edition Microsoft Windows XP Professional