Server manager not working properly after installing WMIC

Panagiotis Efrosinis 20 Reputation points
2026-09-10T06:40:34.65+00:00

Windows server 2025 after installing WMIC the server manager not working and the message is " Online - Data retrieval failures occured" and the if I select from the menu "Manage" the option "Add Roles anf Features" this option is not working.

Also in the event viewer the DFSR service outputs the following message "The DFS Replication service failed to register the WMI providers. Replication is disabled until the problem is resolved. "

Thanks in advance.

Panagiotis Efrosinis

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments
Answer accepted by question author
Domic Vo 32,140 Reputation points Independent Advisor
2026-09-10T07:12:03.93+00:00

Hello Panagiotis,

the issue you are describing is directly tied to the installation of WMIC on Windows Server 2025. WMIC is deprecated and not included by default in modern Windows builds. When you manually add WMIC binaries or legacy WMI components, it can break the WMI provider registration process. Server Manager and DFSR both rely heavily on WMI providers to query system state. If those providers fail to register, you see exactly the behavior you mentioned: Server Manager showing “Online – Data retrieval failures occurred” and DFSR logging “The DFS Replication service failed to register the WMI providers. Replication is disabled until the problem is resolved.”

The root cause is that WMIC installation overwrites or misaligns the WMI repository and provider registration under %SystemRoot%\System32\wbem and the registry keys under HKLM\SOFTWARE\Microsoft\WBEM. DFSR’s provider (DFSR-WMI) fails to register correctly, which disables replication. Server Manager queries also fail because the CIM repository is inconsistent.

The recommended remediation is to remove WMIC completely and restore the WMI repository. First, uninstall any WMIC package you added. Then run winmgmt /verifyrepository to check the repository state. If it reports inconsistency, run winmgmt /salvagerepository. In some cases, you may need to re-register the DFSR WMI provider manually using regsvr32 dfsrprov.dll from %SystemRoot%\System32. After that, restart the DFSR service and Server Manager should resume normal operation.

Microsoft does not support reintroducing WMIC on Server 2025, as it is fully deprecated. The supported way to query WMI is through PowerShell (Get-CimInstance, Get-WmiObject is also deprecated). If you need WMIC functionality, you should migrate scripts to PowerShell equivalents. Continuing to use WMIC will cause exactly these kinds of failures because the binaries are not maintained for current builds.

If after salvaging the repository and re-registering providers the issue persists, the only guaranteed fix is to remove WMIC and perform a repair install of the OS to restore the default WMI provider set. This is documented in Microsoft’s guidance for DFSR and WMI provider failures.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Panagiotis Efrosinis 20 Reputation points
    2026-09-10T16:07:50.1733333+00:00

    Hi Dominic

    Thank you for your reply. The problem with your instructions has been resolved. Your help was essential in resolving our issue with Server Manager and DFSR.

    Thank you very much.

    Panagiotis Efrosinis .

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.