Windows 7, "Repair your computer" F8 boot option not working (SOLVED)
Cristina:
The chkdsk results indicate that no errors or bad sectors were found.
I thought of one additional check that you could perform. The recovery CD contains the Windows System File checker, sfc.exe, that can check the integrity of the system files that Windows uses. If one of these files was corrupted by a virus then this tool may be able to replace the infected file with a good file. For instructions, see Method 2 here: http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-pro… Pay close attention to the drive letters indicated for your system by DISKPART, as the article explains.
If that doesn't work you may want to consider a repair install of Windows. Here is an article on how to do this: http://www.sevenforums.com/tutorials/3413-repair-install.html
Hi Mark,
Thanks so much for all your help, I really appreciate the time you dedicated to it. Just for some closure, I ran memcheck86+ for 12 hours and after 18 passes there was no problem. I also tried to boot the computer with one memory card at a time, still with no success. Convinced it was still the virus that I either could not remove properly or that had already caused damage before being removed, and having the confirmation that the virus that last attacked my computer was the trojan Sirefef, I googled the case, and I'm now getting help from a Malware Response Team in another forum. (So far, after running Farbar Recovery Tool as suggested, the results were that my services.exe is missing, typical deletion from Sirefef.)
So for everyone else having this problem, "Sirefef won't let me boot my computer", and for the Acronis MVP Volunteers interested in learning more, I leave you the link.
http://www.bleepingcomputer.com/forums/t/496069/sirefef-trojan-wont-let…
Thanks again for the lovely help!
Cristina
Hi Mark,
As many others seem to have experienced, I am unable to utilize the f8 option to perform a full system recovery. After reading multiple previous posts, I have my BCD output listed below. Your assistance would greatly be appreciated!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {c63482df-24b4-11e0-9916-eacf8e99bd62}
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}
recoverysequence {c63482e1-24b4-11e0-9916-eacf8e99bd62}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {c63482df-24b4-11e0-9916-eacf8e99bd62}
nx OptIn
Windows Boot Loader
-------------------
identifier {c63482e1-24b4-11e0-9916-eacf8e99bd62}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{c63482e2-24b4-11e0-9916-eacf8e99bd62}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{c63482e2-24b4-11e0-9916-eacf8e99bd62}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {c63482df-24b4-11e0-9916-eacf8e99bd62}
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\HarddiskVolume2
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
EMS Settings
------------
identifier {emssettings}
custom:26000022 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}
Device options
--------------
identifier {c63482e2-24b4-11e0-9916-eacf8e99bd62}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi
C:\Windows\system32>
Thank you in advance!
Kierstan O. (Kay-Dee)
hi mark, i was having the same annoying problem and booting from a win 7 dvd to do a repair install would not work etheir.
I desperately need to perform a repair as there are some corrupt system files detected by sfc which cannot be repaired and i figured a system repair is the only way.
this is my bcd output:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=G:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {6a293fa4-03bb-11df-aa54-b82a7678fcaf}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 0
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {456dd2b8-b7a1-11e1-9672-edfd971d8466}
device unknown
path \Windows\system32\winload.exe
description Windows 7 Ultimate (recovered)
locale en-US
osdevice unknown
systemroot \Windows
resumeobject {49ad4f25-b71b-11e1-bf94-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {456dd2b9-b7a1-11e1-9672-edfd971d8466}
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Ultimate
locale en-US
recoverysequence {456dd2b9-b7a1-11e1-9672-edfd971d8466}
recoveryenabled Yes
testsigning No
osdevice partition=C:
systemroot \Windows
resumeobject {b216c0be-b755-11e1-a455-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {456dd2bc-b7a1-11e1-9672-edfd971d8466}
device ramdisk=[C:]\Recovery\6a293fa6-03bb-11df-aa54-b82a7678fcaf\Winre.wim,{456dd2bd-b7a1-11e1-9672-edfd971d8466}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\6a293fa6-03bb-11df-aa54-b82a7678fcaf\Winre.wim,{456dd2bd-b7a1-11e1-9672-edfd971d8466}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {6a293fa5-03bb-11df-aa54-b82a7678fcaf}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {6a293fa6-03bb-11df-aa54-b82a7678fcaf}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {6a293fa4-03bb-11df-aa54-b82a7678fcaf}
nx OptIn
Windows Boot Loader
-------------------
identifier {6a293fa6-03bb-11df-aa54-b82a7678fcaf}
Resume from Hibernate
---------------------
identifier {49ad4f25-b71b-11e1-bf94-806e6f6e6963}
device unknown
path \Windows\system32\winresume.exe
description Windows 7 Ultimate (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {6a293fa4-03bb-11df-aa54-b82a7678fcaf}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No
Resume from Hibernate
---------------------
identifier {b216c0be-b755-11e1-a455-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Ultimate (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=G:
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}
Device options
--------------
identifier {456dd2ba-b7a1-11e1-9672-edfd971d8466}
ramdisksdidevice unknown
ramdisksdipath \Recovery\6a293fa6-03bb-11df-aa54-b82a7678fcaf\boot.sdi
Device options
--------------
identifier {456dd2bd-b7a1-11e1-9672-edfd971d8466}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\6a293fa6-03bb-11df-aa54-b82a7678fcaf\boot.sdi
Device options
--------------
identifier {6a293fa7-03bb-11df-aa54-b82a7678fcaf}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\6a293fa6-03bb-11df-aa54-b82a7678fcaf\boot.sdi
Kierstan:
I don't see anything wrong with your BCD; it appears to be set up correctly. Doing a full system recovery is dependent on how your PC manufacturer set that up. I would suggest that you contact them directly or visit their user forum for help.
Thank you Mark, I tried to do a full system recovery with the f8, but when it shows the "windows is loading files" screen, the bar fills and stays there. It doesn't proceeds any further. Im wondering if I may have to re-install the OS.
Kierstan:
Either something is wrong with your recovery partition or else it's a hardware problem. You could try running MemTest or the Windows memory test to rule out bad RAM. Otherwise, you may need to see if your PC manufacturer makes available a recovery DVD that can restore the PC to factory state if the recovery partition is unable to do so.
Thanks for the rapid replies :)
Its a Dell Inspiron laptop, so I created the recovery disc from the Dell Data Safe 2.0. Is that what you are referring to? Iam going to perform the MemTest right now.
Rende:
The recoverysequence value in the main Windows Boot Loader entry is incorrect. To fix, enter the following in an elevated command prompt window:
bcdedit /set {current} recoverysequence {456dd2bc-b7a1-11e1-9672-edfd971d8466}
Also, the resumeobject value in the Windows Boot Manager entry is incorrect:
bcdedit /set {bootmgr} resumeobject {b216c0be-b755-11e1-a455-806e6f6e6963}
The following entries are all invalid and can be deleted:
bcdedit /delete {456dd2b8-b7a1-11e1-9672-edfd971d8466}
bcdedit /delete {456dd2b9-b7a1-11e1-9672-edfd971d8466}
bcdedit /delete {6a293fa5-03bb-11df-aa54-b82a7678fcaf}
bcdedit /delete {6a293fa6-03bb-11df-aa54-b82a7678fcaf}
bcdedit /delete {49ad4f25-b71b-11e1-bf94-806e6f6e6963}
bcdedit /delete {6a293fa4-03bb-11df-aa54-b82a7678fcaf}
bcdedit /delete {456dd2ba-b7a1-11e1-9672-edfd971d8466}
bcdedit /delete {6a293fa7-03bb-11df-aa54-b82a7678fcaf}
Kierstan:
I'm not sure how Dell handles their recovery function; everybody does this somewhat differently. You'd be best advised to visit a Dell forum for help.
Will do, thank you again for assisting me Mark :)
Its a Dell Inspiron laptop, so I created the recovery disc from the Dell Data Safe 2.0. Is that what you are referring to?
Yes. I would expect it to be more than a single disk, though. I used Dell DataSafe to create Recovery Discs. This burned to three DVD+R disks, or to a 16 GB flash drive.
Restoring that would return the laptop to factory state, exactly how you received it from Dell before its first boot. If you have any user data you need to save, you must do that before restoring, as anything on the drive would be lost during the restore process.
thanks for the assistance, mark
Hello
I am having booting problem.I can't even start windows (7).it started when i created another partiition because i wanted dual boot with windows xp. i did it without the disc or usb i just used bcd but i am a newbie so i think i screwed up somewhere acctually i am not even sure what i did at all... and now my windows wont start, i get a windows boot manager error, i can't see entry menu where i could chose between windows xp or 7.
i dont have a windows 7 cd, my sister moved to another city and it was hers, i could ask her but it would take like a week.
is there anythinh i could do? or is it screwed up now?
thats the error...
the windows boot configuration data file does not contain a valid os entry
not sure if it's even legal to download xp like that but i am just a kid.....hope you can help me or understand my problem, i did not write detailz about that, btw cant get to safe mod.. tried f8
thanks...
Marten,
See if you can find someone who will make you a Windows 7 recovery CD, this might help (I don't think it will solve the problem completely) it will allow you to get to utilities that can remake the BCD.
Can you think and give a rough idea of how you tried to add XP to your boot menu?
Was Windows 7 booting correctly beforehand?
Which was the original OS XP or W7?
as i said i am a kid, so i like playing games and so on. my win 7 was running just fine but my pc isn't the best. So my friend told me that win xp requires less and has higher performance. and my original os was 7. well the pc came with vista but it was like 6 years ago and i have changed OS quite a lot so i dont think that matters.
i'll try to explain how i tried to dual boot.
well i started with installing easybcd then i downloaded xp from thepiratebay i tried to run it but the install button was like forbitten cause i think i needed to burn it on cd. well thats where i used easybcd i made xpinstall.exe and renamed it to .iso that might be wrong but yeah i tried it, anyways next i used easybcd and chose something called ISO. and i cant really remember what next, I pressed something and thought that it worked and restarted my pc and that happend..i know i did it wrong ...
and i have a laptop do, so i could buy an empty cd, depends how much they cost
now i have another question. Can i burn xp on that cd and use that or i am.going to need to burn win7 on it? and how big the size of the cd has to be? like how much space it needs?
sry about my english, not my main language..
thanks.
i mean is 700mb cd enough for xp or win7 and please tell me if i can use xp cd or do i have to use win7 still, because i'd like to have xp
i found win7 disc but it wont load.. tried to change booting devices but nothing happens...it just wont load. please help me..
i found win7 disc but it wont load.. tried to change booting devices but nothing happens...it just wont load. please help me..
btw.i.am ready to delete my os if it's poaaible. all i can really use is bios.
EDIT: oh you said recovery cd...aahh i missed that but how much space cd needs to burn that recovery thing to it
nvm
Marten,
I think you'll find the easiest thing to do will be to wipe the hard drive and start again, but if you want to avoid that, there area number of steps you will need to take before there is any chance of recovering your current system.
Do you actually have a copy of True Image? The first thing will be to make a complete disk image of your system to another hard drive.
When you try to boot your PC exactly what happens, how far into the boot process does it get, do you get as far as the boot manager trying to display items?
Apart from maing the XP into an ISO, there is a problem that your copy of XP from where you downloaded it might not be a true XP install file, it could contain viruses or have been altered so that you aren't dealing with software that will ebhave as you think.
Once you have this all sorted out, there is a copy of XP for Virtual PC that you can download free from Microsfot themselves, this runs as a virtual machine in Windows 7. If you are running windows 7 Ultimate, there is a further option which can be explored as far as running XP is concerned.
i'd go with the easiest thin but that does not seem easy to me..
when i am starting the pc it'll go through the section where you can run bios.
then it gets to the section where you can see memory and things, and where it's suppous to boot from cd or dvd. it does say it if i entered the cd but it wont load, next thing that happens is just that screen with the error.
Oh and how can i clean up my hard drive without OS and without windows cd loading.
and if i do clean it, then i can install new windows?
i'd go with the easiest thin but that does not seem easy to me..
when i am starting the pc it'll go through the section where you can run bios.
then it gets to the section where you can see memory and things, and where it's suppous to boot from cd or dvd. it does say it if i entered the cd but it wont load, next thing that happens is just that screen with the error.
Oh and how can i clean up my hard drive without OS and without windows cd loading.
and if i do clean it, then i can install new windows?
i'd go with the easiest thin but that does not seem easy to me..
when i am starting the pc it'll go through the section where you can run bios.
then it gets to the section where you can see memory and things, and where it's suppous to boot from cd or dvd. it does say it if i entered the cd but it wont load, next thing that happens is just that screen with the error.
Oh and how can i clean up my hard drive without OS and without windows cd loading.
and if i do clean it, then i can install new windows?
wth... i m sorry if there is multiple posts, its cause i am using my phone and it's like doing multiple posts i think
Marten,
You do realise that the easiest option means everything on your hard drive will be deleted, you will have no way of getting any of your programs or data in either XP or Windows 7.
Before you do anything, if you have a purchased True Image, make a complete disk image to another hard drive, you will need to use the True Image recovery CD to boot from in order to do this, or temporarily remove the hard drive from your PC attach it to a USB hard drive case and image it from a machine in Windows that is working. If you don't have True Image at the moment, then obviously you can't do this. You can download the trial version, however the Windows version will only work for 30 days and the recovery CD can only recover images.
Is your Windows 7 DVD a proper Windows 7 DVD, not one downloaded from a non Microsoft website? I ask because from what you say there seems to be a problem with the DVD if it won't allow you to boot from it.
Make sure your in your BIOS you have set the CD/DVD as the first boot item, also if your BIOS has the option make sure it has the highest priority. Depending on the make of your PC there are variosu ways of entering the BIOS, the most common are pressing the DEL key or F1 just after the BIOS post check finishes. The BIOS post check is th eone where it tells you the name of the BIOS, the processor and you'll see the RAM check running. You press whichever key or combination is required as soon as the RAM stops counting and says OK. IF you don't see the post, but just have a splash screen come up, you need to be pressing whichever button you need very quickly throughout the booting.
Check your Windows 7 DVD in another computer, if it boots to the windows asking for keyboard details, your DVD is OK and you cna just remove the DVD form the PC and switch the PC off, no files on your PC will have been altered, so, so long as you don't go any further than that you will be OK.
Mark, I am new to using this blog. As a fellow HAM (N2BGR) maybe you can answer a simple question for me, since I have no way of getting Acronis Tech support( my product is too old). I have a full backup of my Win7 64bit system ( I do not use the incremental or differential backup types, only full) on an external HDD created with TI 2010. I just purchased TI 2013 for the same system. My question: If I needed to restore my system from the TI 2010 backup using TI 2013 will I run into any roadblocks, compatibility wise? Or Would you advise rather, that I just upgrade to TI 2013 first, and then create a new backup (I would have to delete the older backup due to limited HDD space).
73. Bill
ATI 2013 can restore images made with ATI 2010, and many earlier versions as well.
Bill,
You really need to invest in another external hard drive to store more backups. Having only one backup is living dangerous with your data. AS a senior citizen myself, I know how tight money can be but if you are gong to mess with compuers, you need to bite the bullet and spend $80-$100 so you have more storage space.
Once you have the new disk, then before you do install or uninstall anything. Download the 2013 ISO file from your registered account and create a new 2013 TI Recovery CD. Use the new CD to make a full and complete backup of your current system (checkmark the disk option as to what is to be included within the new backup) when booted from the 2013 Recivery CD.
Just a note. Before you can install 2013, you will need to un-install 2010 plus run the cleanup utility (link below) and I want to be sure you have a new current backup before you proceed with any uninstall-cleanup-reinstall procedure.
Bill:
To add to tuttle's comment, Acronis designs their software to be backwards compatible, so the latest version should work with backups made with older versions.
However, I have another suggestion for you, and that is to give some consideration to the hazards of having only one backup. It's like having all of your eggs in one basket. With external hard disk prices fairly low, you should invest in one that is large enough to store several backups. If you really want to add an extra layer of protection against fire, flood, wind, etc., rotate your backups between your existing storage disk and the new one, and keep one of them at a different physical location like at your office or a trusted friend or relative's house.
*edit* I see that Grover and I doubled (hams understand what this means). But you should consider what both of us are recommending.
Mark, I solved my second backup situation. I had completely forgotten that I had a second, un cabled up, HDD (same make and model) sitting in my computer case. I cleaned up, checked for errors and defragged my C: drive then cloned the second drive with ATI 2010. I also did a complete FULL backup onto my ext backup drive. I'm now ready to uninstall ATI 2010. I have to answer GroveH's message now.73
Mark, I solved my second backup situation. I had completely forgotten that I had a second, un cabled up, HDD (same make and model) sitting in my computer case. I cleaned up, checked for errors and defragged my C: drive then cloned the second drive with ATI 2010. I also did a complete FULL backup onto my ext backup drive. I'm now ready to uninstall ATI 2010. I have to answer GroveH's message now.73
GroverH, I just posted a message to Mark in which I said " Mark, I solved my second backup situation. I had completely forgotten that I had a second, un cabled up, HDD (same make and model) sitting in my computer case. I cleaned up, checked for errors and defragged my C: drive then cloned the second drive with ATI 2010, then disconnected it from the system. I also did a complete FULL backup onto my ext backup drive. I'm now ready to uninstall ATI 2010." So this is directed to you. "Before you uninstall and install, download the 2013 ISO file from your registered account and create a new 2013 TI Recovery CD" Don't I need to install ATI 2013 to get access to the 2013 ISO image? "Before you can install 2013, you will need to un-install 2010 plus run the cleanup utility (link below)"........ I don't see the cleanup utility link.
Bill,
Acronis Cleaner, see item #4 in Grover's signature in post #478 above.
You can download the recovery ISO and burn it to a CD from your Acronis account.
Thank you Colin.
Bill,
Once you register your 2013 serial number (64 dharactes) with Acronis, the ISO file will be available in your account for download and burning as a True Image Recovery CD. Once this file is burnt as a CD, it will be identical as if it were created after a complete install of 2013.
After burning, you should be able to boot from the new CD and create a complete backup
I've been having a problem lately with bsod's involving hal.dll and ntoskrnl.exe, but it shows them as caused by hal.dll. I performed memtest on my memory and got the software from my hard drive manufacturer's site to check the hard drive but no problems were shown on either. Next i tried to use system recovery from the windows disc, but it says "This version of System Recovery Options is not compatible with the version of Windows you are trying to repair". I then made a recovery disc with the windows 7 disc and had the same result. Do i need to use system recovery to fix the hal.dll problem or is there another way, and if i do need to use the system recovery, how would i access it if i can't use the win7 disc or the recovery disc?
Any suggestions would be helpful.
Jimmy:
The error message that you're receiving from the Windows DVD and the recovery CD sometimes appears in PCs with multiple hard drives. Windows recovery expects to find an installation of Windows on the hard disk enumerated as disk 0 by the BIOS. Try disconnecting every hard disk except the one with Windows installed on it, and make sure that the BIOS is set to boot from this disk. Then try running system recovery again.
Hi Mark,
I was wondering if you could help me with a problem. My BOOTMGR seems to have gone missing. So I've been trying every solution I could find on the Internet to no avail, plus it seems when I boot up on my Windows 7 disk and go to Repair your computer, select my installed windows and click next I get a compatibility error. Now I tried following your instructions at the beginning of this thread but I came to a wall when I typed in bcdedit /enum all /v I only got the following:
Windows Boot Manager
Identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
default {0d25ecb7-e434-11e2-8241-9e4d18f42dd1}
displayorder {0d25ecb7-e434-11e2-8241-9e4d18f42dd1}
bootsequence {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30
Windows Boot Loader
identifier {0d25ecb7-e434-11e2-8241-9e4d18f42dd1}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Ultimate
locale en-US
osdevice partition=C:
systemroot \Windows
Windows Memory Tester
identifier {b2721d73-1db4-4c62-bf78-c548a880142d}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
And that's all there was, which is odd because every other post has a lot more.
My Recovery folder has the following folder in it: {958e4c43-8c7c-11e0-bdb6-b6a36efb18dc}
That string doesn't match up with any of the others.
Anything you could advice to help will be much appreciated!!
Mark:
You have your system configured to do a Windows memory test the next time it boots. Perhaps this is why the command "/enum all" only lists three entries; the last of which is the Memory Tester. Try removing the one-time boot sequence with the following command:
bcdedit /deletevalue {bootmgr} bootsequence
Then try listing the BCD contents again:
bcdedit /enum all
(don't add the /v modifier)
Error messages about BOOTMGR being missing are often caused by having the wrong partition marked as active. From a command prompt in the recovery environment, use DISKPART to determine which partitions are on your disk(s) and which are active:
DISKPART
Select Disk 0
Detail Disk
Could you post the output of the last command (Detail Disk)?
Hi Mark,
Thanks for the quick reply. I've attached a picture of the Detail Disk, as I'm typing on an iPad which makes things difficult, hehe.
I tried deleting the value but still go the same 3 results. I've attached a pic for that too.
Hi Mark,
Ok I managed to fix it. It was because of an active partition thing. I didn't know that System Reserved needed to be active, I was trying to make C: drive active....
Sigh, it's the simple things that catch you.
Thanks for the Help!!
Mark:
Does the BCD now contain more than three entries? In other words, does it look normal now?
Yes, it seems to be normal now :)
Thanks!
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {958e4c41-8c7c-11e0-bdb6-b6a36efb18dc}
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}
recoverysequence {958e4c43-8c7c-11e0-bdb6-b6a36efb18dc}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {958e4c41-8c7c-11e0-bdb6-b6a36efb18dc}
nx OptIn
Windows Boot Loader
-------------------
identifier {958e4c43-8c7c-11e0-bdb6-b6a36efb18dc}
device ramdisk=[C:]\Recovery\958e4c43-8c7c-11e0-bdb6-b6a36efb18dc\Winre.wim,{958e4c44-8c7c-11e0-bdb6-b6a36efb18dc}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\958e4c43-8c7c-11e0-bdb6-b6a36efb18dc\Winre.wim,{958e4c44-8c7c-11e0-bdb6-b6a36efb18dc}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {958e4c41-8c7c-11e0-bdb6-b6a36efb18dc}
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}
Device options
--------------
identifier {958e4c44-8c7c-11e0-bdb6-b6a36efb18dc}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\958e4c43-8c7c-11e0-bdb6-b6a36efb18dc\boot.sdi
Hi Mark Wharton, please help me. Quick run down on how I got here -- I have a Dell laptop and was able to restore it to factory image. Then, I updated all the drivers and created a new image on my external hard drive. Finally, as I move old files and install more updates, I decide to revert back to the new image that I saved on the external hard drive. This is when I discover that my system won't go into "repair your computer" and boots up Windows normally. My computer works fine but I really would like to figure this out. I have included the output response, disk management snapshot, directory structure, and recovery folder content.
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {d537af28-d339-11e0-b285-14feb5c3ae08}
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}
recoverysequence {f45283b3-e8f4-11e2-a7d7-14feb5c3ae08}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {d537af28-d339-11e0-b285-14feb5c3ae08}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures
Windows Boot Loader
-------------------
identifier {f45283b2-e8f4-11e2-a7d7-14feb5c3ae08}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{f45283b3-e8f4-11e2-a7d7-14feb5c3ae08}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{f45283b3-e8f4-11e2-a7d7-14feb5c3ae08}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {d537af28-d339-11e0-b285-14feb5c3ae08}
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\HarddiskVolume2
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}
Device options
--------------
identifier {f45283b3-e8f4-11e2-a7d7-14feb5c3ae08}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi
By the way: I created a system repair disc and tried to boot up with it, computer goes into the screen where I'd normally log in and idles. Mouse cursor appears and nothing else.
Mike:
The recoverysequence value is incorrect. Enter the following in an elevated command prompt window:
bcdedit /set {current} recoverysequence {f45283b2-e8f4-11e2-a7d7-14feb5c3ae08}
Hello.
I really hope some moderator can see this and sort this out. It's been over a month now that I have untoggled every possible way of getting replies to this topic. I even took the trouble to find in the forum a thread about how to be removed from the Acronis database, asking to have my email removed as we are not able to do it as users (?!?).
And yet I keep receiving replies to this thread. I hope I am not doomed to it forever
Seriously, could a moderator permanently wipe my registration data fon this forum? It would be very much appreciated.
Kind regards,
Cristina Lr
Thanks Mark! Reformatting as I type :)
Unfortunately, it didn't recognize the Windows image that I had saved earlier on the external drive, the folder and the subfolder wouldn't light up "next" to continue. Will re-update all the drivers again after factory image completes.
Much thanks!
Mike
Christina Lr,
http://forum.acronis.com/forum/6758?page=9#comment-135348
Yes, that can be a pain.
I read where you have tried this before but try one more time.
You can usually fix that yourself by edting your last post of any or your postings in this thread.
Click the edit button at the bottom of your last post.
Then note at the very bottom, uncheck the option to received notices.
This option is just above the save/preview button.
If this does not work, try going into your personal account "my account" /edit and change the settings to received notices from this forum.
Mark and staff-
Thank you for the wonderful work you have done here. Can I please get the correct items to run against my system? My F8 key also does not work, I got the settings from a install CD:
Windows Boot Manager
--------------------
identifier {bootmgr}
device unknown
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {facca3c4-03f1-11e1-8e63-180373c7cff2}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {facca3c6-03f1-11e1-8e63-180373c7cff2}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {facca3c4-03f1-11e1-8e63-180373c7cff2}
nx OptIn
Windows Boot Loader
-------------------
identifier {facca3c6-03f1-11e1-8e63-180373c7cff2}
Resume from Hibernate
---------------------
identifier {facca3c4-03f1-11e1-8e63-180373c7cff2}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device unknown
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}
Device options
--------------
identifier {facca3c7-03f1-11e1-8e63-180373c7cff2}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi
Great thanks to all of you.
Brad:
Please boot again from your Windows 7 install DVD and go to a command prompt window. Type the following three commands, each on its own line:
Diskpart
Select disk 0
Detail disk
Could you post the output from the last (detail disk) command?
Disk ID: D86D5C89
Type : SATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C RECOVERY NTFS Partition 6377 MB Healthy
Volume 2 D OS NTFS Partition 105 GB Healthy
Volume 4 FAT Partition 23 MB Healthy Hidden
Thank You Mark.