Remote WMI relies on Windows Firewall settings incorrectly even if a third-party firewall is enabled

Assume that a third-party firewall is installed and registered by using Windows Firewall to take ownership of Firewall policy management. Remote Windows Management Instrumentation (WMI) connections are blocked even though the third-party firewall that owns the policy is configured to allow the connections. 

This issue occurs in the following operating systems:

  • Windows 10 Version 1511
  • Windows 10
  • Windows 8.1
  • Windows Server 2012 R2
  • Windows Embedded 8
  • Windows Server 2012
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 SP1
This issue occurs because the DCOM API doesn't honor the third-party firewall when it queries the firewall settings.
To work around this issue, run the following command at a command prompt to enable WMI traffic:
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
Microsoft is researching this problem and will post more information in this article when the information becomes available.

Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Article ID: 3192130 - Last Review: 10/03/2016 15:16:00 - Revision: 4.0

Windows 10 Version 1511

  • kbqfe kbsurveynew kbexpertiseinter KB3192130