SurfaceHub Gen1 violation error at several devices

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.