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
Totally - but so far all of us seem stonewalled.
Same problem here. 1.0.34 no disk issues evident via UEFI.
Ccan see the eMMC when looking for drivers via recovery media).
Reinstall does nothing.
No bootable device.
GBP200+ for an out of warranty exchange when it's been bricked by an update isn't the answer.
Tried to call MS support but ultimately led down a telephonic be support path to download and run a diagnostic tool on a device that won't before the clal then terminates without speaking to a human.
Sort it out please Microsoft.
(I am the "friend") By the way, the initial uefi version of the motherboard-changed device is not 1.0.34. I spent a whole afternoon ungrading the system from 1903 (even in S mode) to 20H2 and now the uefi version is 1.0.34. I have used it for about 2 days and reboot it serveal times and it can still function well.
I have the exact same issue with my sister's Surface Go, UEFI 1.0.34 and a 64 GB eMMC memory.
I used a Windows 10 pre-install environment to check the eMMC and for the most part I am able to access data on it, but after a while of looking through the files, the drive becomes sluggish and unresponsive. My initial thought was that the memory was failing, but after viewing this thread it seems the update is the main issue.
I just hope Microsoft is able to sort this out soon and not force us to buy new devices......