Online - Data Retrieval Failures Occurred Windows Server 2022 Jun 2026
| Cause | Description | |-------|-------------| | | Temporary link flaps, iSCSI session timeouts, or FC/FCoE signal issues | | Corrupted metadata | Storage Spaces or CSV cache metadata mismatch | | Disk firmware issues | Outdated or buggy firmware on SSDs/HDDs | | Driver incompatibility | Storage controller drivers not fully compatible with Windows Server 2022 | | Sector read failures | Bad blocks in critical metadata regions (e.g., GPT header, LDM database) | | MPIO misconfiguration | Improper Multipath I/O settings causing path failures |
Capture with Fiddler or Wireshark. Enable logging: | Cause | Description | |-------|-------------| | |
If Server Manager can't pull logs because the server account lack rights, adding permissions often ends the blockage. Microsoft Learn On the managed target server, open Computer Management Navigate to System Tools Local Users and Groups Double-click the Event Log Readers Windows should automatically reset the value to 1
Get-PhysicalDisk | Select FriendlyName, OperationalStatus, HealthStatus, CannotPoolReason Get-VirtualDisk | Select FriendlyName, OperationalStatus, HealthStatus, FootprintOnPool StartTime=(Get-Date).AddHours(-2) | Where-Object storahci
on Windows Server 2022 and been greeted by a red "Refresh failed" notification or the dreaded "Online – Data retrieval failures occurred"
the server. Windows should automatically reset the value to 1 and rebuild the clean metadata.
Get-WinEvent -FilterHashtable @LogName='System'; StartTime=(Get-Date).AddHours(-2) | Where-Object storahci