Windows 7, "Repair your computer" F8 boot option not working (SOLVED)
Oh no it just bsoded again but it happened when I went on the and control centre and changed the scaling as I'm running on a 22inch HDTV
Horatio:
It looks like you're onto something. Go to the website of your video card's manufacturer and download the recommended Windows 7 driver for the card.
It auto downloaded the driver when I rebooted, it was only when I went to the amd catalyst control centre and changed the scale of the monitor so that it was at full screen without a black border, that it bsoded.
Horatio:
A lot of people make ATI video cards and some will work fine with the generic Windows driver; others won't. You should still search for and install the driver that is specific to your brand of video card from the manufacturer's web site. Before installing the correct driver, I would uninstall the Catalyst control center and then reinstall it after installing the video driver.
OK thanks will try that
OK thanks will try that
Simple Ques ref True Image 2012
The backup drive is full with continuous backup. I would like to start with a fresh backup. I cannot seem to delete the image or format the drive. Any ideas how to clean this drive?
Simple Ques ref True Image 2012
The backup drive is full with continuous backup. I would like to start with a fresh backup. I cannot seem to delete the image or format the drive. Any ideas how to clean this drive?
Delete should be available when you choose recovery of the NSB, from memory it needs to be selected from the small cog icon.
Hi Mark
Apparently the issue with "Repair my computer" missing from "adv boot menu" keeps comming back.
It happened to me after I upgraded to Win8. Wanted to roll back to Win7 but no luck. Microsoft does not leave you the choice really.
Decided do it from scratch and to go back to factory settings, personalize it and make my own backup image.
I tried to sort things out myself and have gone throught previous posts but every case is different. I messed it up earlier and spent a day to figure it out. Time to ask for help.
Is there anything you recon that might be incorrect in the attached file. I'd be much appreciated.
Pau:
There are no entries in your BCD for the Windows Recovery Environment, so that's why it isn't working. Let's try the simple fix first. Enter the following in an elevated command prompt window:
reagentc /enable
If this doesn't work then please post the output of the following command:
reagentc /info
which should look something like this:
If this doesn't list the path to the recovery folder then see if you can find it on your PC and post its path. You will need to enable the display of both hidden and of protected operating system files in order to see it.
Mark
Tried that before but didnt work.
C:\Windows\system32>reagent /info
'reagent' is not recognized as an internal or external command, operable program or batch file.
ReAgent.dll and Reagent.exe are both in C:\Windows\system32\
When I register the lib:
C:\Windows\system32>regsvr32 reagent.dll
it gives me this:
"The module 'reagent.dll' was loaded but the entry-point DIIRegisterServer was not found. Make sure that 'reagent.dll' is a valid DLL or OCX and then try again"
I am looking for a solution but I also relay on you if you know what's causing it.
Rgds.
Pau:
Are you running the reagent command in an elevated command prompt window? The response will be as you have shown if the command is run in a standard user command prompt window.
Yes, I run command line as administrator.
As you previously requested my recovery partition is not hidden and the image is under R:\Recovery\43b67941-3772-11e2-b023-005056c00008
Meantime I was trying to recover it using imagex.
imagex /apply R:\dell\image\factory.wim 1 c:\
I was able to launch it but stopped on threads that Windows is using.
Not sure if this is a good step.
EDIT:
Now it does recognize the command but with error
c:\Windows\System32>reagentc /info && /enable && /setimage [...]
REAGENTC.EXE: Operation failed: 2
The system cannot find the file specified.
Someone had the same problem few pages ago and I believe it hasnt been resolved.
I'll keep troubleshooting anyway.
Pau:
For the command reagentc /enable to work, the file C:\Windows\System32\Recovery\ReAgent.xml has to be present and populated with the correct pointers to the recovery environment.
Until your last post, I wasn't aware that you were trying to get the Dell Recovery function working. Is that your intention?
Is there a /boot folder on the R: partition? A BCD in the folder? What are its contents?
bcdedit /store R:\boot\bcd /enum all
My appologies I didnt specify it earlier.
Good news is I was able to restore it to the factory state as I wanted. Followed steps suggested by Nenda BS on page 3 in this thread (e.g. copied reagent.xml).
But after restoration I couldnt boot up the system nor F8 option.
I got error:
File: \Boot\Bcd
Status: 0xc000000f
For some reason bcd was not restored.
I made bootable usb memory stick with "Hirens" diagnostic tools and booted my Windows 7 through it.
What happend next:
- there is nothing in mbr
- bcdedit /enum all shows:
The boot configuration data store could not be opened.
The system cannot find the file specified.
- the boot tab in msconfig is empty (no entry)
- tried to rebuild or restore new bcd with Bootrec /RebuildBcd but no luck
- disk part didnt help me too much
Used some diagnostic mbr fixing tools from diagnostic usb but all was being written to the usb drive, not local drive.
I noticed I cant install anything.
The partition with Windows 7 is flagged and active.
I'll try with bcdedit -set / -create tomorrow.
I'll keep you posted.
Pau:
On a standard Dell PC with a recovery partition, the boot files and the BCD are located in the recovery partition, which should be active. Try making the recovery partition active. You can use diskpart, PTEDIT32, gparted, or there may be a suitable tool on your Hirens stick.
Making the recovery partition active fixed BCD.
All is working as required.
Just wonder why the user that I created during the first Windows start was unable to install programs.
I had to create a new one and delete the original.
I appreciate your help.
Have a good one.
Pau:
It all makes sense now. Your first BCD showed the PC booting from the Windows partition and no recovery entries. When you posted about having a Dell recovery partition, I suspected that the BCD with the recovery entries was located there. Glad that you have it sorted.
I've run into strange behavior with Windows that is only fixed by creating a new user profile. There's probably a way to fix this but I didn't have the patience to figure it out. Creating a new profile is the expedient solution.
Hi Mark,
You have the patience of a saint :-)
I've spent the past few hours reading this thread and looking at the various fixes you've highlighted to resolve people's various issues. Like most I am stumped when it comes to decrypting the windows messages. Are you able to take a assist with the problem I'm having?
Background info on the issue and what I've done to date.
1 Built a brand new PC as Win 7 64bit (OEM disk) a few days ago. SSD as the boot/system (c:) drive and 2 x 1TB drives as mirrored storage (E:). Blu-ray/Dvd drive (d:)
2. Installed all the software I need (office, Virus, etc)
3. Created a system restore image okay
4. Went to create a repair disk through the Windows control panel app and got this error "System repair disc could not be created - The parameter is incorrect: 0x80070057." Also noticed that F8 doesn't seem to work.
5. Tried to create the repair disk from the original OEM disk from boot up and get an error message along the lines of "system repair is not compatible with the installed version of Windows"
6. Tried a clean boot option (In this thread) and then running the repair disk app thinking that maybe it was the virus software causing an issue. No joy!
7. Tried Klicksters suggestion in this thread here. No joy!
8. This is where I have come to this thread and trawled through the various problems people are having. Attached are the bcedit and reagentc screenshots. Plus a shot of the disk mgmt console
9. From my own limited knowledge and from what I've read on here it appears that bcedit looks okay but my recovery environment and winre.wim directory are missing from the reagentc info screen. However not sure how to resolve this and certainly don't want to do something that will cause further issues.
Any ideas?
Thanking you
Rankin:
You are getting the error message "System repair disc could not be created - The parameter is incorrect: 0x80070057." because the path to the Recovery environment in the file C:\Windows\System32\Recovery\ReAgent.xml is missing or incorrect.
Your response from ReAgentc /info looks like mine except for this entry. For reference, mine looks like this:
============================================================
C:\Windows\system32>reagentc /info
Extended configuration for the Recovery Environment
Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\1891464f-9a7d-11de-9ebe-fe9c458232f8
BCD Id: 1891464f-9a7d-11de-9ebe-fe9c458232f8
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful
==================================================================
I'm not sure how you would get the file to have the correct entry since, if you examine it in a text editor, besides the path to the recovery environment you need partition IDs and offsets. You could try this. First, save a copy of the ReAgent.xml file and a copy of the existing BCD. Then try to disable, then enable the recovery environment with ReAgentc. In an elevated command prompt, try:
reagentc /disable (this should remove the recovery entry from the BCD)
reagentc /enable (this should add the entries back)
Look again at Reagentc /info to see if the path to the recovery environment is now present. But first you will have to reboot to see the changes.
I agree that your BCD looks correct, provided that the Recovery folder and its files are in the locations shown in the BCD.
Getting the F8 key to work on a fast, modern PC requires that you hit the F8 key at the precise instant when the OS is scanning for the keystroke. It may take a little practice to get it right. I usually have to tap the key rapidly just as the BIOS finishes POST and before Windows starts to load. To get around this you could try the command reagentc /boottore, which will configure the BCD to launch WindowsRE once at the next reboot.
Note that Microsoft had to give up on using the F8 key in Windows 8 since the new OS boots so fast. I read that the window for scanning the keystroke on modern PCs using Windows 8 was only 250 msec wide, which would have required almost perfect timing on the part of the user, so they abandoned this method.
Hi Mark,
Thank you for your response.
trying reagentc /disable returns this;
C:\Windows\system32>reagentc /disable
REAGENTC.EXE: Operation failed: 2
The system cannot find the file specified.
and enable this:
C:\Windows\system32>reagentc /enable
REAGENTC.EXE: Operation failed: 57
The parameter is incorrect.
I compared your reagentc /info file against another Win8 laptop build I have and this part of the file is the same as yours
\\?\GLOBALROOT\device\harddisk0\partition1\Recovery
I wonder if there's a way to define this by some command?
Also, I'm confident I'm hitting the F8 key at the right moment. When I do hit it, instead of the Safeboot options I get the option to select which drive I want to boot from.
Running the reagent /boottore command goes into the recovery options okay? Is there anything I could check from there
regards
Rankin:
I have been trying to find the time to experiment with editing the ReAgent.xml file but have not been able to get out from under a heavy workload at the office. If I can figure out how the id and offset values in the WinRE Location Path are determined then you could probably edit your file to correct the errors you see when running the ReAgentc command. I've attached a copy of my file so that you can compare it to yours.
It sounds like your PC BIOS is using the F8 key for another purpose (to select the boot device). My Dell and Lenovo PCs use the F12 key for that purpose. Try holding down the space bar right after the BIOS power-on self-test completes and immediately before Windows starts to boot. That should stop the boot process at the Windows Boot Manager screen (that's normally not displayed if you have only one OS installed). From there you should be able to access the Advanced Boot Options. This may be your only method of getting to this menu if the BIOS has taken over the F8 key.
Hi Mark
My girlfriend seems to having the same issue as many people and while I need to get it fixed I realllllly need to get one word document off the computer as my girlfriend has an essay that needs to be handed in tonight.
Is there anyway to get into the main hard drive and pull that file with this error?
Mark:
The easiest way is to boot the PC from a CD containing a recovery environment. For example, if you're running Windows 7 then you would make a System Repair Disk on another Windows 7 PC (type "Repair" in the Start/Search box and choose "create a system repair disk"). You can also boot the PC from a Windows installation DVD or you can use a Live Linux CD; anything that allows you to access the disk with your file on it. Then copy the file to a flash drive.
Hi Mark:
I was reading all the topic because i have a similar problem like other but i tried to do the steps in your comments before but i stell have the same proble.
The proble is i want to use restore system in my Vaio whit W7 x64 it has a hidden partition but when i restart and press f10 to run the system recovery only show me a black screen whit this message ( edit windows boot option for windows 7 path:/windows/system32/winload.exe partition:2 ) i tried to follow the steps in the firs page but didn´t work.
Before this ocurre i create a partition for intall fedora and a few days ago i unistall and join that partition with disk C: i didn´t modify the system restore.
I appreciate you help
Thanks for your time
Alfonso:
Your BCD looks correct for booting to the Windows Recovery Environment located on the main Windows partition (partition 2 with drive letter C:) However, your first partition is a Sony Recovery partition, and I suspect that's what you want to have working.
There isn't an entry in the BCD for booting into the recovery partition, and I don't know how Sony has set this up. I would suggest that you check with Sony or one of their user forums. Some manufacturers will make available recovery disks that can be used for this function.
Thanks mark im going to serch in the Sony forums that boot option and look for a recovery disk.
Thanks for you help and you quick help.
First at all, forgive my english.
Could anyone help me, please? I'd like to boot from the recovery partition but I can't. I copyed the recovery partition using acronis; I formatted and installed windows again and finally I paste the recovery partition using acronis. Now, obviously, I can't recover.
This is my bcdedit table.
----
C:\WINDOWS\system32>bcdedit /enum all
Administrador de arranque de Windows
----------------------------------
Identificador {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale es-ES
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {acd019eb-60dd-11e2-a720-a432d392ac08}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Cargador de arranque de Windows
-----------------------------
Identificador {acd019e9-60dd-11e2-a720-a432d392ac08}
device ramdisk=[C:]\Recovery\acd019e9-60dd-11e2-a720-a432d392ac
08\Winre.wim,{acd019ea-60dd-11e2-a720-a432d392ac08}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\acd019e9-60dd-11e2-a720-a432d392ac
08\Winre.wim,{acd019ea-60dd-11e2-a720-a432d392ac08}
systemroot \windows
nx OptIn
winpe Yes
Cargador de arranque de Windows
-----------------------------
Identificador {current}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 8
locale es-ES
inherit {bootloadersettings}
integrityservices Enable
recoveryenabled No
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {acd019eb-60dd-11e2-a720-a432d392ac08}
nx OptIn
bootmenupolicy Standard
Reanudar tras hibernación
-------------------------
Identificador {acd019e7-60dd-11e2-a720-a432d392ac08}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale es-ES
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No
Reanudar tras hibernación
-------------------------
Identificador {acd019eb-60dd-11e2-a720-a432d392ac08}
device partition=C:
path \WINDOWS\system32\winresume.exe
description Windows Resume Application
locale es-ES
inherit {resumeloadersettings}
recoveryenabled No
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
pae Yes
debugoptionenabled No
Herramienta de comprobación de memoria de Windows
-------------------------------------------------
Identificador {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Herramienta de diagnóstico de memoria de Windows
locale es-ES
inherit {globalsettings}
badmemoryaccess Yes
Configuración de EMS
--------------------
Identificador {emssettings}
bootems No
Configuración del depurador
---------------------------
Identificador {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
Defectos de RAM
---------------
Identificador {badmemory}
Configuración global
--------------------
Identificador {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Configuración del cargador de arranque
------------------------------------
Identificador {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Configuración de hipervisor
-------------------
Identificador {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Reanudar la configuración del cargador
--------------------------------------
Identificador {resumeloadersettings}
inherit {globalsettings}
Opciones de dispositivo
-----------------------
Identificador {acd019ea-60dd-11e2-a720-a432d392ac08}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\acd019e9-60dd-11e2-a720-a432d392ac08\boot.sdi
C:\WINDOWS\system32>
----
Thank you, very much.
amnenia amnenia:
When you installed Windows 8, the installer created its own recovery folder, located at C:\Recovery. The BCD created by the Windows 8 installer had no idea that there was a separate recovery partition because it wasn't present when Windows was installed.
Does your factory recovery partition currently have a drive letter assigned? If not, assign a temporary one using Windows Disk Management. If so, use the current drive letter to list the contents of the BCD located on the recovery partition. There may be enough information in the old BCD to enable the recovery partition in the new BCD. If the recovery partition's drive letter is X, for example, then use the following command:
bcdedit /store X:\boot\bcd /enum all > %userprofile%\Desktop\oldbcd.txt
Replace "X" in the above command with the correct drive letter. Run the command from an administrative command prompt. It will create a text file on your desktop listing the contents of the recovery partition's BCD.
Hi! Thank you very much!!
I did what you say but, what must I do now?
Could you attach a copy of the old bcd file to your next reply?
Sure, there is it
I don't think that I can help you set this up to work the way it used to. Each PC manufacturer has different ways of setting up a recovery partition, and I'm not familiar with them all. Please consult a user forum for your PC for help with doing this.
OK, thank you anyway..
Can't anyone else help me, please?
Hi Mark, hi everybody
Would you mind to give me a clue about how could I fix this issue, please? I can't find anyone else who can help me. I just found several tutorials to apply a .wim image from de recovery partition to the primary partition, but my partition table is completely unstructured and if the recovery software doesn't boot I don't know what to do... The only help I've found is in english language (no problem for the rest) but everyone who reply my questions in spanish tells me there is no way to fix this trouble, I should format the hard drive... Am I asking too much? I'm just looking for a little directive or clue wich allows me to give one more step to the solution.
Thanks for your help.
Best wishes.
amnea amnea:
Windows 8 has its own recovery method built in. In looking at the BCD on your recovery partition, it looks like all it does is run the Windows installer to reinstall Windows. Since you already did that, what do you need the recovery partition for? What does the recovery partition do differently than what you already did by reinstalling Windows?
You can access all of the built-in recovery features of Windows 8 by several methods. From the Charms bar choose "Settings" and at the bottom of the list choose "Change PC Settings", then choose "General", and then scroll to the bottom of the list of settings to access one of three choices for recovery - "Refresh your PC without affecting your files", "Remove everything and reinstall Windows", or "Advanced Startup".
Another way to reach these choices is from the Desktop. Open the Control Panel and choose "Recovery", then click on the link "If you're experiencing problems with your PC you can refresh it in PC settings", which will lead to the same three recovery methods.
What I'm trying to understand is what the recovery partition has to offer that is any different from the recovery options that are built in to Windows 8.
Mark Wharton,
Since you seem to be the resident hero in this forum, I wonder if I could ask you for advice with my issue? I tried to follow your instructions, but found that bcdedit /enum reported that
"the boot configuration data store could not be opened.
the requested system device could not be found"
I tried other other bcdedit options and nothing.
When I boot my Win7Ultimate 64K PC after uninstalling Acronis, I get the error that No Configuration file could be found.
Windows Repair doesn't work, fdisk doesn't work, but at the command prompt, I can access the volume using the D: letter assignment, so the data is fine, it just won't load.
Please tell me you know some secret byte or two to push around to solve this. Thanks for your help,
jase
Jason:
1. Where do you see the error "No Configuration file could be found"? Before Windows boots or after? Is it a Windows error message in a dialog box or is it pre-boot on a text screen?
2. Does your PC eventually boot into Windows?
3. If it does not boot into Windows, have you tried running Windows Repair at least 3 times? Multiple passes are sometimes needed if several boot issues are present. The automatic repair seems to fix only one problem at a time.
Mark, thanks for your reply...
1. After my BIOS POSTS, the "Loading Operating System" text displays and then immediately the message shows up saying that no configuration file could be located. This is before Windows loads, right away.
2. My PC will not boot from that disk, period. Though it is accessible when mounted as a non-bootable disk.
3. I have tried the disk repair no less than a dozen times. I have tried it by booting from CD, from USB Stick, and even an external eSata hard drive and on every occurrence, I get the same issue: It quits almost immediately and says it can't be repaired, and can it report this error to Microsoft. (which is real funny considering the machine can't boot)
I have tried BCDEDIT with the /enum flag---can't access the BCDstore
I have tried BCDEDIT with the /createstore flag and was able to create a new BCDstrore on the boot drive
I have tried BootRec /fixmbr - it says it is fixed the mbr
I have tried BootRec /fixboot same thing.
but
BootRec /rebuildBCDstore* It enumerates all the existing windows installs and says that it is going to add all of these to the BCDStore right before it returns the error that it can't access the drive *(I'm not sure what the exact flag was, but i got it from the help to be sure it was correct)
Then I realized that the C: drive was actually the 100mb System Partition and not my boot volume. So needless to say, it wasn't going to have the necessary loader to do anything. So I booted into regular windows 7 from my RAID and unassigned the drive letter to the system reserved partition and tried it all again--no luck.
Upon further inspection of the C: drive (my supposed boot vol), I noticed that the BootWiz and Boot directories were missing. Also there was no apparent loader on the drive. So following a technet post about copying bootmgr to the drive, I copies the Boot directory and the bootmgr application. Restarted and this time got a slightly different error.
It says that it cannot access the bcdstore and to do a startup replair. Which is square one and doesn't help.
I'm really at wits end. Please tell me you have an idea how I can repair the boot sectors on this disk... thanks for the reply,
jase
Jason:
I will try to help but right now I'm puzzled by the error messages that you are seeing. They aren't Windows error messages, so where are they coming from? Could you answer the following questions in an effort to shed some more light on your problem?
1. Precisely what did you do immediately before you saw this problem appear? In your first post you mention that you "uninstalled Acronis". Which Acronis program? True Image or Disk Director? Which version?
2. In your second post you mention "Bootwiz". Are you or were you using Acronis OS Selector?
3. How many disks are on your system? How many partitions on each disk? What is on each partition? If you can boot this PC from any version of Windows, then please post a screenshot from Windows Disk Management showing the disk layout for each disk. That will be most helpful in trying to figure this out.
Bootwiz was a hidden folder in older versions of Acronis (not sure if it is still used by 2013), and was used for the F11 Acronis Startup Recovery Manager. It is possible that the Acronis Startup Recovery Manager was not de-activated on the system prior to un-install of Acronis True Image, and the deletion of the bootwiz folder and removal of True Image is causing this error message because the Startup Recovery Manager changes to the boot sector were still in place when rebooting to Windows.
Update:
bootwiz folder is still used by Acronis 2013 when activating the Startup Recovery Manager. Attached is the contents of the folder when ASRM is enabled. When ARSM is disabled, the folder remains, but is empty.
James:
True, but Jason did replace the MBR by using bootrec /FixMbr, assuming that the command was targeted to the correct disk. That SHOULD have removed the boot code used by the Acronis ASRM and replaced it with the Windows 7 native boot code.
Upon re-reading Jason's posts and reading between the lines, the /boot directory and bootmgr file and bcd are probably missing from the System Reserved partition (it looks like he copied them to the Windows partition) and the Active flag may be set on the wrong partition, although you would think that the Windows automatic repair could have figured that out.
With multiple disks (and perhaps multiple operating systems on the disks) it may be more involved than what we think, so we should wait for his reply to shed some more light on the problem.
Hi Mark,
I know you must be tired of helping everyone with their Windows Boot Manager issues but I'm also having the same problem as some of the previous posters. I tried myself in guidance you provided earlier but FAIL. I have a Dell N5010 window 7 home 64-bit laptop that I'm trying to restore to the factory state by using F8, but when I select F8 and choose repair your computer option the PC just boots to Windows normally. When i try to use the USB recovery disk it gives me the winload.exe error.
I would REALLY appreciate any help you can provide on helping me repair the Boot Manager files. I have attached the output to the "bcdedit /enum all" file to this post along with a screenshot of the Windows Disk Manager.
Thanks a lot for any help you can provide!!!
Hi Mark,
I know you must be tired of helping everyone with their Windows Boot Manager issues but I'm also having the same problem as some of the previous posters. I tried myself in guidance you provided earlier but FAIL. I have a Dell N5010 window 7 home 64-bit laptop that I'm trying to restore to the factory state by using F8, but when I select F8 and choose repair your computer option the PC just boots to Windows normally. When i try to use the USB recovery disk it gives me the winload.exe error.
I would REALLY appreciate any help you can provide on helping me repair the Boot Manager files. I have attached the output to the "bcdedit /enum all" file to this post along with a screenshot of the Windows Disk Manager.
Thanks a lot for any help you can provide!!!
Bill:
One issue is that the recoverysequence pointer in the second Windows Bootloader entry (the one that boots Windows 7) is pointing to the wrong location. It's pointing to the first Windows Bootloader entry in your BCD when it should be pointing to the third entry (the one that boots the recovery environment). To fix you can enter the following command into an elevated command prompt window:
bcdedit /set {current} recoverysequence {6abef737-3411-11de-8ea8-ac010edf8f1e}
This should fix the problem of starting the recovery environment.
What I'm really puzzled by is that the first entry in the BCD, Windows Boot Manager, is set to look for the file bootmgr on the C: (Windows) partition, when the file is on the active partition on your disk, partition #2, the Recovery partition. So I don't understand why your PC boots at all.
Let's ignore that issue for the moment and see if the above change allows you to enter the recovery environment. If it does and you're successful in restoring to factory state, then post a copy of the BCD afterwards and I'll take another look.
Hi Marks thanx for quick response. I tried that command and its applied successfully. Then i restart the computer and go into the Advance options and try the computer repair. When i press the enter and a window comes "Loading files" like that thats mean its trying to go into recovery mode but after that normal windows starts. I also try again with the USB but the problem is still same winload.exe.
The new BCD file is attached for your further guidance.
Bill:
Then there must be something missing or damaged on the recovery partition that's preventing the recovery environment from starting. The BCD entry is correct since the files start to load. Let's instead see if we can get your USB flash drive to work.
Could you post a copy of the BCD on the flash drive? First use Windows Explorer to locate the BCD on the F: partition. You will have to enable display of both hidden and system files in order to find it. It's probably at F:\boot\bcd. If so, enter the following command in an elevated command prompt window, but substitute the correct path to the file if the BCD is in a different location:
bcdedit /store F:\boot\bcd /enum all > %userprofile%\Desktop\bcd3.txt
This command should place a copy of the flash drive's BCD on your desktop in a text file. Attach it to your next reply.
Here is the bcdedit file out from USB.
Here is the bcdedit file out from USB.