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-08-02T05:20:24+00:00

    We got the same problem. The surface was out of warranty, but in Sweden there is a law that the seller of a new product is accountable for fixing the product if it is a fault the user can't have created. The first year, the evidence burden lies on the seller that the fault is user created, and in the two following years that changes so the user needs to be able to show that they havent misused the product and that the fault has been there all along (ie would have happened anyhow).

    Short story - the exchanged ours without any protests .

    I really hope they do the same for the rest of you, this will tarnish the surface brand and its crazy that a company gets away with stuff like this. I've seen far worse from apple, and really didn't think MS would be this greedy....

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-08-01T19:19:45+00:00

    Hi masd

    It's great you started this.

    You can join a discord channel I created for people with this problem. https://discord.gg/4HF8UtPd also, here's a page with how my case went through https://telegra.ph/Surface-Go-firmware-bug-bricks-the-device-06-24 

    Also, no need to post the same message 4 times, you end up just spamming subscribers' email.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-08-01T19:15:10+00:00

    HOLDING MICROSOFT TO ACCOUNT - I'VE STARTED THE BALL ROLLING!!

    I have been in this discussion now for several weeks and have raised two tickets with MS, both times when I requested escalation they have just ignored me! So I am angry and reading how many others that we know of here are affected, some with substantial loss of data, loss of all they operations due this issue, I'm even angrier.

    Some of you have mentioned taking a Class Action out against MS and I have now looked into this. I am based in the UK and have found a great platform where we can take collective action together.

    To start with we must find ALL the people affected by this issue, including all those who I fear have simply bought new devices, my guess is around the world there will be thousands. This will begin as a campaign which once we get 50 of us in the group we will then take out to the media. From here we will leverage to hold Microsfoft accountable.

    This is the link for the campaign page so join and spread as far and wide as possible! https://findothers.com/campaign/calling-on-microsoft-to-compensate-surface-go-owne

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-08-01T19:10:52+00:00

    HOLDING MICROSOFT TO ACCOUNT - I'VE STARTED THE BALL ROLLING!!

    I have been in this discussion now for several weeks and have raised two tickets with MS, both times when I requested escalation they have just ignored me! So I am angry and reading how many others that we know of here are affected, some with substantial loss of data, loss of all they operations due this issue, I'm even angrier.

    Some of you have mentioned taking a Class Action out against MS and I have now looked into this. I am based in the UK and have found a great platform where we can take collective action together.

    To start with we must find ALL the people affected by this issue, including all those who I fear have simply bought new devices, my guess is around the world there will be thousands. This will begin as a campaign which once we get 50 of us in the group we will then take out to the media. From here we will leverage to hold Microsfoft accountable.

    This is the link for the campaign page so join and spread as far and wide as possible! https://findothers.com/campaign/calling-on-microsoft-to-compensate-surface-go-owne

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments