Miracast connectivity issue on Windows 11 Build 26200

Question

I'm looking for assistance with what appears to be a Miracast issue affecting Windows 11 Build 26200.

I have tested this on two separate Windows 11 devices:

• Dell Pro 14 (Intel Wi-Fi 6E AX211)
• Alienware Aurora 16 (MediaTek Wi-Fi 7 MT7925)

Both devices are running Windows 11 Build 26200 and exhibit the same behaviour.

When pressing Win + K, both my Microsoft Wireless Display Adapter (latest firmware) and Samsung 55" QLED TV are discovered without issue. However, when attempting to connect, Windows displays "Connecting..." for several seconds before reporting "Couldn't connect."

I have already completed the following troubleshooting:

• Reinstalled the Wi-Fi and graphics drivers.
• Updated the BIOS.
• Confirmed the Microsoft Wireless Display Adapter firmware is up to date.
• Verified netsh wlan show drivers reports Wireless Display Supported: Yes.
• Verified dxdiag reports Miracast: Available, with HDCP.
• Verified Wi-Fi Direct and Miracast capabilities using netsh wlan show wirelesscapabilities.

The issue occurs with two different Miracast receivers and on two different PCs with different wireless chipsets, which leads me to believe this may be related to Windows rather than a hardware or driver issue.

Event Viewer records the following during each failed connection attempt:

WLAN AutoConfig: The driver disconnected while associating with the temporary ScreenCast-... Wi-Fi Direct profile.

Could you please advise whether this is a known issue with Windows 11 Build 26200 or whether there are any additional diagnostics or hotfixes available? If required, I'm happy to provide Event Viewer logs, DxDiag output, ETL traces, or any other information that would assist your investigation.

I look forward to your guidance.I'm looking for assistance with what appears to be a Miracast issue affecting Windows 11 Build 26200.

I have tested this on two separate Windows 11 devices:

• Dell Pro 14 (Intel Wi-Fi 6E AX211)
• Alienware Aurora 16 (MediaTek Wi-Fi 7 MT7925)

Both devices are running Windows 11 Build 26200 and exhibit the same behaviour.

When pressing Win + K, both my Microsoft Wireless Display Adapter (latest firmware) and Samsung 55" QLED TV are discovered without issue. However, when attempting to connect, Windows displays "Connecting..." for several seconds before reporting "Couldn't connect."

I have already completed the following troubleshooting:

• Reinstalled the Wi-Fi and graphics drivers.
• Updated the BIOS.
• Confirmed the Microsoft Wireless Display Adapter firmware is up to date.
• Verified netsh wlan show drivers reports Wireless Display Supported: Yes.
• Verified dxdiag reports Miracast: Available, with HDCP.
• Verified Wi-Fi Direct and Miracast capabilities using netsh wlan show wirelesscapabilities.

The issue occurs with two different Miracast receivers and on two different PCs with different wireless chipsets, which leads me to believe this may be related to Windows rather than a hardware or driver issue.

Event Viewer records the following during each failed connection attempt:

WLAN AutoConfig: The driver disconnected while associating with the temporary ScreenCast-... Wi-Fi Direct profile.

Could you please advise whether this is a known issue with Windows 11 Build 26200 or whether there are any additional diagnostics or hotfixes available? If required, I'm happy to provide Event Viewer logs, DxDiag output, ETL traces, or any other information that would assist your investigation.

I look forward to your guidance.

Answer 1

Hello,

This is indeed a regression in Windows 11 Build 26200. Miracast discovery works, but the connection fails with “Couldn’t connect,” and Event Viewer shows WLAN AutoConfig disconnecting from the temporary Wi-Fi Direct profile. Since you tested across Intel AX211 and MediaTek MT7925 chipsets, and with both a Microsoft Wireless Display Adapter and Samsung QLED TV, hardware and drivers can be ruled out. The issue is tied to the OS build itself. Before concluding, confirm that the Wireless Display optional feature is installed via Settings > Apps > Optional Features, and that your graphics driver reports WDDM 3.1 or newer in dxdiag. If those are already in place, then the failure is due to the networking stack regression introduced in Build 26200. Microsoft has not yet released a hotfix, and the only reliable workaround is rolling back to Build 26100 or earlier if Miracast is critical. Submitting ETL traces and logs through Feedback Hub under “Devices and Drivers > Wireless Display and Miracast” will help Microsoft prioritize the fix. For now, HDMI or DisplayPort connections are the only stable alternatives until the next Insider build resolves this.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Hoang Le.