首先嘗試手動(dòng)啟動(dòng)WMI服務(wù)，若失敗則進(jìn)入下一步；2. 使用WMI控制臺(tái)（wmimgmt.msc）檢查錯(cuò)誤以確認(rèn)是否存在WMI提供程序連接問題；3. 以管理員身份運(yùn)行命令提示符，停止winmgmt服務(wù)，重命名%windir%\System32\wbem\repository文件夾為repository.old，重啟服務(wù)以重建倉庫并重啟電腦；4. 在管理員命令提示符中進(jìn)入wbem目錄，逐一注冊(cè)所有DLL和EXE文件，然后執(zhí)行winmgmt /salvagerepository和winmgmt /resetrepository修復(fù)WMI倉庫；5. 運(yùn)行sfc /scannow和DISM /Online /Cleanup-Image /RestoreHealth檢查并修復(fù)系統(tǒng)文件；6. 進(jìn)行全盤殺毒掃描，并檢查組策略或安全軟件是否禁用了WMI；7. 若存在權(quán)限問題，可運(yùn)行winmgmt /resetsecurity重置WMI安全設(shè)置，或使用PowerShell測(cè)試WMI訪問，若仍失敗可嘗試系統(tǒng)還原，多數(shù)問題通過重建倉庫和重新注冊(cè)WBEM組件即可解決，整個(gè)過程需管理員權(quán)限并重啟系統(tǒng)結(jié)束。

If you're seeing the error "The Windows Management Instrumentation (WMI) service is not running" on your Windows PC, it usually means the WMI service has been stopped or is having trouble starting. This can break system tools, cause performance issues, or prevent software from working properly (like Task Manager, Event Viewer, or system monitoring tools).

Here’s how to fix it step by step:

1. Start the WMI Service Manually

First, check if the WMI service is simply stopped and can be started:

1. Press Win R, type services.msc, and press Enter.
2. Scroll down and find Windows Management Instrumentation.
3. Right-click it and select Start.
4. If it starts successfully, set its Startup type to Automatic.
5. Reboot and check if the issue returns.

?? If the service fails to start or crashes immediately, move to the next steps.

2. Run the WMI Diagnostic Tool (WMI Control)

Use the built-in WMI Control to check for corruption:

1. Press Win R, type wmimgmt.msc, and press Enter.
2. Right-click WMI Control (Local) and select Properties.
3. Go to the General tab and check for any error messages.
4. If you see something like “Error: Cannot connect to WMI provider,” it indicates corruption.

This doesn’t fix the issue but helps confirm it.

3. Rebuild the WMI Repository

A corrupted WMI repository is a common cause. Rebuilding it often resolves the issue.

?? Important: This will reset all WMI settings and custom namespaces.

Steps:

1. Open Command Prompt as Administrator:

   • Press Win, search for cmd, right-click and choose Run as administrator.

2. Stop related services:

   net stop winmgmt

3. Navigate to the WMI repository folder and rename it:

   cd /d %windir%\System32\wbem
   ren repository repository.old

4. Restart the WMI service (this will rebuild the repository):

   net start winmgmt

5. Wait a few minutes — Windows will automatically recreate the repository.

6. Reboot the PC.

? After reboot, monitor if WMI functions normally.

4. Register WMI DLLs and Repair WBEM Components

Sometimes WMI components become unregistered. Re-register them:

1. Open Command Prompt as Admin.

2. Run these commands one by one:

   cd /d %windir%\System32\wbem
   for %i in (*.dll) do regsvr32 /s %i
   for %i in (*.exe) do %i /RegServer

   This registers all DLLs and re-registers executables like wmiprvse.exe.

3. Then re-register WMI itself:

   winmgmt /salvagerepository
   winmgmt /resetrepository

   resetrepository safely rebuilds the repo (safer than manual rename in some cases).

5. Run System File Checker (SFC) and DISM

Corrupted system files can break WMI.

1. In Admin Command Prompt:

   sfc /scannow

2. After SFC finishes, run:

   DISM /Online /Cleanup-Image /RestoreHealth

3. Reboot and test WMI again.

6. Check for Malware or Unauthorized Changes

Malware or third-party software (especially aggressive optimizers or antivirus tools) can disable WMI.

• Run a full scan with Windows Defender or a trusted antivirus.
• Check Group Policies or security software settings that might restrict WMI.

7. Permissions Issue? Try WMI Repair Script (Advanced)

If you suspect permission problems in the WMI namespace:

1. Run this in Admin CMD:

   winmgmt /resetsecurity

   This resets WMI namespace security to defaults.

2. You can also use PowerShell to check access:

   Get-WmiObject -Class Win32_ComputerSystem

   If it fails, WMI is still broken.

Final Notes

• The WMI service is critical. Never disable it permanently.
• Avoid third-party "registry cleaners" — they often cause WMI issues.
• If nothing works, consider system restore to a point when WMI was working.

Most cases are fixed by rebuilding the repository and re-registering WBEM files. It’s not complex, but requires admin access and a reboot.基本上就這些。

以上是如何修復(fù)' Windows Management Instrumentation（WMI）服務(wù)未運(yùn)行”的詳細(xì)內(nèi)容。更多信息請(qǐng)關(guān)注PHP中文網(wǎng)其他相關(guān)文章！