Online - Data Retrieval Failures Occurred Windows Server 2022 Jun 2026

Did this start after an or a specific update ? data retrieval failures occurred showing in server manager

Run the Deployment Image Servicing and Management (DISM) tool to repair the system image: DISM /Online /Cleanup-Image /RestoreHealth Use code with caution.

If you are running a Failover Cluster, the issue might be a stale cluster state. powershell Get-StorageProvider | Register-StorageProvider Use code with caution. Check Cluster Disk State: powershell

Verify your user account still has Administrator privileges.

If you performed an in-place upgrade to 2022, outdated keys in ...\WINEVT\Channels from removed features (like File Services or Media Foundation) can trigger this error. 🛡️ Best Practices to Prevent Future Failures Did this start after an or a specific update

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

If you are currently looking at your console and trying to figure out which path to take, tell me:

Relaunch Server Manager after the repair is complete to see if data begins to flow.

A recent Windows security update ([KB number], installed on [date]) modified the default Schannel TLS cipher suite order , disabling older but still required cipher suites (e.g., TLS_DHE_* and some TLS_ECDHE_* with weak key exchange). Several external endpoints had not yet upgraded to fully modern suites. 🛡️ Best Practices to Prevent Future Failures This

Once you identify where the failure happens (network, TLS, auth, or app-specific), the fix becomes clear. If the issue persists, collect a and Event Logs for the exact time of failure and share with your network or security team.

If you are encountering this error, which of the following best describes your scenario: Did this happen after a recent ? Is it happening on all servers or only one ? Are you using Dell hardware with this error?

Sometimes the error is caused by a corrupted XML report file generated during a background BPA scan. Removing these files forces Server Manager to create clean entries.

: The server's computer account may lack the necessary rights to read its own event logs through WinRM . Formatted data from missing

A known bug involves the Microsoft-Windows-Kernel-IoTrace/Diagnostic channel.

A corrupted WMI repository often causes Server Manager to report false failures. Run Command Prompt as Administrator. Run the following commands: winmgmt /verifyrepository

Windows Management Instrumentation (WMI) corruption breaks data polling.

Navigate to the following Microsoft Learn support page for registry modification details.

Formatted data from missing, stuck, or corrupted update packages blocks the retrieval pipeline.