Naren:

Yes, I see that you are missing an object in the BCD for starting the recovery environment. There is also an "Unknown" pointer in the element for resuming from hibernation.

I can't help you with this one. Your BCD is highly customized by the manufacturer and I'm not familiar with the syntax that they are using. I suggest that you look for help in a Dell forum or contact Dell directly. If Dell can provide you with a recovery DVD to restore your system to original factory state, that may be your best bet.

thanks u so much, I had forgotten that I have a dell recovery cd. Well my problem fixed. But there was a problem in Diagnostic screeshot and bcd list attached

I hope you can correct these problems  :)

thank u sir

Hi, 

I've an HP Z440 workstation. When I bought it I asked a Win 7 downgrade (from 8.1) on an SSD instead of usual 1 TB Hard Disk.

Now I'd like to use the Recovery Partition (a dedicated partition, size 11,7 GB), but I cannot reach it. I only have 8.1 recovery disk, and none about Win7
The reseller told me that workstation came with the 1TB hard disk equipped with Win7, and he cloned it on the SSD. I think that's the point the recovery partition messed out, but I cannot fix it.

The disk is in GPT mode, so i cannot make the recovery partition active in order to boot at startup.

Reading previous post I cannot understand what to do, can anybody help me?

I attach the bcedit output (standard and verbose), thanks in advance if anybody can suggest something!!

Gab

Gab:

Your BCD looks to be configured correctly to boot into the Windows Recovery Environment. According to HP, you press the F11 key repeatedly as the system boots: http://smallbusiness.chron.com/boot-off-recovery-partition-hp-53080.html

If this doesn't work, are you able to access the UEFI boot options by pressing F10? http://h30434.www3.hp.com/t5/Business-PCs-Workstations-and-Point-of-Sal…

If so, I see a number of UEFI firmware boot options defined in the BCD; several of them say "System Diagnostics" and "HP Recovery". If your F10 key allows access to the UEFI boot options, try those.

Hi Mark, 

My name is heru from Borneo.

My windows pro (x64) can't boot to windows.  I have tried repairing it with CD/DVD Windows 7, but there are message "This version of System Recovery Options is not compatible with the version of Windows youa arae trying repair". I just want to be able to boot sucessfully. Can You help me?

Hello, Heru:

I have seen that error message before. Here is an article that describes various workarounds: http://techspeeder.com/2014/09/03/this-version-of-system-recovery-optio…

Mark Wharton wrote:

Here are the appropriate entries that need to be repaired:

=======================================================
Windows Boot Loader
-------------------
identifier {e6752484-d2da-11de-8cd2-cdc3b318e7d5}
this one is missing references to the device and osdevice partitions

Device options
--------------
identifier {e6752485-d2da-11de-8cd2-cdc3b318e7d5}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\e6752484-d2da-11de-8cd2-cdc3b318e7d5\boot.sdi
========================================================

What probably happened was that the partitions on the disk were probably 2048-sector offset if they were created by Vista or the Windows 7 installer. When you restored, TI changed the offset to 63-sectors, and thus the BCD pointers were incorrect. Here is how you can fix them.

<sarcastic comment>God bless Microsoft for using GUIDs in the BCD and for the name of the recovery folder</sarcastic comment>; you have to be really careful to type every character correctly or it won't work. It will help to copy and paste the GUIDs instead of typing them. You could try copying and pasting from the text below if the forum software hasn't added any stray spaces or characters and if I haven't made any mistakes:

===============================================================
Steps to add the Windows Recovery Environment (WinRE) to the Windows 7 BCD store.
12/12/2009  MJW

The general syntax of the commands needed to add the three missing entries is:
bcdedit /set {GUID1} device ramdisk=[C:]\Recovery\GUID1\Winre.wim,{GUID2}
bcdedit /set {GUID1} osdevice ramdisk=[C:]\Recovery\GUID1\Winre.wim,{GUID2}
bcdedit /set {GUID2} ramdisksdidevice partition=C:

Where the GUIDs for your case are:
GUID of boot manager entry: {GUID1} = {e6752484-d2da-11de-8cd2-cdc3b318e7d5}
GUID of device options entry: {GUID2} = {e6752485-d2da-11de-8cd2-cdc3b318e7d5}

