Surface Go uefi version is 1.0.34 and No Bootable Device error

Anonymous
2022-05-27T23:37:40+00:00

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.

Surface | Surface Go | Install and update

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.

0 comments

362 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-06-22T18:45:07+00:00

    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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-06-22T02:28:35+00:00

    (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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-06-22T02:09:15+00:00

    Hi Tom, thanks for your all efforts that trying to make things done. In the community of my zone, there is a friend got the same problem and took the device back to MS support with warranty to fix up. After that, the motherboard on the device is replaced and it works on firmware 1.0.34 and the warranty has been delayed from June to September.

    I have no idea if this firmware update is aiming to force users to change their device, but I still hope that they will push another fix update or something to repair it.

    In conclusion, for you all, if you have the warranty in time, just go and fix it for free, is your power. If not, we should push this hard to MS to make the device back to live.

    ps：I have tried to install ubuntu and got the same answer as well. It must be some basic firmware file gets bugs on it.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-06-22T01:40:16+00:00

    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......

    Was this answer helpful?

    0 comments