Miracast on the new 5.6.135 Teams agent update does not work as intended

Question

Miracast on the new 5.6.135 Teams agent update does not work as intended

Rahuleo 130

With the re-appearance of Miracast back to Surface Hubs, it is currently not working as intended. With Surface Hub 2S Miracast has been enabled with the option to ask for PIN every time. The hub also displays the Miracast option (Windows + K) on the homescreen and also in the cast menu.

However, The PIN is not displayed on the Hub on the MTR experience, when using a surface laptop and selecting the Hub from the cast menu to enter the PIN.

I logged in to the Windows OS and tried the same method:

Selecting the Surface Hub from the cast menu (Windows + K)
Prompts to enter the PIN
The Hub displayed a notification that a device is trying to connect and the drop-down menu had options: Always allow, "Allow once", "Don't allow"
Clicked on "Allow Once"
Then a Screen cast window appeared displaying the PIN
Once entered, the surface laptop screen was displayed as a Windowed screen

With the update, the expected should have been the same process to connect, surface hub displaying a PIN of the MTR experience and casting the screen instead of having to log into the Windows OS which only admins would log in to troubleshoot/investigate issues.

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Alex-L 13,280 Microsoft External Staff Moderator

Hi Rahuleo

Thanks for the detailed write‑up, based on your testing, this looks like a behavior difference between the Windows OS projection flow and the Teams Rooms (MTR) experience.

Miracast itself is working correctly (since the PIN and connection flow function as expected in the Windows session), but in the MTR interface the PIN/approval UI is not surfaced, so the “Ask for PIN every time” scenario cannot complete.

For now, workarounds would be to allow casting without PIN or approve the request from the Windows admin session. I’d also recommend submitting feedback or opening a support request so the product team can review this behavior (note: as this is a public forum, we don’t have visibility into backend logs or the ability to escalate cases directly):

On the device: More (…) > Settings > Report a problem
Admin side: Microsoft 365 admin center > Support > New service request
Windows feedback: Feedback Hub > Devices > Projection/Connect

This helps ensure the issue is properly reviewed by the Teams Rooms / Surface Hub engineering team.

0 comments

1 additional answer

Answer 1

Hi,

We experienced the same Miracast issue on our Surface Hub 2S devices running Teams Rooms on Windows.

Miracast worked when logged in as a Windows administrator, but the PIN was not displayed in the Teams Rooms (Skype) interface.

We managed to resolve the issue through the Teams Rooms Pro Management Portal:

Navigate to Rooms → Select the device → Settings → Device → Miracast.

Enable Miracast and configure the PIN requirement (if it's already enabled, disable first and restart)
Apply the settings and wait until the device settings job shows Completed.
Restart the Surface Hub and test Miracast again in the Teams Rooms interface. If it's correct it will show a Miracast Symbol with Win+K on the top left.

Important: If the Miracast setting disappears from the portal after changing it, completely close and reopen the portal. The option should become visible again after a while.

We also encountered a "Settings fetch failed" error. Using Re-apply on the failed activity successfully pushed the configuration.

After applying the settings, Miracast worked correctly on our device.

This allows us to keep PIN authentication enabled instead of disabling it as suggested in the accepted answer.

Hope this helps others experiencing the same issue!