How to run wmi service in a standalone host process?
Translate this pageArabicBulgarianCatalanChinese SimplifiedChinese TraditionalCzechDanishDutchEstonianFinnishFrenchGermanGreekHaitian CreoleHebrewHindiHungarianIndonesianItalianJapaneseKoreanLatvianLithuanianNorwegianPolishPortugueseRomanianRussianSlovakSlovenianSpanishSwedishThaiTurkishUkrainianVietnamese
Check out this page in {0} translated from {1}translated fromOriginal:Translated:Automatic translation powered by Microsoft® TranslatorStart translatingStop translatingCloseClose and show original pageSelect
Open services.msc console, you can find Windows Management Instrumentation service, I.E., "WMI", whose name is winmgmt, it has following description,
"Provides a common interface and object model to access management information about operating system, devices, applications and services. If this service is stopped, most Windows-based software will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start."
Winmgmt service usually was hosted together with other services, sometime in order to debug wmi service process conveniently, you might want to host the winmgmt service in a standalone host process. In order to achieve that, you can try either of the following in commandline window,
1) Run following commands,
net stop winmgmt
winmgmt /standalonehost
net start winmgmt
OR 2)
net stop winmgmt
sc config winmgmt type= own
net start winmgmt
After that, you can debug the wmi service process by running following commandline "windbg.exe -psn winmgmt"
Of course, approach (2) can apply to any other service, such as winrm service.