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-03T14:42:16+00:00

    Dear Microsoft

    It's a sad moment, but honestly we both knew it would happen one day. To make it short, it's time to say goodbye. We look back at many years we've spent together. From Windows 3.1 on, I worked with each Version of Windows, and I don't know how many hundred installations i did. Then I've been super excited when I installed the first Beta of the .net SDK 1.0, or when I downloaded all those fancy-named previews of SQL Server .net. I've built codezone.ch for you, the first swiss .net developer community. I still do carry with pride the orange bag from Tech.Ed 2004 at Amsterdam. And I introduced SharePoint (MOSS is how we called it back then) and Dynamics CRM at hundreds of clients. I even used Bing instead of google, which I think tells more about my loyalty than anything else. And until recently, edge was my default browser.

    Now you broke my Surface go.

    Well, we all make mistakes, but at least we should admit them, and try to fix things. That's what I so painfully miss here.

    I did somehow feel it coming. Just recently I installed Debian on my old Thinkpad, I replaced OneDrive by Nectcloud, and if it wasn't for my wife, I would have replaced o365 by LibreOffice already. While all these solutions aren't any better or more comfortable than your stuffs, they have one advantage: The people behind them did not disappoint me the way you just did. So I will get rid of my last Microsoft products, together with my now unfortunately useless Surface Go, and move forward.

    I honestly wish you all the best, and I do hope you will sooner or later learn to take your customers (as in where the money that pays your salary comes from) serious.

    Martin

    P.S: Please, please don't suggest to use an usb recovery image, or the eraser tool. It won't fix neither my Surface nor our relationship.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  2. Anonymous
    2022-05-28T22:25:06+00:00

    Hi Stephen,

    The drive icon isn't displayed which is why I feel it's a firmware issue.

    There are a number of reddit reports of the same issue with this firmware.

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments
  3. Anonymous
    2022-05-31T01:18:02+00:00

    As I said on my initial post ... I've already done the recovery image and it failed.

    I have a growing concern this is a bug with the firmware update that occurred this month. There are a number of reports here and on reddit reporting exactly the same behaviour. Could you tell me how to report this.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  4. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2022-05-31T08:58:35+00:00

    Steven,

    As I said on my initial post ... I've already done the recovery image and it failed.

    I have a growing concern this is a bug with the firmware update that occurred this month. There are a number of reports here and on reddit reporting exactly the same behaviour. Could you tell me how to report this.

    Thanks for confirming, Bronwen Zande.

    If I may ask, have you also done performing the Surface Data Erase tool? If not, please see Microsoft Surface Data Eraser (Surface) - Surface | Microsoft Docs on how to.

    If you filter on Surface Go, you will see multiple threads with this issue after this firmware update. There are 50+ me too's. Also threads on Reddit.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments