Backup Fails with WMI Errors

In some cases, the Guardian Neo program may produce an error caused by a malfunction in Windows Management Instrumentation (WMI). For example, an operation fails with the message "WMI 'ExecQuery' failed".

Error code: 1012; Module: 20 
LineInfo: 0xC523D9A02D03D55C 
Fields: {"Query":"SELECT * FROM Win32_OperatingSystem","$module":"mms_vsa64_3917"} 
Message: WMI 'ExecQuery' failed.


Error code: 1012
Module: 20
LineInfo: 0xC523D9A02D03D55C
Fields: {"$module":"mms_vsa64_12420","Query":"SELECT * FROM Win32_OperatingSystem"}
Message: WMI 'ExecQuery' failed for query '%ls'.


A Windows Management Instrumentation (WMI) query has failed. The WMI repository may be corrupted or it works incorrectly


WMI is Windows Management Instrumentation, Guardian Neo Program uses its functionality on Windows machines to get information about disks, systems, and services. The WMI errors indicate that Guardian Neo Agent had attempted a query via WMI tools and WMI tools failed to process it.

This article describes how to troubleshoot WMI errors.

Confirm WMI is broken

  1. Launch the WMI MMC snapin: go to Start -> Run -> type wmimgmt.msc 
  2. Right click WMI Control (Local) and click Properties



  1. Alternatively, you can open WMI properties by going to Control Panel -> Administrative Tools -> Computer Management. In the left-hand pane, click Services & Applications -> WMI Control, right-click and select Properties.

  2. If WMI is working correctly, you will see a Successfully connected window as shown below.



  1. If you see an Invalid class or any other error message then WMI is not working properly

Enabling WMI event tracing

By default, WMI events are not traced. This procedure describes how to use Event Viewer to enable WMI event tracing and locate WMI events. 

  1. Open Event Viewer: 

    - Press Win + R;
    - in the Run window that opens, type eventvwr.msc and press Enter

  2. On the View menu, click Show Analytic and Debug Logs:


  1. Locate the Trace channel log for WMI under Applications and Service Logs > Microsoft > Windows > WMI Activity.
  2. Right-click the Trace log and select Properties. Click the Enable Logging check box to start the WMI event tracing.



  1. Reproduce the issue.
  2. WMI events appear in the event window for WMI-Activity. Double-click an event in the list to see the detailed information. 
  3. In some cases, the event will contain instructions on how to resolve a particular error. For other events, use the Event ID and Source in your search to find additional information online.


How to check WMI repository consistency

In Windows Vista or higher, you can check if the repository is damaged with the following command from the elevated Command Prompt (Start -> Search -> type "cmd" -> right-click and select Run as administrator):

winmgmt /verifyrepository

If the repository is not corrupted, a “WMI Repository is consistent” message will be returned. If the repository is consistent, you need to troubleshoot more granularly using the WMI Events in Event Viewer.

If the command returns that the WMI database is in an inconsistent state, perform recovery of the repository as described below.


NB// Rebuilding WMI repository manually can result in some 3rd party products not working until reinstallation. 


1. Disable and stop the WMI service.

     sc config winmgmt start= disabled

(note the blank space before disabled)

     net stop winmgmt

(this will also ask to stop Acronis services)

 2. Run the following commands

     Winmgmt /salvagerepository %windir%\System32\wbem      

     Winmgmt /resetrepository %windir%\System32\wbem

3. Re-enable the WMI service and reboot the machine

     sc config winmgmt start= auto

 If the problem remains after consistency check, rebuild the WMI repository:

 1. Disable and stop the WMI service.

     sc config winmgmt start= disabled 

     net stop winmgmt

2. Rename the repository folder located at %windir%\System32\wbem\repository to repository.old.

3. Re-enable the WMI service.

     sc config winmgmt start= auto

 4. To recreate the repository, you need to run a WMI-using application. The simplest way to do this is to launch the WMI MMC snapin again (Start -> Run -> wmimgmt.msc), right click WMI Control (Local), and click Properties. There will be a delay of some seconds while a new repository is created. 




  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

New Software 2018 - How to recover / restore files customer login

To Recover / restore files from customer login: When logged in, You will see you have an option...

New software 2018 - Initial setup + Installing Software and adding a backup

Installing Software - Initial Setup Initially as client/ customer you will get an activation...

Guardian Neo Backup of SQL instance fails with "There are no SQL writers"

Symptoms You have installed Guardian Neo Backup agent for SQL and created a backup plan for a...

New Software 2018 - Reseller Rebranding

Reseller BrandingOnce you have logged in, Go to Settings > Branding on the left side panel...