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 No comments

362 additional answers

Sort by: Oldest
  1. Anonymous
    2022-06-14T10:12:41+00:00

    Keep us posted how you go...I'm back to radio silence

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-06-14T19:30:15+00:00

    Same here since today.

    "No bootable device"

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-06-15T07:51:30+00:00

    I've had the same issue since Saturday, with my daughter's Surface Go, which she uses for her schoolwork. Has anyone had any ideas on how to revert or fox the firmware?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-06-15T08:08:56+00:00

    So far no ... we can't rollback our own firmware and most of us... our devices are out of warranty.

    If you contact support (which you should do just so there are more case #'s) you'll probably get similar responses..but keen to hear how you go.

    Was this answer helpful?

    0 comments No comments