: The most frequent underlying trigger is a corrupted or broken metadata structure for the Microsoft-Windows-Kernel-IoTrace/Diagnostic event log. When Server Manager tries to read this channel, it breaks and halts data processing.
Detach and reattach the storage pool:
The Windows Remote Management service is disabled, misconfigured, or blocked by local policies.
If you performed an in-place upgrade to Windows Server 2022, removed features like "Media Foundation" or "File Services" may leave behind ghost registry entries. WINEVT\Channels
Incident Report: Online Data Retrieval Failures on Windows Server 2022 : The most frequent underlying trigger is a
To prevent data retrieval failures from recurring on your Windows Server 2022 infrastructure, implement the following practices:
Get-WinEvent -FilterHashtable @LogName='System'; StartTime=(Get-Date).AddHours(-2) | Where-Object $_.Message -match "disk
One of the most frequent culprits is the default packet size limit for . WinRM is the service that enables Server Manager to communicate with and manage remote servers. Its default maximum envelope size for data exchanges is 512,000 bytes . In environments with a large amount of management data, such as Storage Spaces Direct (S2D) clusters with many performance counters, this limit can be easily exceeded. When Server Manager requests data, the response packet from the managed node is too large to be processed, resulting in a retrieval failure. This is one of the most straightforward technical issues to diagnose and resolve.
Corrupted update components or specific faulty patches blocking service communication. If you performed an in-place upgrade to Windows
While the error appears in non-clustered environments, it is particularly common in Windows Server 2022 . In a cluster, Server Manager must retrieve consolidated data from multiple nodes, and its internal mechanisms are subject to the same constraints of WinRM packet sizes, permissions, and log integrity. Any break in this data flow from a single node can trigger the error for the entire cluster view. In some cases, you may see a bidirectional issue where Server DCB01 cannot retrieve data from DCB02, and vice versa .
To help narrow down your specific issue, please share a few more details:
Last updated: Q2 2025 – Applies to Windows Server 2022 (build 20348+)
Add the server's own Computer Account to the local Event Log Readers group via Computer Management > Local Users and Groups > Groups . Its default maximum envelope size for data exchanges
Server Manager often fails because it cannot access a specific event log provider. Event Viewer Applications and Services Logs ServerManager Operational for specific provider names. A common culprit is the Microsoft-Windows-Kernel-IoTrace/Diagnostic 2. Reset Corrupted Log Channels (Registry Fix)
You can also adjust the maxEnvelopeSize via the Registry. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client . If no value exists, create a new DWORD (32-bit) named maxEnvelopeSize with a decimal value of 8192 (or higher) and restart the WinRM service.
In some cases, especially with Exchange DAG members, the data payload exceeds the default size. Run PowerShell as Administrator and execute: