Miracast not working - Windows 11 Enterprise (MDM Intune)

Question

Microsoft 4k Wireless Display adapter Microsoft Wireless Display adapter v2 obviously already tried all other troubleshooting steps.

Cannot connect to either of these adapters with Windows 11 Enterprise
Can connect to both adapters with Windows 10 Enterprise
Can connect to both adapters with Windows 11 Home MDM we use is with Intune.

Endpoint Security baseline is not assigned to all devices.
Bitlocker is enabled on devices. Any help would be appreciated.

Answer 1

Just implemented this: https://www.leonsitblog.com/2020/01/resolving-wifi-display-connection.html This Fix was what resolved the issue. (in my case I had not enabled security baseline yet as my windows 10 devices worked fine but windows 11 devices did not) In case the link above gets removed or the website removes itself. This is the below fix:

Needed to create a Firewall exclusion and configured a new profile in the following manner;

1. Navigate to Devices > Windows
2. Select Configuration Profiles and then Create Profile
3. Enter a suitable name, select Windows 10 and later for the platform and then Endpoint protection for the profile type
4. Navigate to Microsoft Defender Firewall under the Firewall rules heading select Add Populate the settings based on the Wireless Display (TCP-In) Firewall rule

The profile should then be deployed to your devices enabling you to connect to Wi-Fi displays once more.

Answer 2

I had a similar issue on multiple Intune-managed Windows 11 devices.

We already had general inbound casting rules deployed through Intune with the application set to Any.

The TCP rule allowed ports 7250, 7236-7240, 2869, 10243, and 5040.

The UDP rule allowed ports 5353, 1900, 7236-7240, and 3702.

Both rules applied to all firewall profiles and interface types. These rules had worked previously, but Miracast recently stopped connecting. The displays were still visible through Windows + K, and casting worked when Windows Defender Firewall was disabled.

A Windows Filtering Platform trace showed inbound TCP 7236 traffic for C:\Windows\System32\WUDFHost.exe being blocked by the default inbound rule.

I added the following Intune firewall rule:

Name: Miracast WUDFHost TCP 7236 Application: C:\Windows\System32\WUDFHost.exe Direction: Inbound Protocol: TCP Local port: 7236 Profiles: All Interface types: Any Action: Allow

After the rule applied, Miracast worked on four tested computers with Windows Defender Firewall enabled.

It is unclear why the broader rule with the application set to Any stopped working, but explicitly allowing WUDFHost.exe on TCP port 7236 resolved the issue.

Answer 3

I also had to open UDP to get it working. Here my rules:

---

Answer 4

Miracast events are logged to Wlanautoconfig.The event log errors can provide more details on where the connection fails.