Miracast blocked through Microsoft Security Baseline

Question

_{Monday, October 22, 2018 3:04 AM}

Hi,

more or less we just imported Microsoft's security basline template for Windows 10.

Unfortunately after doing so Miracast stopps working.

Could you please help me to point out the settings I need to change to get it running again?

Many thanks in advance

Ruben

All replies (4)

_{Monday, October 22, 2018 6:50 AM}

I had the same problem when testing a Surface Hub and found that Microsoft Windows 10 Security Baseline is blocking Miracast when the laptop is using the Public Windows Firewall because the baseline doesn’t allow the local firewall rules to be merged with the rules from the GPO.

If possible, switch to the Private Firewall profile or create a new GPO to change this parameter.

After some tests, I also found that adding these rules in the Public firewall allow Miracast through the Public Firewall:

Inbound rule 1: "Surface Hub Miracast - TCP" : local ports 7236, 7250, 50000; Profile: Public; Program and service: %SystemRoot%\System32\WUDFHost.exe

Inbound rule 2: "Surface Hub Miracast - UDP" : local ports 5353; Profile: Public; Program and service: %SystemRoot%\System32\WUDFHost.exe

Gérald

_{Tuesday, October 23, 2018 1:23 AM}

Thank you very much Gérald!

I will test it and come back to you asap :-)

_{Tuesday, October 23, 2018 8:24 AM}

After adding those rules the situation improved. Windows 10 is now showing devices and also it states "connecting". But after a long while nothing futher happens.

Do you have other suggestions?

_{Sunday, March 24, 2019 10:37 PM}

We solved this by following the recommendation on the Miracast Trouble Shooting page (https://docs.microsoft.com/en-us/surface-hub/miracast-troubleshooting#check-firewall) to create a firewall rule for C:\Windows\System32\WUDFHost.exe.  We had to allow all ports, not just the specific ports listed by Gerald (thanks for getting us on the right track!).