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
The default maximum size for Windows Remote Management (WinRM) packets may be too small for the data being retrieved. The solution for me was as following and
Open PowerShell as an Administrator and run the following command to increase the envelope size to or higher: powershell Run the following standard repair tools: sfc /scannow
If you upgraded to Windows Server 2022 from an older version, "ghost" features that were removed during the upgrade might still have entries in the registry. WMI Fix Run winmgmt /salvagerepository Repairs the core
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.
Check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels for entries related to removed features like or older File Services .
The most frequent culprit for this error is a corrupted diagnostic log channel. You can often resolve this by temporarily disabling the channel and forcing a rebuild.