So the commands would be as follows. Each command is all on one line:
bcdedit /set {e6752484-d2da-11de-8cd2-cdc3b318e7d5} device ramdisk=[C:]\Recovery\e6752484-d2da-11de-8cd2-cdc3b318e7d5\Winre.wim,{e6752485-d2da-11de-8cd2-cdc3b318e7d5}

bcdedit /set {e6752484-d2da-11de-8cd2-cdc3b318e7d5} osdevice ramdisk=[C:]\Recovery\e6752484-d2da-11de-8cd2-cdc3b318e7d5\Winre.wim,{e6752485-d2da-11de-8cd2-cdc3b318e7d5}

bcdedit /set {e6752485-d2da-11de-8cd2-cdc3b318e7d5} ramdisksdidevice partition=C:

After entering these three commands, check them again with bcdedit /enum all. You should see these two corrected entries:
================================================================================
Windows Boot Loader
-------------------
identifier              {e6752484-d2da-11de-8cd2-cdc3b318e7d5}
device                  ramdisk=[C:]\Recovery\e6752484-d2da-11de-8cd2-cdc3b318e7d5\Winre.wim,{e6752485-d2da-11de-8cd2-cdc3b318e7d5}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\e6752484-d2da-11de-8cd2-cdc3b318e7d5\Winre.wim,{e6752485-d2da-11de-8cd2-cdc3b318e7d5}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Device options
--------------
identifier              {e6752485-d2da-11de-8cd2-cdc3b318e7d5}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\e6752484-d2da-11de-8cd2-cdc3b318e7d5\boot.sdi
================================================================================
.

.

.

Thank you SOOOO much! This post just helpd me a ton! I had acidentally destroyed my recovery partition and went through the process of manually fixing it. I had to recreate the 100MB partition. I used another working machine with Win7 on it to copy over the contents of the partition followed by the 4 bootrec commands to fix my BCD. This got my Win7 install booting however my PE environment would no longer work when I used F8 to "Repair your computer".

I then ran the first 3 commands though when I looked at my BCD again I noticed the ramdisksdipath was still incorrect. I then ran the last command to re-point that and all was fine.

bcdedit /set {28f0d4c7-2054-11e5-bf1f-e540a2a71f53} device ramdisk=[C:]\Recovery\7d6ec772-2a1f-11e2-b7b2-f241181ac250\Winre.wim,{28f0d4c8-2054-11e5-bf1f-e540a2a71f53}

bcdedit /set {28f0d4c7-2054-11e5-bf1f-e540a2a71f53} osdevice ramdisk=[C:]\Recovery\7d6ec772-2a1f-11e2-b7b2-f241181ac250\Winre.wim,{28f0d4c8-2054-11e5-bf1f-e540a2a71f53}

bcdedit /set {28f0d4c8-2054-11e5-bf1f-e540a2a71f53} ramdisksdidevice partition=C:

bcdedit /set {28f0d4c8-2054-11e5-bf1f-e540a2a71f53} ramdisksdipath \Recovery\7d6ec772-2a1f-11e2-b7b2-f241181ac250\boot.sdi

My difference was that I actually had 3 GUID's. The recovery directory on my C drive was under a different, probably from some old botched install. Anyway repointing worked.

Chris:

You're welcome. Glad you got your Win PE working again.

Mark, you right
I have solved my problem using the same cd repair, the problem is in BIOS using EFI. However many thanks

Hi Mark.

I have an issue with starting my computer. It shows an error on a blue screen saying that: 

Recovery

Your PC/Device needs to be repaired

The Boot Configuration Data file is missing some required information.

File:\Boot\BCD

Error code: 0x0000034

You'll need yo use recovery tools. If you don't have any installation media (like a disc or USB device), contact you PC administrator or PC/Device manufacturer.

So i searched internet and found some solutions and tried them. I created recovery USB from another computer and tried it. I tried bootrec /rebuild bcd and other commands but dont worked at all. I dont want to loose some photos and files in my PC. So i hope there is a way to repair it without deleting my personal files.

So you are one of my last chances i think. Please help me.

I attached my bcdoutput. It has some Turkish words in it. I hope you can understand.

Umut Mert:

I see that you are missing most of the entries for the first BCD object in your attached bcdoutput.txt file. This object is the one that Windows uses to start the boot process and should look like this (in English; the title and identifier will appear in Turkish on your machine). Note that you only have the first two lines in your BCD, the title and the identifier. You need the rest of the lines:

Windows Boot Manager
--------------------
identifier            {bootmgr}
device                 boot
description          Windows Boot Manager
locale                  tr-TR
inherit                 {globalsettings}
default                {default}
resumeobject      3ba6109a-74f8-11e5-93f6-a5ce5c2d82a5}
displayorder        {default}
toolsdisplayorder   {memdiag}
timeout                 30

I am going to make an assumption that you have a standard BIOS motherboard (not the newer UEFI) and that your system has an active partition that it boots from. If my assumptions are correct, here are the commands that you need to enter to fill in the missing entries in the boot manager object.

You should boot your machine from the recovery medium that you used to capture and print out the BCD listing that you attached to your post. Once there, open a command prompt window and copy/paste each of these commands, one at a time. When done, list the bcd and compare the first object, "Windows Boot Manager" to the text above to verify that you have entered all of the commands correctly. When satisfied, try rebooting your PC.

Here are the needed BCD commands:

bcdedit /set {bootmgr} device boot
bcdedit /set {bootmgr} description "Windows Boot Manager"
bcdedit /set {bootmgr} locale tr-TR
bcdedit /set {bootmgr} inherit {globalsettings}
bcdedit /set {bootmgr} default {default}
bcdedit /set {bootmgr} resumeobject {3ba6109a-74f8-11e5-93f6-a5ce5c2d82a5}
bcdedit /set {bootmgr} displayorder {default}
bcdedit /set {bootmgr} toolsdisplayorder {memdiag}
bcdedit /set {bootmgr} timeout 30

Hopefully, this will get you back in operation.

Heya Mark, I have a Windows 8.1 computer that won't boot, it's an HP Laptop. Wondering if you would see if the boot config is to blame? Thanks in advance!

Sai:

I see a normal-looking BCD for a UEFI PC.

How far does the laptop get in the boot process? Can you describe what happens when you attempt to boot it?

Hard drive was dying so it is probably just corrupted system files, tries to boot to advanced recovery and then generic BSOD "your pc ran into a problem" cyclical nightmare. I will just format it. Thanks for looking at the BCD Mark. Have a nice day!

Mark,
would you mind offering some advice to me? Im using windows 7 and have the same no repair your computer option on advanced boot menu, i appreciate anything from you..

Arfy

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {1098109a-1fba-11e7-8ac0-e73c0d7cd38d}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=C:
systemroot              \Windows
resumeobject            {1098109a-1fba-11e7-8ac0-e73c0d7cd38d}
nx                      OptIn

Resume from Hibernate
---------------------
identifier              {1098109a-1fba-11e7-8ac0-e73c0d7cd38d}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume1
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 Yes

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}
 

First of all is to say thanks to Mark, it is amazing to have read all this threat and find out how many people you have help since 2009.

I recently had a crash after updating win7 so, I did a recovery which welcomed me with a Status: 0x000000f. I did unplug all HD but the 2 in RAID hosting Windows. Doing a research I found this threat, also I found another link which I thought faster than to be asking and bothering about the BCD issues. I link it here, it may be helpful.

http://windowsitpro.com/systems-management/build-bootable-bcd-scratch-b…

This worked just fine, now it recognizes my win7 but, now I got the same error with an added line:

File: \windows\system32\boot\winload.exe

Status: 0x000000f

Info: The selected entry could not be loaded because the application is missing or corrupted-
 

I have tried many times to run the windows repair disk and also out of curiosity, decided to install a whole new windows just to confirm if it was a hardware or BIOS issue but, everything seems to be "normal". I really don't know what else to do, whatever hint would be appreciated

I had the same problem --booting into wins 7 is fine but going into "repair your coputer" is not. it keeps giving me error message.
 

Hey Mark

I was wondering if you could help me with something, I am on my old windows 7 computer and i forgot the password to my admin account so i went on youtube for ways to reset/change it and i found a way in the "startup repair" to get to startup repair you have to hard shut off your computer 1-3 times so i did that then i was on the boot menu where it should be but i didnt see i rather saw 3 steps that involved the windows installion cd but i didnt have it because this is my old laptop i need to access the files on here so it would be great if u could help me with this and tell me how i could get startup repair option WITHOUT a cd/dvd. Remember i also cant use admin thing lke admin cmd etc