How to fix "The WS-Management service received a request which specified a maximum number of elements, but the service does not support this feature."

Error Description

This error typically occurs when a remote PowerShell session or a management tool (like Windows Admin Center, System Center, or third-party monitoring software) tries to query data using Windows Remote Management (WinRM). The client request specifies a parameter to limit or define the maximum number of elements returned in a single batch (pagination or enumeration optimization). However, the WinRM / WS-Management service on the target machine is configured with a policy or a version constraint that does not recognize or support this specific pagination feature, causing the request to fail.

Step-by-Step Fix

To resolve this issue, you need to adjust the WinRM configuration on the target machine to handle enumeration and optimization requests properly, or ensure that the service is running with appropriate compatibility settings.

Step 1: Open PowerShell as Administrator

1. Press the Windows Key on your keyboard.
2. Type powershell.
3. Right-click on Windows PowerShell from the search results.
4. Select Run as administrator.

Step 2: Check Current WinRM Configuration

Before making changes, you can view your current WS-Management configuration to ensure the service is active and see its properties.

1. Type the following command and press Enter:

   winrm get winrm/config

2. Look through the output to ensure the service is running and to check if any custom policies are restricting WS-Management behavior.

Step 3: Enable WinRM Compatibility Features

The error often happens because advanced enumeration features are blocked or unconfigured. You can reset and update the default WinRM configuration to ensure all standard features are supported.

1. Run the command to quickly configure WinRM with standard defaults:

   winrm quickconfig

2. If prompted to make changes or analyze the firewall exceptions, press Y and then Enter to confirm.

Step 4: Adjust MaxElements and Enumeration Timeout Settings

Sometimes explicit constraints on maximum elements or timeouts cause the WS-Management service to reject optimized queries. You can increase or explicitly define these parameters.

1. Run the following command to configure the default maximum number of elements per user if the query is hitting a system threshold:

   winrm set winrm/config/winrs '@{MaxShellsPerUser="30";MaxProcessesPerShell="25"}'

2. Next, adjust the enumeration timeout policy to give the service more time to process elements without failing the batch request:

   winrm set winrm/config/Timeout '@{Value="60000"}'

Step 5: Restart the WinRM Service

For the configuration changes to take full effect, you must restart the Windows Remote Management service.

1. Stop the service by running:

   net stop winrm

2. Start the service again by running:

   net start winrm

Step 6: Verify the Connection

Test the connection from the client machine or locally to ensure the error is resolved.

1. Run a local test command to ensure the service responds to enumeration queries:

   Get-WSManInstance -ResourceURI "winrm/config"

2. If you are connecting remotely, test the connection from the management machine using:

   Test-WSMan -ComputerName "TARGET COMPUTER NAME"

   (Replace TARGET COMPUTER NAME with the actual name or IP address of the machine you just configured).