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: Newest
  1. Anonymous
    2022-06-09T20:23:51+00:00

    This is ridiculous. I've been trying to open a support request, but it leads me back to the community page WHERE THEY TELL ME TO OPEN A SUPPORT REQUEST. It is impossible to talk to an actual human and responses in the support do not acknowledge that it is a firmware issue. I've lost all hope

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-06-09T09:16:57+00:00

    I have te same issue after updating on version 1.0.34.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-06-09T08:47:31+00:00

    And back to the "It's out of warranty....we can still process a replacement for only 353.87 AUD."

    Sigh. It's super disappointing nobody wants to even consider this is a firmware issue ....

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. 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 No comments