Thank you for reporting the issue. We have created and published a solution.
For more information, please view Surface Go or Surface Go 2 turns on and shows "No Bootable Device" (microsoft.com)
-Todd
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Recently receiving "No Bootable Device" error on Surface go running UEFI 1.0.34.
I've tried all the recovery disk options without success.
Have also noticed a few reddit threads with similar issues with this version in the last week or so
Anyone else seen this and managed to recover their device?
I have lodged multiple support tickets, confirmed there is no way for a user to roll back this firmware update.
I have also lodged a complaint here: https://www.microsoft.com/en-au/microsoftfeedback
Edit: 11/7 - After 5-6 weeks I've finally been able to send it back and it's been a fee-free replacement. It has been a lot of back and forth and mentioning this thread with so many other instances of it.
Still waiting for someone to lodge this as a firmware issue.....and remove that version of the firmware from Microsoft site.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you for reporting the issue. We have created and published a solution.
For more information, please view Surface Go or Surface Go 2 turns on and shows "No Bootable Device" (microsoft.com)
-Todd
I don't get how they just brush all our comments off like we ALL got a material problem the same day we all installed the FW update. Way to go Microsoft.
Same issue. I installed an windows update , restart getting "No bootable device" .
(Surface Go 1 ,uefi ver 1.0.34)
All support does is want to charge me almost $400 for a new device.
Same issue. Bricked around 2 weeks ago. Got to try recovery last weekend only no luck. Same screenshot ufei with nothing top right. Date very close to last update.
Almost certain this is MS issue