Inventory Scan failure - Asset Scan Locked (or) WMI Connection Failed


You are unable to proceed with manual / scheduled Inventory Scanning and you get an error - "Asset Scan Locked" (or) "WMI Connection Failed", during the process.


You will encounter this error due to one or more of the following reasons:

  1. Client machine is too slow due to reasons like high CPU/Memory utilization.
  2. WMI is not configured properly.
  3. WMI repository corrupted.


Execute the below command in cmd as an administrator:

  • For Windows XP
    • winmgmt /clearadap - Clears the WMI performance counter settings.
    • winmgmt /kill - Stops the WMI service.
    • winmgmt /unregserver - Unregister the WMI service.
    • winmgmt /regserver - Registers the WMI service.
    • winmgmt /resyncperf - Re-synchronizes performance counters.
  • For Windows 2003 Server
    • wmiadap.exe /c - This command re-compiles all MOF files
    • wmiadap.exe /f - This command reloads the performance library and rebuilds the performance counters.
    • lodctr /R - This command reloads all performance counters and their settings from the Windows registry.
  • For Windows 7 and Windows Server 2008
    • winmgmt /salvagerepository


To rebuild your WMI repository:

  • First, disable and stop the winmgmt service
  • Then, remove or rename the C:\Windows\System32\wbem\repository
  • Now, start the winmgmt service
  • Open command prompt as an administrator and execute the following command:
    • cd C:\Windows\System32\wbem\
    • for /f %s in ('dir /b *.mof') do mofcomp %s
    • for /f %s in ('dir /b en-us\*.mfl') do mofcomp en-us\%s
  • Open the performance monitor to verify the computer loading status. Note: If you face any issue in opening the performance monitor, troubleshoot it using this article.


To repair/re-sync your WMI repository:

  • Open the elevated command prompt and execute the following command to verify your WMI repository status:
    winmgmt /verifyrepository: If you receive the output as "WMI Repository is consistent", then the repository is not corrupted. Else, troubleshoot using the below given steps
  • Execute the following command:
    • winmgmt /salvagerepository: If the repository salvage fails to work, then run the below command to see if it resolves the issue:
    • winmgmt /resetrepository: This will display a “WMI Repository has been reset” message to indicate the function success.

After completing all the above steps, verify if WMI service is running in the services.

  • If the service is running, change the startup type to automatic
  • Restart the WMI service to proceed with asset scan.

If the above settings are already configured:

  • Press Windows and R button to open RUN dialog, and enter "wbemtest".
  • Click Connect and select Query.
  • Execute the query "select * from Win32_OperatingSystem".
  • If this works, resume your inventory scan operation.
Unable to resolve this issue?
If you feel this KB article is incomplete or does not contain the information required to help you resolve your issue, upload the required logs, fill up and submit the form given below. Include details of the issue along with your correct e-mail ID and phone number. Our support team will contact you shortly and give you priority assistance and a resolution for the issue you are facing.

 * Mandatory Fields

Other KB articles 24/5 Support

Support will be available 24hrs a day and five days a week (Monday through Friday), excluding USA & India public holidays.

Tel : +1-888-720-9500
Email :

Speak to us

  • Join the Endpoint Central Community, to get instant answers for your queries, register with our Forum.
  • Look out for the latest happenings in Desktop Management, follow our Tweets on Twitter.
  • Get to know the latest updates and Best Practices in Desktop Management through our Blog.