The is a critical database that stores information about the system's hardware, software, and configuration. If this repository becomes corrupted, any tool relying on WMI for data collection—including Server Manager—will experience failures. WMI errors are often flagged in the Event Viewer with Event ID 5858 .
Look for a subfolder named Results within these role directories.
| Area | Best Practice | |------|----------------| | | Set LinkDownTime to at least 30s. Enable MPIO. Avoid jumbo frames unless fully switched. | | Storage Drivers | Use Windows Server 2022-certified drivers only. Avoid old StorPort 2012 drivers. | | S2D | Ensure all disks have identical firmware. Run Get-StorageJob weekly. | | Backup Agents | Exclude disk metadata folders from on-access scanning. | | Monitoring | Alert on Event ID 508 (VDS), 129 (storahci), and 153 (disk). |
Are there any specific showing up in the Event Viewer under Applications and Services Logs > Microsoft > Windows > ServerManager-DeploymentProvider ?
If the salvage fails, force a rebuild of the repository by running: winmgmt /resetrepository Use code with caution. Reboot the server to finalize the WMI rebuild. Step 3: Reset WinRM and PowerShell Remoting
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 .
Use sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to fix general OS corruption that may impact management providers. If you'd like, let me know: Is your server part of a Failover Cluster ?
The WMI service, which provides management data, may have become corrupted.
Schedule via Task Scheduler with trigger: On event – Log: System, Source: Ntfs, Event ID: 98 .
If this fails with "ERROR_IO_DEVICE" but Get-Disk succeeds, the issue is at the SCSI command layer—not the disk.
: Change the Enabled DWORD value from 1 to 0 and reboot . Windows typically resets this to 1 automatically upon a successful reboot with clean metadata . 2. Increase WinRM MaxEnvelopeSize
: The account running Server Manager may lack rights to access specific event logs on remote nodes.
For issues specifically involving Kernel-IoTrace , you can disable the channel in the Registry Editor to force a rebuild on reboot:
In Windows Server 2022, this issue is commonly linked to packet size limits, especially in clustered environments, or corrupted WMI/Event logs. Common Causes for Data Retrieval Failures