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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-09-14T05:18:37+00:00

    Thanks. I wish I knew about this before I returned the broken device. I even reached out to a few Microsoft partners and they couldn't help.

    Now I make sure docs are backed up to the One Drive.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-09-14T06:30:06+00:00

    Are you able to get the surface to work again? Like rolling back the firmware??

    Microsoft will send you a refurbished one. For me, I don't get it. My device was new?? I would like to keep my device for security reasons. But you can only get a replacement when you send in your bricked surface!!! I even suggested that I will pay some extra money, so that they could send me a new surface go 3. No, they don't give you any other options except send in your device, and we will send you a second hand one????!!!! ****!!!!

    Oh, they do give you another option, since they consider that as an option. Do nothing and pretend nothing had happened!!!!!!

    I think Microsoft has become so big that they could afford to do this. What would they think of next to fxxk up? We are talking about firmware, which cannot be rollback easily if at all!!! I think we should go back to the old days where you cannot actually update the firmware, except physically remove a chip. Maybe then, we will at least be sure that they are not going to fxxk up the firmware!!!!

    Did any of you guy considering legal actions????

    Also, did you noticed that the thread started in May!!!!!! The problem may have started earlier than that!!!

    Thanks for sharing.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-09-14T08:26:14+00:00

    My replaced one got an update to 1.0.34. It worked some weeks and now I got the same error: No Bootable device.

    Oh no, that's the worst nightmare ... I will try to block this update because I do not want to have a defective device again. For me, this firmware update appeared in WU after updating Windows 10 to version 20H2.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-09-14T08:27:43+00:00

    Christoph_71 -- What the heck?? seriously? I still have an open ticket. I am going to ask if there is a way to jump 1.0.34

    Please, let me know when you find out if the Surface Go update to version 1.0.34 is safe now?

    Was this answer helpful?

    0 comments