Surface Go uefi version is 1.0.34 and No Bootable Device error

After some 6 weeks and 4 separate attempts I am pleased to report that today I have been successful with MS Support. This was achieved through the Surface Go support chat service. They didn't even ask me for the photo of the UEFI screen. They acknowledged in black and white that the firmware update was their error and so they are replacing devices free of charge, outside of my warranty.

I feel sympathetic for anyone else that is still struggling so I will share what I can in case this will help you.

Firstly I made sure I was on the MS Surface Go support - you can check this by looking at the URL. This is the page: https://support.microsoft.com/en-us/surface-go  scroll down the page and click on Contact Us. I put in my issue as "Surface Go bricked after 1.0.34 update". I also did something different this time to the other tickerts - I selected "Hardware issue" on the drop down rather than "Technical support".

As others have reported here, it does seem they a have process in place now:

1. They acknowledge the firmware caused devices to break
2. They offer a free replacement and ask if you want to proceed with that
3. They escalate the issue to the Hardware Team - and I think this may be the key point - Hardware not Tech Support
4. Ask for your address etc
5. Process it
6. Tell you you will receive a confirmation email with the return label within 24 hours to send back your machine with.
7. Once they receive the broken device they will ship you a replacement.

The agent was very helpful, and apologetic and he said he had seen my previous unanswered emails and support tickets. So it seems that they either have finally got a solution is place and or they respond to you being persistent.

Here is the screenshot of the chat that I hope will help and encourage everyone else who is still trying to get a replacement.

I feel like sometimes it's like they don't read our commentaries. Support ain't helping Steven as our devices aren't on warranty anymore. You guys need to figure out a alternative to help us. It's not like only 2 devices aren't responsive anymore. Plenty of people on reddit are complaining about the same issue that we are both experiencing.

Please open a ticket on that problem over at Microsoft.

Just to list the steps I have tried which didn't solve the problem:

• Create a recovery USB and recover from a drive (with and without keeping my files)
• Using the "Startup Repair" option from the recovery drive
• Via Command Line from recovery drive: Using bootrec /fixmbr, bootrec /fixboot, bootrec /rebuildbcd
• Via Command Line from recovery drive: Deleting the created system EFI partition, and recreating it with create partition efi size=100 and bcdboot C:\Windows /s S: /f ALL
• Erasing the surface using the data eraser tool (https://docs.microsoft.com/en-us/surface/microsoft-surface-data-eraser), and re-installing windows using the recovery drive
• Changing the boot order in the BIOS (having each of the options "Internal Storage", "Windows Boot Manager" and "USB Storage" on top once)

If anyone has ANYTHING else I could try I would be happy to do so

Hey Steven,

I have the same issue with the FW 1.0.34 and I tried reimaging AND the erase tool and I still get the No Bootable Device at startup. I even tried going in the command prompt and typing the famous bootrec /fixboot and all of the commands and still get the same issue. Pretty sure it has something to do with the latest FW update.