Error Description

This error occurs because the Windows Remote Management (WinRM) service restricts security configurations on network adapters classified as Public. By default, Windows blocks WinRM remote management traffic on Public networks to protect your system from external threats. To enable WinRM, all active network connections must be changed to Private or Domain.

Step-by-Step Solutions

Here are the three easiest ways to fix this issue. You only need to use one of these methods.

Method 1: Change Network Profile to Private via Windows Settings (Easiest)

1. Open the Start Menu and click the Settings gear icon (or press Windows Key + I).
2. Click on Network & Internet.
3. Select your current connection type from the left sidebar:
   • Choose Wi-Fi if you are on a wireless network.
   • Choose Ethernet if you are using a wired cable.
4. Click on the name of your active network connection.
5. Under Network profile, change the selection from Public to Private.
6. Open your command tool and run your WinRM command again.

Method 2: Change Network Profile via PowerShell (Fastest)

1. Right-click the Start Menu button.
2. Select Windows PowerShell (Admin) or Terminal (Admin).
3. Type the following command to view your active networks and press Enter:

   Get-NetConnectionProfile

4. Look at the output and find the InterfaceIndex number for the network set to Public.
5. Type the following command (replace NUMBER with your actual InterfaceIndex digit) and press Enter:

   Set-NetConnectionProfile -InterfaceIndex NUMBER -NetworkCategory Private

6. Verify the change by running Get-NetConnectionProfile again.

Method 3: Skip the Public Network Check (Advanced)

If you must keep your network profile set to Public but still need WinRM enabled, you can force WinRM to accept Public interfaces.

1. Right-click the Start Menu button.
2. Select Windows PowerShell (Admin) or Terminal (Admin).
3. Type the following command and press Enter:

   Enable-PSRemoting -SkipNetworkProfileCheck -Force

4. Alternatively, if you are configuring a specific quick-config command, run:

   winrm quickconfig -skipNetworkProfileCheck

Verification

After applying any of the methods above, verify that the service is running correctly by executing this command in an administrator command prompt:

Test-WSMan

If it returns identification details about the WinRM service, the error is successfully resolved.