How to fix "WinRM cannot process the request because the WMI object contains too many levels of nested embedded objects."

Error Description

The error message "WinRM cannot process the request because the WMI object contains too many levels of nested embedded objects" occurs when a Windows Remote Management (WinRM) query attempts to retrieve Windows Management Instrumentation (WMI) data that exceeds the default serialization depth limit.

WinRM uses an XML-based protocol (WS-Management) to transmit data. To prevent denial-of-service (DoS) attacks and excessive memory consumption, Windows enforces a strict security limit on how deeply objects can be nested inside one another during this translation process. When a complex query (often related to deeply nested system components, clustering, or third-party monitoring agents) crosses this threshold, WinRM halts the operation and throws this error.

Step-by-Step Fix

To resolve this issue, you must manually increase the maximum depth allowed for nested WMI objects in the WinRM configuration. This change must be applied via an administrative command-line interface.

Step 1: Open PowerShell as Administrator

1. Press the Windows Key on your keyboard.
2. Type PowerShell into the search bar.
3. Right-click on Windows PowerShell from the search results.
4. Select Run as administrator.
5. Click Yes if the User Account Control (UAC) prompt appears.

Step 2: Check the Current MaxEnvelopeSize (Optional)

Before making changes, you can view your current WinRM configuration limits by running the following command:

winrm get winrm/config

Look through the output for the MaxEnvelopeSizekb or XML processing limits under the soap or xml nesting sections to understand your baseline.

Step 3: Increase the XML Nesting Depth Limit

Run the following command to increase the max structural depth limit allowed by the WinRM service. By default, this value is often set to 10. Increasing it to 30 or higher typically resolves complex nested object errors:

winrm set winrm/config @{MaxEnvelopeSizekb="8000"}

Next, explicitly configure the XML processing depth limit using this command:

winrm set winrm/config/soap @{MaxXMLNestingDepth="30"}

(Note: If your specific Windows build does not support the MaxXMLNestingDepth property directly via that path, proceed to Step 4 to apply the configuration via the Windows Registry).

Step 4: Alternative Registry Fix (If PowerShell Commands Fail)

If the WinRM command-line utility rejects the property syntax, you can apply the nesting limit directly via the Windows Registry:

1. Press Windows Key + R, type regedit, and press Enter to open the Registry Editor.
2. Navigate to the following registry path: HKEY LOCAL MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\
3. Look for a key or DWORD named MaxXMLNestingDepth.
4. If it does not exist, right-click on the blank space in the right pane, select New > DWORD (32-bit) Value, and name it MaxXMLNestingDepth.
5. Double-click MaxXMLNestingDepth, change the Base to Decimal, set the Value data to 30 (or higher, up to 64), and click OK.

Step 5: Restart the WinRM Service

For the changes to take effect, you must restart the Windows Remote Management service. Run these commands in your administrative PowerShell window:

Stop-Service winrm
Start-Service winrm

Alternatively, you can use the standard command prompt syntax:

net stop winrm
net start winrm

Step 6: Verify the Resolution

Rerun the application, script, or monitoring tool that originally triggered the error. The WMI object should now serialize successfully through WinRM without hitting the nesting bottleneck.