Online - Data Retrieval Failures Occurred Windows Server 2022 |link| -

If Server Manager fails to pull performance data (CPU, RAM, Disk utilization), rebuilding the performance counters often resolves the block. Open as an Administrator. Navigate to the system directory: cd c:\windows\system32 Use code with caution. Rebuild the counters from the base system files: lodctr /r Use code with caution. Sync the counters with the WMI repository: winmgmt /resyncperf Use code with caution.

When a server has many roles (like in a Failover Cluster or Exchange DAG), the data packet exceeds the default WinRM limit. Open as Administrator on the target server . If Server Manager fails to pull performance data

Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = Use code with caution. Copied to clipboard Restart the Windows Remote Management service: powershell Restart-Service WinRM Use code with caution. Copied to clipboard Microsoft Q&A Discussion on MaxEnvelopeSize Rebuild the counters from the base system files:

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 Open as Administrator on the target server

If the error persists and Event Viewer points to a specific channel, resetting it can resolve the issue.

Windows Server 2022 , but older apps may default to TLS 1.0.