Troubleshooting Windows Error: "WinRM cannot make the configuration change."

Error Description

The Windows Remote Management (WinRM) error "WinRM cannot make the configuration change" typically occurs when you attempt to configure, initialize, or modify WinRM settings (such as running winrm quickconfig or Enable-PSRemoting).

This issue is predominantly caused by active Group Policy Objects (GPO) that enforce specific restrictions on the WinRM service, overriding your local administrative commands. It can also be triggered by a misconfigured or corrupted WinRM listener, corrupted service states, network profiles mistakenly set to "Public" instead of "Private/Domain," or a conflict with the local firewall blocking configuration changes.

Step-by-Step Fixes

Follow these solutions in sequence to resolve the error.

Solution 1: Reset and Revert Restrictive Group Policies

Local configuration changes fail if an Active Directory or local Group Policy is hard-locking the WinRM configuration.

1. Press Windows Key + R to open the Run dialog box.
2. Type gpedit.msc and press Enter to open the Local Group Policy Editor.
3. In the left navigation pane, navigate to the following path:
   • Computer Configuration ? Administrative Templates ? Windows Components ? Windows Remote Management (WinRM) ? WinRM Client
4. Look at the policies listed on the right side. Change any policy marked as Enabled or Disabled to Not Configured.
5. Next, navigate to the service path in the left pane:
   • Computer Configuration ? Administrative Templates ? Windows Components ? Windows Remote Management (WinRM) ? WinRM Service
6. Locate policies such as Allow remote server management through WinRM or Allow Basic authentication. Double-click them and set them to Not Configured.
7. Close the Group Policy Editor.
8. Open Command Prompt as an Administrator and force an immediate policy refresh by running:

   gpupdate /force

Solution 2: Clear and Restore Defective WinRM Listeners

If a previous automated script or installation left a broken listener template on the default ports, WinRM will reject configuration changes.

1. Click the Start Menu, search for Command Prompt, right-click it, and choose Run as administrator.
2. Run the following command to view all active WinRM configurations and find broken listeners:

   winrm enumerate winrm/config/listener

3. Look for any active listener bound to Port=5985 with Transport=HTTP.
4. Delete the conflicted listener manually by typing:

   winrm delete winrm/config/Listener?Address=*+Transport=HTTP

5. Re-run the core restoration command to force a clean slate recovery of the subsystem:

   winrm invoke Restore winrm/Config

6. Attempt to trigger the configuration initialization again:

   winrm quickconfig

Solution 3: Change Your Network Profile Type

WinRM rules purposely reject automated quick-configuration modifications if your computer network interface card is bound to a "Public" connection state due to security defaults.

1. Right-click the Start Menu and select Windows PowerShell (Admin).
2. Check your current active network profiles by running:

   Get-NetConnectionProfile

3. Look at the NetworkCategory field. If it states Public, you must convert it to ensure WinRM permits local configuration changes.
4. Modify the connection profile status to Private by executing the following command (replace "Ethernet" with your specific interface name found from the previous step if it differs):

   Set-NetConnectionProfile -InterfaceAlias "Ethernet" -NetworkCategory Private

5. Try executing the remote configuration setup sequence once more:

   Enable-PSRemoting -Force

Solution 4: Flush WinHTTP Proxy Interferences

A lingering corporate proxy or local routing entry can trap configuration messages intended for the local web services management daemon loopback address.

1. Open Command Prompt with administrative privileges.
2. Wipe out any hidden proxy redirections that are trapping local WS-Management API calls:

   netsh winhttp reset proxy

3. Restart the core service dependencies cleanly from the command line:

   net stop winrm
   net start winrm

4. Verify if your changes apply correctly without generating the error block.