The default maximum size for Windows Remote Management (WinRM) packets may be too small for the data being retrieved.
If the registry and WinRM fixes don't work, the issue may lie deeper in the WMI repository. The default maximum size for Windows Remote Management
The solution for me was as following and is important to follow the order as below: Add the affected node itself (computer object) Microsoft Community Hub Run the following standard repair tools: sfc /scannow
Always ensure basic system integrity isn't the root cause. Run the following standard repair tools: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth Key Action Why it Works Registry Fix Set Kernel-IoTrace/Diagnostic to 0 Forces rebuild of corrupted log metadata. WinRM Fix Increase MaxEnvelopeSizekb to 8192 Allows larger data payloads to pass through. Permissions Add server to Event Log Readers Resolves access denied errors for WinRM. WMI Fix Run winmgmt /salvagerepository Repairs the core management data provider. WMI Fix Run winmgmt /salvagerepository Repairs the core
the server. Upon restart, Windows typically resets this value to 1 and recreates the necessary metadata files.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic . Locate the DWORD and change its value from 1 to 0 .