Blue screen error after downloading software update. File:BCD Error code:0xc0000098

Anonymous
2019-02-26T22:12:31+00:00

Erro code 0xc0000098 blue screen on surface go after download of software update

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
Answer accepted by question author
Anonymous
2019-06-21T00:35:50+00:00

Well, I was able to fix my surface although will now have to re-install a bunch of things.

A few tips for those wanting to self fix.  Download the Surface image and put onto a USB.  You will need a USB-C to USB-A adapter if you have a Surface Go.

If stuck in the Blue screen of death loop, go to the Surface UEFI menu by pressing the Windows Key.  In boot order, order the USB higher up than the Windows Boot.

Boot from Surface, then follow the instructions provided by microscoft.

i.e. Select Keyboard

From there -> Troubleshoot, recover from device, skip key entry, recover vs. clean wipe depending on your uses

Now, I think this problem is related to Windows Update and surfaces since it's happened to a bunch of people.  Hope microsoft can look into this.  A bit nervous to install windows updates again

Was this answer helpful?

9 people found this answer helpful.
0 comments

49 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-08-08T05:29:24+00:00

    I am facing the recovery error in my surface. What can I do??

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-08-01T10:25:23+00:00

    I actually had the 0098 BCD error after the 1903 upgrade failed, and these instructions above recovered my Surface Go. It booted up and completed the 1903 update and everything was fine.

    Anyway it fixed my issue so it may help someone else who doesn't want to rebuild their Surface after this 0098 BCD error

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Barb Bowman 80,815 Reputation points MVP Volunteer Moderator
    2019-08-01T09:38:54+00:00

    That is a (good) fix for a different error. This thread is about the 0098 error
    and the read only fix you found is for a 0025 error. This is not the issue the
    others in this thread have.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-08-01T00:35:12+00:00

    Here is the fix that worked for me, which I found from this link : https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-bootrec-fixboot-access-is-denied/747c4180-7ff3-4bc2-b6cc-81e572d546df?page=23

    I think the issue is the 1903 update caused the UEFI boot partition to become read only, as I was getting access denied when trying to do anything with it.

    Grab a Bootable Windows 10 Installation USB:

    1. Insert the Media USB in your Surface GO and restart. (a USB C hub with USB A ports worked ok here)
    2. Boot from the USB.
    3. Select Repair Your Computer.

    Select Troubleshoot.

    1. Choose Command Prompt from the menu: (you may have to enter your Bitlocker recovery key if you have it enabled)

    Type in the command:

    Diskpart

    Type in the command:

    List disk            (Note which disk is your Boot drive number mine is 0)

    Type in the command:

    Sel disk 0

    Type in the command:

    List vol               (Note which volume is the EFI partition mine is 4)

    Type in the command:

    Sel vol 4

    Type in the command:

    assign letter=V:

    Type in the command:

    Exit

    Type in the command:

    V:

    After you have assigned a drive letter Using Diskpart You can format the EFI partition:

    Example: if you assigned a letter V to the partition the command would be:

    format V: /FS:FAT32

    Type in the command:

    bcdboot C:\windows /s V: /f UEFI 

    Reboot (you may have to enter your Bitlocker recovery key if you have it enabled)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments