How to Fix Windows Error: "The WinRM client cannot process the request"

The Windows Remote Management (WinRM) error usually occurs when the system cannot establish a secure connection between the local computer and the remote host. This guide explains why this happens and provides clear, step-by-step solutions to resolve the issue.

Error Overview and Common Causes

This error code typically surfaces when using PowerShell remoting, managing Hyper-V servers, or running administrative scripts. The most common reasons behind this message include:

• Disabled WinRM Service: The service is not running on either the local or remote machine.
• Authentication Issues: Windows is blocking the connection because the remote host is not trusted.
• Network Location Profile: The network profile is set to "Public," which automatically blocks WinRM traffic.
• Firewall Blockage: Windows Firewall or third-party security software is obstructing port 5985 (HTTP) or port 5986 (HTTPS).
• Incorrect Execution Policy: PowerShell restrictions prevent remote script execution.

Step-by-Step Fixes

Follow these solutions in order. You must run PowerShell or Command Prompt as an Administrator to execute these commands.

Fix 1: Enable and Start the WinRM Service

The absolute first step is ensuring that the WinRM service is properly running and configured to start automatically on both computers.

1. Press the Windows Key, type powershell, right-click Windows PowerShell, and select Run as administrator.
2. Type the following command to configure the WinRM service and press Enter:

   winrm quickconfig

3. If prompted to confirm changes (such as creating exceptions in the firewall or changing the service startup type), type y (Yes) and press Enter.
4. Next, force-start the WinRM service manually to ensure it is active:

   Start-Service WinRM

5. Set the service startup type to Automatic so it runs whenever Windows boots:

   Set-Service WinRM -StartupType Automatic

Fix 2: Add the Remote Host to the TrustedHosts List

Windows security rules block remote connections unless the target machine is explicitly trusted. You must configure the TrustedHosts settings on your client computer.

1. Open Windows PowerShell as an Administrator.
2. To allow connections to any computer (best for testing or internal private networks), type this command and press Enter:

   Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*" -Force

3. If you prefer to trust only one specific computer for better security, replace the asterisk with the remote IP address or hostname:

   Set-Item WSMan:\localhost\Client\TrustedHosts -Value "192.168.1.50" -Force

4. Restart the WinRM service to apply the new configuration:

   Restart-Service WinRM

Fix 3: Change the Network Profile to Private

WinRM will refuse connections if your active network connection is categorized as "Public" because Windows locks down security in public locations.

1. Open Windows PowerShell as an Administrator.
2. Check your current network status by running:

   Get-NetConnectionProfile

3. Look at the NetworkCategory value. If it says Public, copy the name shown next to Name.
4. Change the network profile to Private by running the following command (replace YourNetworkName with your actual network name):

   Set-NetConnectionProfile -Name "YourNetworkName" -NetworkCategory Private

Fix 4: Allow WinRM Ports Through the Windows Firewall

Even if the service is running, the local firewall might actively drop incoming or outgoing management requests.

1. Open Windows PowerShell as an Administrator.
2. Run this command to create a new firewall rule that allows WinRM HTTP traffic (Port 5985):

   New-NetFirewallRule -DisplayName "Allow WinRM HTTP" -Direction Inbound -LocalPort 5985 -Protocol TCP -Action Allow

3. If your environment uses HTTPS connections, open Port 5986 as well:

   New-NetFirewallRule -DisplayName "Allow WinRM HTTPS" -Direction Inbound -LocalPort 5986 -Protocol TCP -Action Allow

Fix 5: Adjust PowerShell Execution Policy

An overly restrictive execution policy can prevent Windows from processing the scripts required to initialize a remote session.

1. Open Windows PowerShell as an Administrator.
2. Check your current execution policy setting:

   Get-ExecutionPolicy

3. If the policy is set to Restricted, change it to RemoteSigned or Bypass to allow local management actions:

   Set-ExecutionPolicy RemoteSigned -Force

Verifying the Solution

Once you complete the steps above, you can verify that the WinRM client can process requests properly. Run the following command in PowerShell to test a local loopback connection:

Test-WSMan

If successful, the command will display information about the WS-Management service version and the stack version, meaning your WinRM client is fully functional again.