How to fix "WinRM cannot make the configuration change."

The core issue stems from Windows isolating its remote management features from untrusted network locations. WinRM requires the active network connection profile to be set to Private or Domain. If any of your active network adapters (including virtual ones created by Docker, Hyper-V, or VPNs) are classified as Public, Windows blocks configuration adjustments as a fundamental security measure to prevent unauthorized remote exposure.

Step-by-Step Easy Fix

Follow these exact steps to resolve the issue by identifying your network status and configuring WinRM successfully.

Step 1: Open PowerShell with Administrative Privileges

1. Press the Windows Key on your keyboard.
2. Type PowerShell into the search bar.
3. Look at the right panel and click Run as administrator.

Step 2: Identify and Change Public Network Profiles to Private

1. Run the following command to check the current profile status of all your connected network adapters:

   Get-NetConnectionProfile

2. Look through the output for any line that says NetworkCategory : Public.
3. Switch all adapters flagged as Public over to Private by executing this command:

   Set-NetConnectionProfile -NetworkCategory Private

4. Verify the change by running Get-NetConnectionProfile once more to ensure all categories show either Private or Domain.

Step 3: Run the WinRM Configuration Tools

1. With your networks secured under a private status, initialize the service using the quick configuration tool:

   winrm quickconfig

2. When prompted to confirm the structural and firewall modifications, type Y and press Enter.
3. Next, comprehensively enforce PowerShell remoting permissions across the operating system by typing:

   Enable-PSRemoting -Force

Step 4: Add Hosts to the Trusted List (Optional)

If your computer belongs to a local workgroup instead of an active corporate domain infrastructure, you must declare what target systems you plan to interact with.

1. Run this command to configure the WinRM client to recognize and interact safely with external hosts:

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

   (Note: The wildcard `allows connections to any remote address. For tighter security parameters, replace` with a comma-separated list of your specific remote server IP addresses).

Step 5: Restart the WinRM System Service

1. Finalize and save your newly implemented settings to the system registry by forcing a clean service recycle:

   Restart-Service -Name WinRM