How to fix "The WS-Management service cannot process the request. The resource URI for an Enumerate operation must not contain keys."

Description of the Error

This error occurs in Windows PowerShell or Windows Remote Management (WinRM) when an Enumerate operation (such as Get-WSManInstance or Get-CimInstance) is executed with a Resource URI that mistakenly includes specific instance keys.

In WS-Management protocol rules, an Enumerate operation is used to query all instances or a collection of objects from a specific class provider. Because it is meant to return a list of multiple items, the Resource URI must point generally to the resource type or class container. If you include specific selectors or keys (like a specific IP address, session ID, or service name) inside the URI string during an enumeration request, the WinRM service rejects it because keys are strictly reserved for Get, Put, or Delete operations targeting a single, specific instance.

Step-by-Step Easy Fix

To resolve this issue, you must modify your PowerShell script or command to remove instance-specific identifiers from the URI parameter when listing items, or switch to the correct operation method if you only want to target a single item.

Method 1: Remove Keys from the Resource URI (For Listing Multiple Items)

If your goal is to list or enumerate all instances, ensure your -ResourceURI string stops at the class or container level.

1. Locate your current command. It likely looks similar to this incorrect example:

   Get-WSManInstance -ResourceURI "winrm/config/listener?Address=*+Transport=HTTPS" -Enumerate

   Note: The `?Address=+Transport=HTTPS` part represents the keys causing the failure.*

2. Modify the URI to exclude the keys. Strip away everything starting from the question mark (?):

   Get-WSManInstance -ResourceURI "winrm/config/listener" -Enumerate

3. Run the corrected command. The WinRM service will now successfully process the enumeration and list all available listeners.

Method 2: Change the Operation to "Get" (For Targeting a Single Item)

If you intentionally included keys because you only want information about one specific configuration instance, you must drop the -Enumerate switch and use the standard retrieval method.

1. Locate your command using the Enumerate switch:

   Get-WSManInstance -ResourceURI "winrm/config/listener?Address=*+Transport=HTTP" -Enumerate

2. Remove the -Enumerate switch (or replace it with specific instance selectors if using CIM/WMI cmdlets) so Windows knows you are fetching a single object:

   Get-WSManInstance -ResourceURI "winrm/config/listener?Address=*+Transport=HTTP"

3. Execute the command. Windows will look up the exact item matching your keys without triggering the enumeration restriction.

Method 3: Restart the WinRM Service (If Using Automated Tools)

If this error is thrown by a third-party management tool, orchestration software, or an automated deployment script where you cannot change the code, restarting the local WinRM service can clear corrupted session states.

1. Open PowerShell as an Administrator (Right-click PowerShell -> Run as Administrator).
2. Type the following command to restart the service:

   Restart-Service WinRM -Force

3. Verify the service status is running:

   Get-Service WinRM

   ---

To help pinpoint the exact syntax adjustment, could you provide the specific PowerShell command or software tool that generated this error? Please also mention if you are attempting to list all items or target a single configuration entry.