Online - Data Retrieval Failures Occurred Windows Server 2022

If you upgraded to Windows Server 2022 from an older version, "ghost" features that were removed during the upgrade might still have entries in the registry.

Before we dive into troubleshooting, let's discuss some common causes of online data retrieval failures on Windows Server 2022:

Administrative user permissions becoming restricted.

: This feature provides more predictable repair times, helping admins manage service levels during hardware failures or planned outages. If you upgraded to Windows Server 2022 from

The error message in Windows Server 2022 is a persistent issue frequently encountered in Server Manager , particularly in Failover Cluster environments. It indicates that while the server or cluster node is technically online, Server Manager cannot retrieve complete configuration data, role status, or event logs.

if ((Get-Disk -Number $disk.Number).OperationalStatus -match "DataRetrievalFailures") Set-Disk -IsOffline $false

Set-WSManInstance -ResourceURI winrm/config -ValueSet @MaxEnvelopeSizekb = "8192" Use code with caution. The error message in Windows Server 2022 is

Ensure the system account has access to the necessary files and folders.

Run the same command on the management server running Server Manager. Restart the WinRM service: Restart-Service WinRM . Refresh Server Manager. 2. Disable Corrupted Kernel-IoTrace-Diagnostic Log

The data retrieval process requires appropriate permissions to query system information and event logs via WinRM. The error can occur if the account used to manage the server does not have the necessary privileges on the target node. The remote server’s computer account, or the account you are logged in with, might be missing from the local security group, which is essential for accessing a wide range of event logs. Ensure the system account has access to the

Restart-Service -Name WinRM Restart-Service -Name Winmgmt -Force Use code with caution.

If no listeners are configured or you want to reset WinRM to its default state, run: powershell winrm quickconfig Use code with caution.