Share via

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

Rahuleo 110 Reputation points
2026-06-10T03:45:33.37+00:00

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:

  1. Selecting the Surface Hub from the cast menu (Windows + K)
  2. Prompts to enter the PIN
  3. 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"
  4. Clicked on "Allow Once"
  5. Then a Screen cast window appeared displaying the PIN
  6. 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.

Surface | Other
0 comments No comments

Answer accepted by question author

Alex-L 7,705 Reputation points Microsoft External Staff Moderator
2026-06-10T09:10:24.8666667+00:00

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.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.