Following Error occured 2 day's ago on several SurfaceHub Gen1 in our company:SurfaceHub error: secure boot violation invalid signature detected. Check secure boot policy in setup.Solution could be to disable Secure Boot and other UEFI details.But following process to enter UEFI / Bios is not working at all: Shut down the Surface Hub completely.Press and hold the volume up button on the side of the device.While holding the volume up button, press and release the power button.Continue holding the volume up button until the Surface logo appears.The device should now boot into the UEFI (BIOS) settings menu.We did test with several different SurfaceHub devices and all kind of pressing and holding these buttons, even with external cabled Keyboard. Not able to enter UEFI.Does anybody have same issue?Know in detail how to enter UEFI at Surface Hub Generation 1.thx for any hints Bruno

Hi Bruno, I have (7) Surface Hub v1's with this error as of now.Possibly another (15) that have not been reported yet but show as offline as of today and have 10.0.19045.5965 as the current version (listed in Intune/TAC). I only briefly tried to troubleshoot one yesterday when I though it was an isolated HW issue. The Admin guide for v1's used to say use the power switch on the back/bottom turning it off/on 3 times to enter setup. I haven't been able to try it today.

We’re currently seeing these issues at customer sites with several Surface Hub version 1 devices (the original black models) showing the following boot error:**“SECURE BOOT VIOLATION – INVALID SIGNATURE DETECTED. CHECK SECURE BOOT POLICY IN SETUP.” **This appears to have started likely following this week's Windows update and subsequent reboot.We’ve opened a support case with Microsoft and are awaiting further guidance. If anyone else is seeing similar behavior or has found a workaround, we’d appreciate any insights.

i have tried this and this does not work either

This is what Microsoft gave to us.For the Serial Issue:I was told you can press the backspace button and then you can enter the s/n. (Not tested)I had to get the BitLocker (Recovery) keys from Active Directory. Once you enter in the recovery key, the unit will work until it is rebooted.It will go back into an errored state anytime the unit reboots but simply press the ESC on your external keyboard and it will boot back up without the recovery key.edit I was just told the reason this happens is because were did not enter in the serial number but rather pressed ESC to enter the recovery key. Be sure to enter the Serial Number.We have not identified a fix for the boot error. We currently have over 300 units effected.Surface Hub v1 Boot Issue After June 2025 Windows Update (KB5060533)[Last Updated: June 12, 2025]We are currently investigating a known issue impacting Surface Hub v1 devices following the June 2025 “6B” Windows Update (KB5060533). After installing this update, some Surface Hub v1 units may no longer boot into Windows and display one of two error messages.Affected Devices:Only Surface Hub v1 is affected.Surface Hub 2S and Surface Hub 3 are not impacted.What You Might See🔴 Secure Boot Violation (Red Screen) You may encounter the following error message on boot:Secure Boot ViolationInvalid signature detected. Check Secure Boot Policy in SetupThis is the primary error blocking startup of affected devices. It is caused by a Secure Boot DBX update included in the June “6B” cumulative update. The Surface and Windows engineering teams have identified this as a conflict between the update and the AMI BIOS used in Hub v1 devices. A fix is actively being developed.🔵 Invalid Serial Number (Blue Screen) Some customers may also see this message:Invalid Serial NumberNew Serial Number: [System Serial]This is a separate issue and not directly related to Secure Boot, but may appear if the BIOS has been fully reset to defaults. In this case, you can re-enter the correct serial number for your device and it will proceed to boot to Bitlocker recovery. If the Bitlocker key is not available, SHRT can be used to re-image the device at that point.To locate your Surface Hub v1 serial number, refer to the label underneath the power and volume control panel, as shown below: What Microsoft Is DoingAs of June 11, 2025, Microsoft has blocked the 6B update from installing on additional Surface Hub v1 devices.Engineering teams are developing a 6B update to prevent future DBX updates from being applied to Hub v1, while still allowing all other security patches through the end of Windows 10 support in October 2025.We are investigating recovery options for devices already affected and will share validated recovery instructions as soon as they are available. What You Can Do NowIf your device is displaying the red Secure Boot error, please retain the device in its current state. We will share step-by-step recovery instructions once a fix is confirmed.If you see the blue Invalid Serial Number screen, manually re-enter the serial number found on the label near the control buttons.Stay connected with your Microsoft representative for direct updates and we will also soon be releasing a Surface IT Pro Blog post around this issue. We understand how critical Surface Hub is to your organization, and we are working urgently across engineering teams to resolve this issue. We appreciate your patience and partnership.If you have questions or need to report affected devices, please reach out to your Microsoft support contact.

