Winrm quickconfig can't complete correctly

Question

I am trying to enable wsam on a laptop but always comes back with the following message

winrm quickconfig

WinRM service is already running on this machine. WSManFault Message ProviderFault WSManFault Message = WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Pri ate and try again. Error number: -2144108183 0x80338169 WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

when I check NICs, with

Get-NetConnectionProfile

no one is public

thanks for your help

Answer 1

Hello @Salam ELIAS ,

Yes, you can restrict WinRM access to a specific IP address using Windows Firewall, even though Set-WSManQuickConfig -SkipNetworkProfileCheck configures the listener to accept requests on all local IP addresses by default.

Open PowerShell as Administrator and run the following command, replacing the example IP with the trusted remote computer's IP address:

Set-NetFirewallRule -Name "WINRM-HTTP-In-TCP" -RemoteAddress 192.168.1.50

Then verify the rule to confirm the restriction is applied. Also check for other enabled WinRM firewall rules that might allow broader access.

Note: This restricts which remote computer can connect. If you want WinRM to listen on only one of the laptop's local IP addresses, the listener configuration must also be adjusted.

Microsoft references:

Set-WSManQuickConfig

Set-NetFirewallRule

Best regards

Answer 2

Hello @Salam ELIAS ,

Thank you for sharing the results. Since both reported network profiles are set to Private, let's check whether WinRM is configured correctly before making further changes.

Please open PowerShell as Administrator and run these commands one at a time:

1. Check the WinRM listener:

winrm enumerate winrm/config/listener

2. Check the WinRM firewall rules:

Get-NetFirewallRule -Name "WINRM-HTTP-In-TCP*" |
Select-Object DisplayName, Enabled, Profile, Action

3. Test the local WinRM connection:

Test-WSMan localhost

Please share the outputs and any error messages. This will help us determine whether the issue is with the WinRM listener, firewall configuration, or network profile detection before applying further changes.

Reference: Microsoft Learn – WinRM installation and configuration

Best regards

Answer 3

Hello @Salam ELIAS ,

Based on the output you shared, neither displayed network profile is set to Public. The issue may be caused by another network adapter or a mismatch in the network profile configuration.

Please try the following steps:

1. Open PowerShell as an administrator and run Get-NetConnectionProfile to check all network profiles.

Run Get-NetAdapter -IncludeHidden to identify any additional or virtual network adapters.

Check the WinRM firewall rules to confirm they are enabled for the appropriate network profile.

If the issue persists, share the command outputs so we can investigate further before making any network configuration changes.

For reference, please see Microsoft's documentation:

WinRM installation and configuration

Set-WSManQuickConfig PowerShell reference

I hope this helps to better understand the diagnostic options available and the risks involved.

If this information was helpful, please click Accept Answer.

Thank you for choosing Microsoft Q&A.

Answer 4

Run PowerShell as Administrator and use the WSMan cmdlet that is designed for this case:

Set-WSManQuickConfig -SkipNetworkProfileCheck

Relevant points for this scenario:

1. Set-WSManQuickConfig configures the local computer for remote management.
2. It starts the WinRM service if needed, sets startup to automatic, creates a listener on any IP address, and enables the firewall exception for WinRM traffic.
3. -SkipNetworkProfileCheck is an available parameter for this cmdlet.
4. This cmdlet must be run from an elevated PowerShell session.

If HTTPS is required instead of the default HTTP transport, the cmdlet also supports:

Set-WSManQuickConfig -UseSSL -SkipNetworkProfileCheck

Note: HTTPS requires manual configuration.

---

• Set-WSManQuickConfig
• Installation and configuration for Windows Remote Management