Forum Widgets
Latest Discussions
Miracast not working on Surface Hub 3 (Windows 11 IoT mode)
Hi everyone, we’re currently experiencing issues with Miracast on our Surface Hub 3 devices when running in Windows 11 (IoT) mode. As far as we recall, Miracast used to work correctly in Windows 11 mode without any issues. We are also aware of the planned rollout for this functionality in MTR mode around May 2026. However, since this was already working for us in W11 mode, we’re wondering if something has recently changed that could have impacted this behavior. So far, we’ve tried all the usual troubleshooting steps, including: - Device reboots - Policy/configuration checks and changes - Full device reinstallation Unfortunately, none of these actions resolved the issue. Has anyone experienced something similar or is aware of recent changes that might explain this? Thanks in advance, AndreaDual Boot on Surface Hub 3
Has anyone else shrunk the Surface Hub partition to support dual boot between MTR and Windows 11? I know it’s a niche case, but since the Surface Hub 3 has plenty of resources (memory & disk) to do more than just a meeting room, it might be interesting to explore! I created a video demonstrating setting it up in this way for testing. https://www.linkedin.com/posts/stilldrey_how-to-microsoft-surface-hub-3-dual-boot-ugcPost-7427475939858554880-l6pq?utm_source=share&utm_medium=member_ios&rcm=ACoAAADpC5gBtRjG2ffA5dQj2Vy6zWx7DvhK55A #SurfaceMVP LinkedIn video - dual boot Surface Hub 3
Miracast by end of 2025?
It is now 2026. MS said early last year that Miracast was coming to SurfaceHubs by the end of 2025 and I haven't seen an update since. Has anyone seen something maybe I haven't? Why aren't there more posts about this exact topic? It seems like this should be core functionality...
Surface Hub 2s with MTR-W no Miracast support!
We have 3 Surface Hubs 2S, which are recently have been updated to MTR-W (W11) (What a bummer...) What we desperately need is Miracast support! We've tried to set this up with the admin account, and once you are in admin mode you are able to configure 'Projecting to this PC' but back in normal mode, you can't use Miracast (Windows-K) anymore. I've read Miracast will become available for Surface Hub 3 but there are no plans to support the Surface Hub 2s. Anyone out there who is/was facing the same problem? Did you manage to solve this? If so, how did you solve this? Thank you, Gerrit
Wifi issues - need to configure wifi for Machine based authentication
All our devices now do not connect to the government available wifi called GovWifi. This is due to the fact the way the devices sign in using Windows 11 with the Skype account having no security assigned to it as it auto signs in. Is there a way to create an xml script or setting to allow this wifi to be set as machine based authentication please. These Windows 11 MTR builds have been very troublesome and we've experienced issue after issue since implementing these builds, so suggestions would be welcomed. Thanks MichaelPresenter Remote Controllers Issue
Since migration to Win11 - The hub remotes have lost functionality. Previously they could be used to move slideshows in PowerPoint along, now all the remote can be used for is volume up or down. Will this feature be restored? Is it linked to the fact you cannot move the slides along on the surface hub screen now either, which again is frustrating.Surface hub on screen KB predictive text
I've noticed some of my surface hubs in my organisation now have the predictive text feature on the onscreen keyboard. I've followed the settings for this; Press the Windows + I keyboard shortcut to open the Settings app. Click on the Time & language tab. Navigate to the Typing section. Click on the toggle button next to the Show text suggestions when typing on the physical keyboard option. However they do not work. Why has this been rolled out to Surface hub MTR devices? The only way I can work on these devices with this feature is using a physical KB. Has anyone seen this and found a resolution please? Again no idea why there's no testing on the roll out of features for these devices. Although I've seen Edge can be added via the Teams admin portal but other apps like Maps are still not available. yours faithfully Michael
Poor Audio/Video Quality in Microsoft Surface Hub 3
When Teams meetings are hosted from our large meeting rooms using Surface Hub 3 85 inches devices, internal participants (both in the room or within the building) experience no issues - audio and video are clear and stable. However, when external participants join these meetings (from outside our network), external participants consistently experience: Poor audio quality: Voices intermittently cut in and out, particularly when someone is speaking from a distance away from the Surface Hub. Unstable video: The camera appears to struggle with focus, causing visual disruptions. This issue has been confirmed across multiple external users and locations, indicating it is not isolated to individual end-user setups.Question about Microsoft Support Structure
My Surface Pro 9 needs what I think is an easy firmware repair. Is it possible to avoid shipping it to Microsoft? The part of the firmware that contains the SKU Model Number is corrupt. It shows as "OEMLO Product" instead of Surface Pro 9. That part of the firmware is protected. It can only be accessed by a Microsoft employee using internal tools and physical access to the Surface Pro. Microsoft Device Support offers only a mail-in program, which would mean a lot of work for everyone that's probably not necessary. I don't know much about Microsoft support structure. So I don't know if it's flexible enough for a kind-hearted employee with access to the right tools to fix this. I live near several large Microsoft facilities in the Washington DC area. I think it's a quick easy repair. It could save me and Microsoft Device Support a lot of work that's probably unnecessary. The corruption may have occurred either as a result of participation in the Windows Insider program or during a Surface Pro 9 firmware update in late August 2025. The absence of a valid SKU Model Number prevents Microsoft's driver package from repairing drivers. It also prevents both business and consumer versions of the Surface Diagnostic tool from running. Meanwhile the SMF Core Driver is not loading. I could probably fix that with the correct driver package, but the driver package won't run without the correct SKU number. Otherwise, the Surface works fine. So I can afford to wait until December 2025 to send in for a complete overhaul. That's when I'll be able to lose access to it for an extended time. The rest of the firmware seems to be okay. Other than the SKU model number the information, including the serial number, appears correct.