The repair was only possible together with MS support. Need was to create a manufacturing.bin send to MS and then receive a signed manufacturing-SIGNED.bin file. With this signed file unlock was possible and with a then follwo bios update all is running fine again. Please get in contact with MS about.

SurfaceHub Gen1 violation error at several devices

32 Replies

Christoph
Copper Contributor
Jun 16, 2025
Good morning everyone!
We're facing the same issue at our company. About one-third of all our Surface Hubs are affected, and I'm too scared to reboot the rest.
We opened a case with Microsoft on June 13th, and since then, crickets. Attempts to escalate with the local Microsoft office and our Key Account Team were shot down, and we were pointed to the Unified contract. Lovely.
I've seen some guides on Reddit, but unfortunately, they didn't help either. My next step will probably be trying the Recovery Tool. It can't do worse than not working, right? 😉
Cheers,
Christoph
BrunoK1874
Brass Contributor
Jun 15, 2025
This is now a known issue at MS: SurfaceHub Gen1 violation error at several devices | Microsoft Community Hub Unfortunately MS tells in our SEV A ticket after 5 days still:
Current Status form MS:
Following the investigation, Microsoft identified this as a known issue affecting Surface Hub v1 devices after the installation of the June 2025 Windows security update. The Microsoft Product Group (PG) is actively developing a set of manual recovery instructions, and further updates will be provided accordingly. In the meantime, the Microsoft engineer advised to leave the device untouched if the 'Secure Boot' error is displayed. However, if the device shows a blue 'Invalid Serial Number' screen, it is recommended to manually re-enter the serial number located near the control buttons.

> In our situation, some devices install this update and now showing "invalid Serie number.
But we cannot enter this serie number. No keyboard, not original wireless, neither cable USB keyboard is able. These keyboards can enter "Esc" to jump over this message, then we have to enter Bit-Locker Key and MS SurfaceHub is working fine. But after restart this serie number enter request comes again.
In addition we are also not able to enter UEFI / Bios anymore.
Question:
Does anybody can access UEFI / Bios in these situation? How?
tmano
Copper Contributor
Jun 14, 2025
We have contacted Microsoft Support and have been informed that only the Surface Hub v1 is affected by the June update.
Microsoft is currently investigating how to recover and will release a Microsoft Learn article on this issue soon.
flamurK
Copper Contributor
Jun 13, 2025
Hi Bruno, we are having this same issue with all of our sites globally and when wanting to speak to a tech at microsoft i was told they are only on a call back basis.

have you had any updates regarding this issue?
PontSBL
Copper Contributor
Jun 13, 2025

We’re currently seeing these issues at customer sites with several Surface Hub version 1 devices (the original black models) showing the following boot error:
**“SECURE BOOT VIOLATION – INVALID SIGNATURE DETECTED. CHECK SECURE BOOT POLICY IN SETUP.” **
This appears to have started likely following this week's Windows update and subsequent reboot.
We’ve opened a support case with Microsoft and are awaiting further guidance. If anyone else is seeing similar behavior or has found a workaround, we’d appreciate any insights.
IsGarLan
Copper Contributor
Jun 13, 2025
Hi Bruno, I have the same problem, please let me know if you find a solution. Thanks!

https://www.reddit.com/r/SurfaceHub/comments/1l99dq9/comment/mxesq6e/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
IsGarLan
Copper Contributor
Jun 13, 2025
I have the same problem. Please let me know if you find a solution. Thanks!
nshrestha
Copper Contributor
Jun 13, 2025
Same issue. Tried all possible ways, but cannot boot to BIOS mode. Also, I cannot download the image from the Microsoft website by appliying serial number.

Thanks
Nikhil
JeremyKC
Copper Contributor
Jun 12, 2025
Hi Bruno,
I have (7) Surface Hub v1's with this error as of now.
Possibly another (15) that have not been reported yet but show as offline as of today and have 10.0.19045.5965 as the current version (listed in Intune/TAC).
I only briefly tried to troubleshoot one yesterday when I though it was an isolated HW issue.
The Admin guide for v1's used to say use the power switch on the back/bottom turning it off/on 3 times to enter setup.
I haven't been able to try it today.
- flamurK
  Copper Contributor
  Jun 13, 2025
  i have tried this and this does not work either

Forum Discussion

SurfaceHub Gen1 violation error at several devices

32 Replies

Resources