Online - Data Retrieval Failures Occurred Windows Server 2022 ^new^ (2025)
Key Event IDs to note: | Event ID | Source | Indication | |----------|--------|-------------| | 153 | disk | Disk has a bad block | | 129 | stornvme | Reset to NVMe device issued | | 512 | StorageSpaces | Failed to read metadata | | 134 | Ntfs | NTFS detected corruption |
For Storage Spaces:
The most frequent culprit. Windows Server 2022 has stricter iSCSI timeouts than previous versions. If the iSCSI initiator loses connectivity for more than LinkDownTime (default 15 seconds), the disk may stay online but fail metadata queries.
This is the most common fix for clustered environments (such as Hyper-V or DAGs) where the volume of managed data exceeds default limits. Log on to the target server showing the error. PowerShell as an Administrator. Run the following command to increase the size to 8192 KB: powershell Key Event IDs to note: | Event ID
If you are managing a cluster and the error persists after the previous steps, you can attempt a more advanced registry modification to disable the problematic Microsoft-Windows-Kernel-IoTrace/Diagnostic log directly.
Look for:
By following the structured diagnosis and solution paths provided in this guide, you can effectively resolve this error and maintain a fully functional Windows Server 2022 environment. This is the most common fix for clustered
Provide Microsoft with:
If any drive returns Pred Fail , replace immediately.
When this error appears, the Server Manager has been successfully able to connect to the target server (“Online”), but when it attempted to collect specific data points—such as event logs, performance counters, or the results of a Best Practices Analyzer (BPA) scan—the operation failed. Run the following command to increase the size
Windows Server 2022, Microsoft’s most robust on-premises server operating system to date, introduces enhanced security, hybrid capabilities, and improved storage performance. However, with complexity comes new edge cases in error handling. One of the most puzzling and frustrating alerts administrators encounter in Storage Spaces, Disk Management, or Failover Cluster Manager is the status:
: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client and set a new DWORD value named maxEnvelopeSize to 8192 (decimal).
Few messages in Windows Server 2022 are as deceptively alarming as You open the Disk Management console ( diskmgmt.msc ) or check the failover cluster manager, and instead of the comforting "Online (Healthy)" status, you are met with this ambiguous yet critical error.
: 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.