Windows Error Fix: WinRM cannot complete the operation

Error Description

The "WinRM cannot complete the operation" error typically occurs when the Windows Remote Management (WinRM) service is unable to process a request. This happens due to misconfigured WinRM settings, a stopped WinRM service, strict Windows Firewall rules, or issues with network location profiles (such as a public network blocking remote management). It prevents administrators from managing the system remotely via PowerShell or other management tools.

Step-by-Step Fixes

Step 1: Start and Configure the WinRM Service

The WinRM service must be running and set to start automatically for remote management to function.

1. Press Windows Key + R to open the Run dialog box.
2. Type services.msc and press Enter.
3. Scroll down and locate the Windows Remote Management (WS-Management) service.
4. Right-click the service and select Properties.
5. Change the Startup type to Automatic.
6. If the service status is stopped, click the Start button.
7. Click Apply and then OK to save the changes.

Step 2: Run the Quick Config Command

Windows includes a built-in tool to automatically configure WinRM with standard settings and open the required firewall ports.

1. Right-click the Start menu icon and select Terminal (Admin) or Command Prompt (Admin).
2. Type the following command and press Enter:

   winrm quickconfig

3. If prompted to make changes and enable the service, type y (Yes) and press Enter.
4. If prompted to create a WinRM listener, type y and press Enter again.

Step 3: Change Network Profile from Public to Private

WinRM often fails on networks classified as "Public" because Windows security policies block remote administration on untrusted networks by default.

1. Right-click the Wi-Fi or Ethernet icon in your system tray (bottom right corner) and select Network and Internet settings.
2. Click on Properties for your active network connection.
3. Change the network profile type from Public network to Private network.
4. Open PowerShell as an Administrator and try running winrm quickconfig again to see if it succeeds.

Step 4: Configure LocalAccountTokenFilterPolicy

If you are trying to connect using local administrator credentials on a workgroup computer, User Account Control (UAC) might block the connection. Creating a specific registry key bypasses this restriction.

1. Press Windows Key + R, type regedit, and press Enter to open the Registry Editor.
2. Navigate to the following path: HKEY LOCAL MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Right-click an empty space in the right pane, hover over New, and select DWORD (32-bit) Value.
4. Name the new value exactly:

   LocalAccountTokenFilterPolicy

5. Double-click LocalAccountTokenFilterPolicy, change its Value data to 1, and click OK.
6. Restart your computer for the changes to take effect.

Step 5: Add Target Hosts to the TrustedHosts List

If you are connecting to a remote machine outside of an Active Directory domain environment, your client machine needs to explicitly trust the remote host.

1. Open PowerShell as an Administrator.
2. To trust all remote computers (common for testing environments), type the following command and press Enter:

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

3. If you only want to trust a specific computer, replace the asterisk with the IP address or hostname of that computer:

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

4. Restart the WinRM service to apply the change:

   Restart-Service WinRM