Forum Widgets
Latest Discussions
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
Surface Hub S2 does not start recovery mode - what to do?
Hi everyone! We have our Surface Hub S2 in our meeting room, but after a power outage, the Hub won't boot anymore. It only comes up with the white Windows Logo and black background in an infinite loop. So, I just accepted, that I have to factory reset the device. But I am not able to boot from any USB stick. I can enter the UEFI Setup and i can update the configuration via USB stick. But when I try to start via "volume down" and power button, no recovery mode is entered. I tried all 3 USB-C slots and the USB A slot, made bootup sticks with the windows recovery tool and also with the surface IT toolkit. None worked. Am I doing something wrong? Is there another way to enter the recovery mode or alter the booting? Thanks, TimHow to use Surface hub with multiple displays
We just recently installed a Surface Hub in the office to use for scrum meeting etc. We have, right next to it, a regular screen (previously used to connect laptop to). What we would like to do is to use the Surface to call into Skype for Business meetings, and get the video shown on the normal screen, and the collaboration area (with whiteboard etc.) on the Surface display. The purpose is to get the video image larger than the normal little box to the left at the same time as maximizing the collaboration area. How can we get this setup?
Surface Hub 3 doesn’t rotate on Windows 11 Pro
Hi, I’ve got a 50” Surface Hub 3 that we’ve switched over to Windows 11 Pro. The thing is, we’re trying to get the screen to rotate — but it just won’t. We’ve noticed that it does work when running in Microsoft Teams Room mode, and also in the Windows 11 IoT admin mode. So what’s going on? Why won’t the Surface Hub 3 rotate when it’s running just Windows 11 Pro or Windows 11 IoT without Teams Room? Is there something we need to enable in the system? We even see the rotation icon in the taskbar, but clicking it doesn’t seem to do anything. Thanks!
Please restore HDMI screen share via Share button and Miracast screen sharing after migration to MTR
The changes you have made make no sense whatsoever and are not end-user friendly. In our company, all MTR-based rooms have an HDMI cable available for screen sharing and I find it hard to understand why you have stripped these two functionalities from Surface Hubs after the migration (especially as Miracast worked brilliantly on SH2S!).
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.Surface Provisioning package
I need some assistance with MDM enrolment for provisioning packages. I can't find what credentials I should be using for building devices and thus after assistance please. When this option for Enrol in mdm is off, some devices have gone into Intune and some haven't. I can't think or see why this is happening. They go into Entra but not Intune. I thought this was a build issue with the devices but i've tried various i.e. upgrading from a Windows 10 teams room to Teams Rooms for Windows 11, and a build media of the New Teams rooms for Windows 11 but still the same issue. I understand i need to complete this Enrol in MDM, so I need some assistance as to what credentials i should be using please. Apologies, if this is a duplicate, for some reason i was certain i had published this yesterday but i can't see this post.Provisioning does not add to MDM - Surface hub
When using the Windows Configuration Designer to create a provisioning package I'm unsure what to add for the MDM devices. Some devices seem to enter the MDM and some don't. Unsure if it's the build on these devices. I've looked for documentation and can't find any for what credentials to use for the following on the Enrol in device management I need to know what to enter for the following fields please. So that I can insure these devices populate into Intune. I don't know why MS make it so hard for this as the setup of the older 2s devices was much easier. Thanks Michael
