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-09-19T09:49:01+00:00

    You have to format you rusb to FAT32, otherwise it will not boot up and statys in a loop.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-09-17T20:37:53+00:00

    NO this does NOT work. I have had two service technicians help with this and still does not work! This definitely does not solve the problem!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-09-17T08:05:29+00:00

    Yes, I just left it and in the end, I got the blue progress bar

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-09-17T07:59:34+00:00

    I think my battery was not fully charged, which caused the boot loop

    now it is working.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments