none
Out of ideas for: C0000034 "The Boot Configuration Data file is missing some required information."

    Question

  • I have Windows 8 Pro x64 using UEFI boot and GPT partitions. I put it into hybernation when there was a text "Your PC will restart in 1 day to finish installing security updates" on welcome screen. Next day - it doesn't boot. It shows a light-blue screen:

    Recovery

    Your PC needs to be repaired

    The Boot Configuration Data file is missing some required information

    File: \BCD

    Error code: 0xc0000034

    I have bootable USB with Windows 8. First, I tried to boot from it and "refresh" (i.e. install over existing copy). Automatic installation option refused to do anything, saying something like "you're running setup from installation media. Please, run your local Windows and re-run installation from there". Obviosly, I can't do that - because my installed Win8 refuses to run.

    Next, I tried to manual install. This time it refuses to continue because "Can not install Windows on GPT partition" (WTF?).

    When I failed refresh option - I tried to repair. All repair options available on menu (except from the one which says it will delete your files - I didn't tried it), all repair options either says that they can't find any issues or that disk with Windows is locked (I have no idea how it can be - I can freely access and modify disk's content after opening command-line).

    My final hope was for command line and bcdboot. Running "bcdboot D:\Windows" (my system drive appears as D: when booting from USB flash) yields failure for copying files. However, "bcdboot D:\Windows /s C:" or "bcdboot D:\Windows /s D:" completes successfully. Unfortunately, these didn't help: the error remains the same. I also tries to add /f ALL and /f UEFI options, but these didn't work either.

    Now I'm completely run out of ideas. The only option that I see is to re-format the disk and fresh-install Win8...

    Saturday, July 13, 2013 10:58 AM

Answers

  • I checked that drive do not have read only attribute (via diskpart's info command).

    _________

    Anyway, I was able to solve this issue, but in a hard way...

    Here are all the pieces (in my interpretation, which could be wrong):

    1. UEFI/GPT is supported only by 64-bit Windows.

    2. BCD is stored on hidden partition for UEFI.

    3. BIOS allow you to boot from media either as UEFI or as legacy BIOS.

    4. Windows 8 upgrade download tool (Windows8-setup.exe) creates installation media based on host OS, taking into account bitness and language.

    So, I did not have installation media ready, because I installed Windows 8 from previosly installed Windows 7 (64 bit) via upgrade proposition from MS. And when I needed installation media to repair - (since I can't download ready ISO from MS) I took my 2nd old machine and go through "upgrade" process - unless I didn't really upgraded, but asked to create a bootable USB. What I didn't realize is that my old machine is running 32 bit Windows. Thus, USB media was created as 32 bit. I.e. there was no support for UEFI/GPT in that instance. That was a reason for all my issues: "unable to install to GPT", "unable to write to disk", "error accessing BCD store".

    What I do: I take my mobile HDD, tear it apart, and connected to broken PC via internal port. I installed a new 32 bit instance of Windows from my USB flash. I installed VirtualBox and managed to create VM from images of my previous Windows 7 installation (I made a backup before upgrading). Luckily, it was working (64 bit Win7 guest on 32 bit Win8 host). Then, I go through "upgrade" process again, connected USB to VM, re-created installation media. This time it was 64-bit.

    (I couldn't use my old PC for this as it was a way too weak, that's why I needed temp instance of working OS on my broken machine)

    I also made a backup of system drive for my non-working system.

    Then, reboot, boot from USB (make sure it boots as UEFI, not as BIOS), go for fresh install, delete all partitions on system HDD (I can safely do that, because I made a backup), install new fresh instance of 64-bit Win8.

    Reboot, boot from mobile HDD again (i.e. didn't finish the installation), restore only C: partition (didn't touch hidden partitions), reboot.

    System refused to run, complaining about missing winload.efi.

    Reboot from USB, go to console, execute "bootrec /rebuildbcd" command. It runs OK (actually, any previosly tried command runs OK too). Reboot -> system is booting!

    However, my joy was a way premature. System started working, displaying a "Installing updates" message, and then.... kaboom! A BSOD with C000021A error, which means one of the two core process was crashed.

    I spend another 2 days trying to figure out reason for this, unless I eventually gave up and made a fresh re-install of the system. :(

    That was a "short" summary of my actions. It's only about 10% from all of my actions. I did not mention any failred try/experiments. The entire issue took me about 4-5 days to resolve.

    Moral of the story: NEVER put your machine into hybernation, when there is "Your PC will restart in 1 day to finish installing security updates" message.



    • Edited by GunSmoker Wednesday, July 17, 2013 4:04 PM Added more details
    • Marked as answer by GunSmoker Wednesday, July 17, 2013 4:08 PM
    Wednesday, July 17, 2013 4:00 PM

All replies

  • The Boot Configuration Data file is missing some required information

    File: \BCD

    Error code: 0xc0000034

    Vista users apparently were plagued by this symptom.  Don't know how applicable its solution is to W8

    http://support.microsoft.com/kb/927391/en-us

    More ideas in this thread (where I found that one, so again, from Vista)

    http://social.technet.microsoft.com/Forums/windows/en-US/4491fe25-be44-430e-a384-fb58c5da5ad0/system-halts-in-boot-after-installation-sp1-0xc0000034-

     (Microsoft search for
        0xC0000034 bcd

    Good luck

     

     


    Robert Aldwinckle
    ---

    Saturday, July 13, 2013 8:46 PM
  • Any automatic "Repair your computer"-like options on installation media are unable to solve the problem. Perhaps, this is because they report system drive as locked? I don't get why it is locked and how can I unlock it?

    Almost any manual command-line command that I run fails too. Error messages are too generic, but I think that commands are unable to locate BCD storage? Perhaps this has something to do with UEFI/GPT? There are 2 hidden partitions on my system drive (beside system partition itself): a 300 Mb "recover" partition, 100 Mb EFI, and the rest is visible partition. All manuals that I see refers to Vista/7 case and assumes that your boot files are located on system drive. Is it holds the same for UEFI/GPT? Wiki says that boot files are located on hidden EFI system partition. Could it be the reason why I can't figure out how to make it work from command-line?

    Saturday, July 13, 2013 11:37 PM
  • I don't get why it is locked and how can I unlock it?

    Apparently it can get a Read-only attribute set on it.

    http://social.technet.microsoft.com/Forums/en-US/W8ITProPreRel/thread/5f731c27-5769-408d-a95b-8af25a9b7dc7/

    (via BING search for
        "windows 8" installed drive locked unlock drive site:microsoft.com
    )

    So, for your case you would not  do the "clean" that that poster was advised  ; )

    Almost any manual command-line command that I run fails too. Error messages are too generic, but I think that commands are unable to locate BCD storage? Perhaps this has something to do with UEFI/GPT? There are 2 hidden partitions on my system drive  (beside system partition itself): a 300 Mb "recover" partition, 100 Mb EFI, and the rest is visible partition. All manuals that I see refers to Vista/7 case and assumes that your boot files are located on system drive. Is it holds the same for UEFI/GPT? Wiki says that boot files are located on hidden EFI system partition. Could it be the reason why I can't figure out how to make it work from command-line?

    I suspect the Read-only attribute is likely to be the more significant factor.  However, I should have thought about seeing if there was an update for that Vista tip.  Oops.

    In any case Vista tips would probably have to be modified to adapt to UEFI and I'm not sure how to do that...

    FWIW here's a W7 version of the above Support article which at least mentions UEFI.  This is the only hit for this search.  So since I didn't specify an OS I don't imagine finding one which is more specific to W8:

    http://support.microsoft.com/kb/2004518/en-us

    (Search Support for
        repair bcd uefi
    )

    Hope you can puzzle it out or wait for someone who is more knowledgeable about how to use these tools.

     
    Good luck

     
    Robert
    ---



    Robert Aldwinckle
    ---

    Sunday, July 14, 2013 3:48 AM
  • I checked that drive do not have read only attribute (via diskpart's info command).

    _________

    Anyway, I was able to solve this issue, but in a hard way...

    Here are all the pieces (in my interpretation, which could be wrong):

    1. UEFI/GPT is supported only by 64-bit Windows.

    2. BCD is stored on hidden partition for UEFI.

    3. BIOS allow you to boot from media either as UEFI or as legacy BIOS.

    4. Windows 8 upgrade download tool (Windows8-setup.exe) creates installation media based on host OS, taking into account bitness and language.

    So, I did not have installation media ready, because I installed Windows 8 from previosly installed Windows 7 (64 bit) via upgrade proposition from MS. And when I needed installation media to repair - (since I can't download ready ISO from MS) I took my 2nd old machine and go through "upgrade" process - unless I didn't really upgraded, but asked to create a bootable USB. What I didn't realize is that my old machine is running 32 bit Windows. Thus, USB media was created as 32 bit. I.e. there was no support for UEFI/GPT in that instance. That was a reason for all my issues: "unable to install to GPT", "unable to write to disk", "error accessing BCD store".

    What I do: I take my mobile HDD, tear it apart, and connected to broken PC via internal port. I installed a new 32 bit instance of Windows from my USB flash. I installed VirtualBox and managed to create VM from images of my previous Windows 7 installation (I made a backup before upgrading). Luckily, it was working (64 bit Win7 guest on 32 bit Win8 host). Then, I go through "upgrade" process again, connected USB to VM, re-created installation media. This time it was 64-bit.

    (I couldn't use my old PC for this as it was a way too weak, that's why I needed temp instance of working OS on my broken machine)

    I also made a backup of system drive for my non-working system.

    Then, reboot, boot from USB (make sure it boots as UEFI, not as BIOS), go for fresh install, delete all partitions on system HDD (I can safely do that, because I made a backup), install new fresh instance of 64-bit Win8.

    Reboot, boot from mobile HDD again (i.e. didn't finish the installation), restore only C: partition (didn't touch hidden partitions), reboot.

    System refused to run, complaining about missing winload.efi.

    Reboot from USB, go to console, execute "bootrec /rebuildbcd" command. It runs OK (actually, any previosly tried command runs OK too). Reboot -> system is booting!

    However, my joy was a way premature. System started working, displaying a "Installing updates" message, and then.... kaboom! A BSOD with C000021A error, which means one of the two core process was crashed.

    I spend another 2 days trying to figure out reason for this, unless I eventually gave up and made a fresh re-install of the system. :(

    That was a "short" summary of my actions. It's only about 10% from all of my actions. I did not mention any failred try/experiments. The entire issue took me about 4-5 days to resolve.

    Moral of the story: NEVER put your machine into hybernation, when there is "Your PC will restart in 1 day to finish installing security updates" message.



    • Edited by GunSmoker Wednesday, July 17, 2013 4:04 PM Added more details
    • Marked as answer by GunSmoker Wednesday, July 17, 2013 4:08 PM
    Wednesday, July 17, 2013 4:00 PM