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
It should be simple enough for Microsoft to post a method to downgrade the firmware from a USB drive till they fix this. At the very least pull 1.0.34 off the update list as this will bugger many eMMC Surface Go's.
Same problem with my Surface Go. My son also has a Surface Go 1 working without any problems. Both using UEFI 1.0.34. The only diffrence is the hard drive. My Surface Go uses the 64 GB eMMC storage, his Surface Go is equipted with the 128 GB SSD drive. Perhaps thats the problem.
If the above is the case, it looks like there could be a 0 missing off the firmware version that the affected versions have, although this could be the different platform.
Your firmware on v1: 1.0.34.0
On thé affected models: 1.0.34