Part 1: Initial Troubleshooting

Ensure that the version of the Microsoft.NET Framework installed on the endpoint is up-to-date and functional. Repair the installation if necessary. For Datto RMM system requirements, refer to our Detailed Windows Requirements article.

Part 2: Discover if the WMI Repository is corrupted

The Datto RMM Agent imports information about an endpoint by querying the host device's Windows Management Instrumentation (WMI). Occasionally, the WMI can become corrupted and become unreadable. This affects the audit information that the Datto RMM Agent can gather and send to the platform.

There are many ways to check for WMI corruption. This process focuses on evaluating parts of the WMI that the Agent uses to retrieve audit information.

To check if the WMI Repository is corrupted, open an elevated command prompt on the device and run the following commands:

Normal output for each line should show a list of information about the area of the WMI queried. If any of your queries return one of the following error messages, then the WMI on your device is faulted, preventing the Datto RMM Agent from reading its data:

The interface is unknown

Invalid class

Invalid namespace \root\cimv2

Invalid namespace \root\default

Provider load failure

Specified cast is not valid

The specified module could not be found

Value does not fall within the expected range

The executable program that this service is configured to run in does not implement the service

The service did not respond to the start or control request in a timely fashion

Part 3: Attempt to fix the WMI Repository

Method 1: Verify and restore the repository

Perform the following steps from an elevated command prompt to verify and restore the WMI:

1. From the Windows Command Prompt, enter:

winmgmt /verifyrepository

2. If you see any output other than, “WMI repository is consistent,” run the following command to merge the readable content of the inconsistent repository into the rebuilt repository:

Winmgmt /salvagerepository

Method 2: Re-register all DLL files and recompile .MOF files

1. Run the following script to re-register all DLL files and recompile .MOF files in the C:\Windows\System32\Wbem folder on the endpoint.

You can save this script as a .BAT file and run it locally on the endpoint, from an elevated Windows Command Prompt session, or from the Desktop as an Administrator. You can also run it from the remote Agent shell or deploy it via a component.

3. Run an audit on the endpoint by selecting it in the Web Portal and clicking the Audit icon. To ensure a full audit, make sure that you do not select any other devices.

Method 3: Rebuild the WMI Repository

If all other troubleshooting described in this article has failed to resolve the issue, you can perform the following procedure to rebuild your WMI repository. Proceed with caution and at your own risk.

Before attempting this process, review the following warning from Microsoft:

If you suspect WMI or repository corruption, rebuilding the repository is the last thing you should do. Deleting and rebuilding the repository can cause damage to the system or to installed applications. Other steps should be taken first to eliminate other possibilities or to confirm you have repository corruption. An extremely large repository also creates problems and can sometimes be interpreted as a corrupt repository, which is not always the case. If issues are due to a large repository, rebuilding it is currently the only method available to reduce its size.

If this process fails to re-add any .MOF files, some installed programs on your endpoint may stop working and require reinstallation. Consider your options carefully before continuing.

1. To rebuild your WMI, run the following commands from an elevated command prompt on the affected endpoint: