Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic . Locate the DWORD and change its value from 1 to 0 .

If a job (like a Repair or Rebuild) is stuck, you may need to remove it (use caution): powershell Remove-StorageJob -StorageJob (Get-StorageJob) Use code with caution. 2. Force a Storage Scan Force Windows to re-enumerate the storage subsystem. powershell Update-StorageProviderCache Use code with caution. 3. Repair WMI Repository

If you are running a clustered environment, ensure you check the status of the Failover Cluster Manager, as issues there often propagate to Server Manager, as suggested in Microsoft's Community Hub .

Get-NetFirewallRule | Where-Object $_.Direction -eq "Outbound" -and $_.Action -eq "Block"

A storage pool or virtual disk has entered a "Degraded" or "Unhealthy" state, preventing WMI from querying it properly.

: If the host machine's computer object lacks direct permission to query its own security and diagnostic channels under tight security policies, Server Manager queries time out.

This guide helps you identify root causes and resolve the Windows Server 2022 error message “Online - Data retrieval failures occurred” (commonly seen with Storage Spaces, CSVs, or clustered storage).

Relaunch Server Manager as an and trigger a manual refresh (F5). 2. Verify and Reset Windows Remote Management (WinRM)

If you are seeing this error, the first step should be increasing the MaxEnvelopeSizekb on both the target and management servers to

If you recently upgraded, check for orphaned keys under ...\WINEVT\Channels for features no longer present on your system and rename them to -old to stop Server Manager from attempting to query them.

: In-place upgrades or migrations (e.g., VMware to Hyper-V) can leave behind orphaned registry entries for removed features that Server Manager still attempts to poll . Recommended Solutions 1. Reset Problematic Event Log Channels

The "Online - Data retrieval failures occurred" error in typically appears in Server Manager when it fails to pull inventory or status data from a local or remote node . This often stems from corrupted event log channels or WinRM limitations. 🛠️ Top Fix: Increase WinRM Envelope Size

the server. Upon restart, Windows typically resets this value to 1 and recreates the necessary metadata files.

If you are managing a Failover Cluster or Exchange DAG, the default data packet limit might be too low . Open as Administrator.