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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-06-22T21:57:55+00:00

    When a Microsoft firmware update bricks a Microsoft device this is on the shoulder of Microsoft to fix it on their dime. This is the sort of thing that is what class action lawsuits are made for.

    Microsoft broke it, they are the only ones that can fix it. It's not a hardware issue, it's a firmware mess that did not get proper testing before it was released.

    I assume there are very few Surface Go 1 devices still under warranty.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-06-13T03:33:11+00:00

    I have the same issue ("no bootable device") on my wife's surface go with Uefi firmware 1.0.34.

    • Attempted Recovery, it does not work - just loops back to recovery menu.
    • checked the disk for errors in cmd, it passed.
    • In cmd I was able to access the drive and all partitions to see files are there, back up my files to external USB.
    • Completely wiped the disk clean, re formatted for fresh install .
    • Attempted fresh windows install which seems to install but once the usb is removed returns back to "No bootable device'

    All hardware is good, this must be a firmware issue.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-06-09T00:09:12+00:00

    I have exactly the same issue and got an exatly the same response from MS. I have firmly confirmed them that it is raised by their 1.0.34 firmware update and told them all measures, not beyond human imaginations, have been taken. The ONLY result is the same - "No Bootable Device". They are trying to ask me to get the deivce being "Tested and Reparied" at my cost! Just imaging: THEIR fault, MY cost! Has anybody ever seen anything as such ridiculous?!

    Such unimaginable suggestion is definitely to be rejected. Then I was told that they are going to escalate the issue, but no body reaches me yet! (The girl told me that somebody at local service deparment will call me)

    Waiting for MS doing their due job as a grown-up.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-06-07T09:22:37+00:00

    Yeah..i'm on my 2nd case number also.

    " Just to clarify dear xxxxx, modifying the Firmware cannot be done as mentioned, what we can do now is engage the hardware team on this case so they can investigate the issue and further assist us on how to proceed

    HamidJune 7, 2022, 7:18 pm"

    So back in circles again

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments