WmiServiceStateCheck check whether the WMI Service is started and running on the computer. Failed to start WindowsManagementInstrumentation (WMI) service. To continue the installation, you must locate the problem and fix the WindowsManagementInstrumentation (WMI) service. The error is as follows: can be stopped and started normally, package
WmiServiceStateCheck check whether the WMI Service is started and running on the computer. Failed to start Windows Management Instrumentation (WMI) service. To continue the installation, you must locate the problem and fix the Windows Management Instrumentation (WMI) service. The error is as follows: can be stopped and started normally, package
WmiServiceStateCheck |
Check whether the WMI Service is started and running on the computer. |
Failed |
Windows Management Instrumentation (WMI) service cannot be started. To continue the installation, you must locate the problem and fix the Windows Management Instrumentation (WMI) service. |
The error is as follows:
It can be stopped, started, and restarted properly.
Google Now
Method 1:
The following script is useless:
@echo on
cd /d c:\temp
if not exist %windir%\system32\wbem goto TryInstall
cd /d %windir%\system32\wbem
net stop winmgmt
winmgmt /kill
if exist Rep_bak rd Rep_bak /s /q
rename Repository Rep_bak
for %%i in (*.dll) do RegSvr32 -s %%i
for %%i in (*.exe) do call :FixSrv %%i
for %%i in (*.mof,*.mfl) do Mofcomp %%i
net start winmgmt
goto End
:FixSrv
if /I (%1) == (wbemcntl.exe) goto SkipSrv
if /I (%1) == (wbemtest.exe) goto SkipSrv
if /I (%1) == (mofcomp.exe) goto SkipSrv
%1 /RegServer
:SkipSrv
goto End
:TryInstall
if not exist wmicore.exe goto End
wmicore /s
net start winmgmt
:End
No error reported
Method 2: The method here is useless.
Http://social.technet.microsoft.com/Forums/en-US/itprovistasetup/thread/11d6d64e-543b-40cd-a0f6-ba97c3806fbb/
1) Start the computer and press F8 on boot up and select Safe Mode.
2) In the start menu type "cmd" (without quotes) and on the top search result, right click the program icon and choose Run as administrator
3) Type "net stop winmgmt" (without quotes) and press Enter to make certain the WindowsManagementInstrumentation (WMI) service is not running.
4) Open a Windows Explorer and locate the path to C:\ windows\system32\WBEM\ folder and rename the Repository folder to something else like RepositoryOLD (right click and choose 'Rename Folder').
5) Reboot and restart as normal.
6) In the start menu type "cmd" (without quotes) and on the top search result, right click the icon and choose Run as administrator
7) Type "net stop winmgmt" (without quotes) and press enter to stop the WMI service.
8) Type "winmgmt /resetRepository" (without quotes) and restart the computer.
Each step prompts a success. The last step is to reset the instance and restart the computer to run the SQL installer.
Method 3:
Reference: https://connect.microsoft.com/SQLServer/feedback/details/682543/wmi-service-cannot-be-started-when-installing-sql-server-denali-ctp3
Select name from WIN32_SERVICE where name = 'winmgmt'
Win32_Service.Name='winmgmt'
The same errors as this one include running powershell
Ps c: \ Windows \ System32 \ wbem> get-wmiobject-Query "select name from WIN32_SERVICE where name = 'winmgmt '"
Get-WmiObject: the instance where the object reference is not set.
Location line: 1 character: 14
+ Get-wmiobject <-Query "select name from WIN32_SERVICE where name = 'winmgmt '"
+ CategoryInfo: NotSpecified: (:) [Get-WmiObject], NullReferenceException
+ FullyQualifiedErrorId: System. NullReferenceException, Microsoft. PowerShell. Commands. GetWmiObjectCommand
The following code is correct when running code 2.0 3.5:
using System;
using System.Management;
public class Sample
{
public static void Main()
{
ManagementClass c = new ManagementClass("Win32_Process");
foreach (ManagementObject o in c.GetInstances())
Console.WriteLine(
"Next instance of Win32_Process : {0}", o["Name"]);
Console.ReadKey();
}
}
No output exception
------------- It seems that the system is reinstalled.
Let's take a look.