Skip to main content

Windows 7, "Repair your computer" F8 boot option not working (SOLVED)

Thread needs solution
Forum Star
Posts: 19
Comments: 2110

#101

Steven:

I only see two places in the BCD that refer to the folder with non-printable characters, and both are in the section that boots to Dell Recovery:

Windows Boot Loader
-------------------
identifier              {62553a77-83ef-11e0-a1fd-b2d5c1bd71e7}
device                  partition=D:
path                    \??????\Windows\system32\boot\winload.exe
description             Windows (TM) Code Name "Longhorn" Preinstallation Environment (recovered)
osdevice                partition=D:
systemroot              \??????\Windows
detecthal               Yes
winpe                   Yes

==========

The non-printable characters refer to this folder on the Recovery partition:

==========

Volume in drive D is RECOVERY
 Volume Serial Number is B6D8-EEB7

 Directory of d:\

09/01/2010  12:25 AM    <DIR>          $AVG
10/01/2010  04:44 AM    <DIR>          $RECYCLE.BIN
09/19/2008  12:51 AM    <DIR>          dell
01/19/2008  11:45 AM    <DIR>          ProgramData
10/04/2010  01:28 PM    <DIR>          RECYCLER
01/29/2008  08:53 PM    <DIR>          sources
10/01/2010  02:03 AM    <DIR>          System Volume Information
11/30/2010  01:08 AM    <DIR>          Tools
10/24/2009  01:23 AM    <DIR>          USB
01/19/2008  11:45 AM    <DIR>          Users
10/02/2010  08:29 PM    <DIR>          ??????
               0 File(s)              0 bytes
              11 Dir(s)   5,478,813,696 bytes free
==========

Since Vista still works and the recovery partition is not hidden, can you explore the contents of the "mystery" folder? I would have suggested listing the directory with dir /a /s but I don't know how you would type the name of the folder. However, maybe Windows Explorer will let you browse it.

If you can view the folder contents then post a screen shot, or if you can figure out a way to list the contents then post the list. Maybe we can figure out what's missing.

Grover's comment is very helpful - if you have an image of the recovery partition then you can browse it and compare it to what's on your recovery partition to find out if anything is missing. If so, restoring the recovery partition would be another way to recover.

Beginner
Posts: 0
Comments: 6

#102

Thanks again for all your help. I figured out a way to view the files in the "hidden" directory and I have attached the output of the "dir /a /s" to this message. Hopefully this will be of some help.

As far as an image of the recovery, unfortunately I don't have anything for this computer. Its a hand-me-down computer my fiancee received from her boss as a present so I really don't have anything more than the laptop itself. As for the recovery disk, I could possibly make one since the computer still boots but I don't know if that will help or not as I don't even know if the current OS install is the original from Dell or if the previous owner had reinstalled at some point.

Hopefully the attached D:\????\Windows file structure will be of help.

Thanks!

Steven

Attachment Size
65908-95650.txt 1.61 MB
Forum Star
Posts: 19
Comments: 2110

#103

Steven:

Does this computer have Norton System Works or Roxio GoBack installed on it?

Beginner
Posts: 0
Comments: 6

#104

I just checked and nothing on the computer from either Norton or Roxio.

Any other thoughts, or should I just plan to reinstall from an OS disk, and hope to track down all the drivers from Dell?

Steven

Forum Star
Posts: 19
Comments: 2110

#105

Steven:

The reason that I asked is that after doing a BING search on the exact STOP error message, I found a bunch of hits that pointed to GoBack as a culprit. Troubleshooting 0x06b stop errors is difficult since there are a number of causes.

In looking through your attachment in reply #102, I can find the files that the BCD is referencing and I don't see anything obvious that would cause the boot process to fail. For certain, the BCD is now correct since the PC does boot into the recovery environment when asked to, but when control is transferred to winload.exe, something goes wrong.

I can only think of one additional thing to try that may be related to the STOP error, and that is to change the mode of the disk controller in the BIOS to IDE, if the BIOS has such a setting. It may be called "IDE Compatibility" or it may be called "AHCI on/off" or something similar. If you find such a setting, and that's a big "IF" with the lack of settings in most Dell BIOSes, then try it to see if this prevents the STOP error from happening.

If that doesn't work then I would either:
a) Try to find a Dell recovery disk that can restore the machine to factory state - either check Dell's web site or search eBay, or:
b) Reinstall Vista from an OS disk. Most of the drivers should automatically install from Windows Update, or:
c) This is a great opportunity to upgrade to Windows 7...

Beginner
Posts: 0
Comments: 6

#106

Hi Mark,
Could you also help me with this problem, I've tried many way to make it work.
My machine is Dell Vostro 3300 with Windows 7 Proff 32 bit OEM.
Problem started when I've restored the backup DVD that I've created when it still OOBE.
The recovery process delete the recovery partition and factory partition, and now I'm about to rebuild this partition, luckily I can get the OOBE image from my backup DVD.
Here is my partition:

Partition 01 : 750 MB Type DE (hidden) contain :
- recovery\windowsre\winre.wim (159 Mb)
- tmp

Partition 02 : 15 Gb Type 27 (hidden) contain:
- DellRestore\factory.wim (OEM factory image)

Partition 03 : 150 Gb Type 07 Drive C: Active contain:
- Windows system

Partition 04 : 300 Gb TYpe 07 Drive D: contain:
- Data

First problem,
- F8 don't have repair your computer menu option, which can get me to the winre boot.

Second problem,
- The DELL Backup & Recovery Management (this is DELL windows application) cannot open, it always said "this system doesn't have Windows Recovery Environment installed", it seem that it cannot see where the Winre file is restored.
I've tried to unhide the Winre partition and then set its path using reagentc command, but
the reagentc also give an error result.

Here is my bcd:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {500efc64-9bdc-11e0-afa7-d7a1a4721697}
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 {500efc64-9bdc-11e0-afa7-d7a1a4721697}
nx OptIn
detecthal Yes

Resume from Hibernate
---------------------
identifier {500efc64-9bdc-11e0-afa7-d7a1a4721697}
device partition=C:
path \windows\system32\winresume.exe
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
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}

many thank's for your help.
Nenda

Attachment Size
68049-96079.txt 2.67 KB
Forum Star
Posts: 19
Comments: 2110

#107

Nenda:

Probably the best source of information about the Dell Utility and Recovery partitions is on Dan Goodell's web site: http://www.goodells.net/dellutility/

Since I don't have any experience working with either of these, I'm not sure that I can be of much help, but I'll try.

First, the Type DE partition is supposed to be a FAT16 partition with the "Type" byte changed to DE in the partition table. Can Windows see this partition if you don't alter the Type byte? Try this -- from Windows Disk Management, right-click on the partition and assign it a drive letter. Does the partition show up in Windows Explorer? Can you see the files? If so, we can probably add info to the BCD that will boot to WinRE.

Beginner
Posts: 0
Comments: 6

#108

Mark:
Thank you for your kind to help me,
As your suggestion about Dan Goodell's, I've already explore it before I post here, that was a very good resources to get to know about Dell recovery partition, however the explanation is more related to WinXp OS, and the image created is using Ghost, while in my case is Win7 and image is using Windows Image (*.wim).

My assumption, the recovery method used here is different with that because when I boot and restore from DVD backup set, it delete all partition and recreate 2 partitions:
1. Partition 01, NTFS type 07 750 Mb with recovery\windowsre\winre.wim
2. Partition 02, NTFS type 07 425 Gb with DellRestore\factory.swm & factory2.swm (split from factory.wim)

But the restore process never successfuly done.
Then I have shrink partition 02 and create partition 03 and 04 for OS and Data, then restore the image manually using imagex.exe to partition 03. When rebooted, the Windows start to configure the system as it the first time setup (OOBE), and it also automatically hide the partition 01 and change the type to DE.

Overall, it succesfully restore my OS as it first time setup. Problem are F8 don't have a repair menu (Winre) and Dell DBRM application cannot work (always said "this systen doesn't have windows recovery environment installed"),

I can change the type of 2 hidden partitions to 07 using Norton Partition Magic Dos (PTEDIT.EXE), however before I change it Norton Partition Magic show warning :
"error 110 has been detected on partition starting at sector 1538048 on disk 1.
The length of the partition in the partition table is incorrect.
The CHS length is 33162352. the LBA length is 33153024, and the File system length is 33153023
Norton Partition Magic has determined that the length can be changed to the correct value of 33162352.
Woul you like to Fix the error?"
I don't know if this info can be usefull, but I've already done previously to choose Yes and No, and nothing fix the problem.

OK, now I have already unhide both partitions, I can see it on Windows.
First Partition Drive S: NTFS 750Mb (recovery\windowsre\Winre.wim)
Second Partition Drive R: NTFS 15 Gb (DellRestored\factory.swm & factory1.swm)
The active partition is the third partition Drive C: (Windows)

Now what should I do next to edit BCD? (attached mybcd2.txt)
Thank you,

Attachment Size
68098-96085.txt 2.67 KB
Forum Star
Posts: 19
Comments: 2110

#109

Nenda BS:

Don't use Partition Magic on Windows 7 created partitions. The program is very old and written before the newer partitioning standards used by Windows Vista and 7 were developed, so it will always think that there are errors in the partition table. But it's OK to use PTEDIT32 to change the partition type in the partition table; that works just fine.

By any chance is there also a C:\Recovery folder? It's a hidden, protected operating system folder so you will need to enable viewing of these file types in Windows Explorer to see it. Standard Windows 7 installations will put WinRE in this folder on the main Windows partition.

We can certainly add entries to the BCD to boot WinRE on the first partition, but I'm not sure how your PC will react if the partition type is set to type DE. Perhaps Dell handles this in the BIOS; I just don't know. I also doubt that I can help with booting to the Dell Restore environment since I don't know how it works.

I'll take a look at the required entries for booting WinRE later this evening and get back to you.

**Edit** Sorry - ran out of evening before I knew it. Will try again in the morning.

Beginner
Posts: 0
Comments: 6

#110

Mark:

My Harddrive now are looks like:
Partition 1 : 750 MB Type 07 NTFS Label SYSTEM: (\recovery\windowsRE\WinRE.wim)
Partition 2 : 15 Gb MB Type 07 NTFS Label RECOVERY: (\DellRestored\factory.wim)
Partition 3 : 150 Gb Type 07 NTFS Label OS: (\Windows)
Partition 4 : 300 GB Type 07 NTFS Label DATA:

Previously, I have tried to make a BCD with Partition 1 (DE) as Active so it will boot from partition1 (DE), and then add it into BCD using Easy BDC. When it boot, it show option:
1. Windows
2. WinRE

If we choose 1. Windows, it will boot to partition 3 and run Windows 7
If we choose 2. WinRE, it will boot to partition 1 and run WinRE

Then we can assume that we can also boot it from DE partition. As for option 2 (WinRE), the WinRE menu is the same like when it booted from DVD backup set (have Dell Image Restore menu).

Everything seem to be enough, but what I want is when it boot, it will directly goto windows 7, and when F8 was triggered, it will go to WinRe.

(By the way, do we need to boot it from partition 1?)

As for DBRM (Dell Backup & Recovery Manager), I found some post in Dell forum that to let DBRM know where is the WinRe path, it should be set using :
- reagentc /setreimage /path S:\recovery\winre /target c:\windows,
and that is always failed,
it always said: cannot create a file when that file already exists.
then i try to disable it first,
- reagentc /disable error: The system cannot find the file specified.

Thanks

attached are
- bcdedit01.txt -> boot from partition 1(DE) - WinRE
- bcdedit03.txt -> boot from partition 3(07) - Windows 7

Attachment Size
68156-96091.txt 4.7 KB
68156-96094.txt 2.67 KB
Forum Star
Posts: 19
Comments: 2110

#111

Nenda:

I was unaware of the REAgentC command-line tool for managing WinRE installations, so thank you for pointing this out. It would seem that I have been doing WinRE recoveries the hard way by manually editing the BCD when a simpler method is available.

As an experiment I tried removing the WinRE information from the BCD (in a Windows 7 VM) and then using REAgentC to restore the entries, and it works. So give this command a try on your system to see if it can set up the F8 boot to WinRE.

For your system I am assuming that you still have the following drive letter assignments for the four partitions:
Partition 1 - S:
Partition 2 - R:
Partition 3 - C:
Partition 4 - D:

While running Windows 7 and from an elevated command prompt enter the following command:

reagentc /enable

Then list the BCD to see if the entries for WinRE are added. For this to work, the file C:\Windows\System32\Recovery\ReAgent.xml must exist and have the correct entries. If the command doesn't correctly add the WinRE entries to the BCD then first run:

reagentc setreimage /path S:\recovery\windowsre\Winre.wim

to tell Windows the location of the F8 recovery image on your first partition, then:

reagentc /enable

List the BCD and if the WinRE entries are present, test the F8 recovery function.

See if this works and then perhaps we use this tool to fix the Dell Restore function. BTW, syntax for REAgentC can be found on TechNet here: http://technet.microsoft.com/en-us/library/dd799242(WS.10).aspx, so it would seem that the info you found on a Dell forum post is using the incorrect syntax for the way your partitions are set up and the drive letters in use, and also is not specifying the /bootkey option to tell the system which F-key is to be used to start the Dell Restore image. The command probably should be something like (for using F11):

reagentc /setosimage /path T:\DellRestored\factory.swm /bootkey 8500

but this is a guess. Since you will be experimenting, it would be prudent to back up your BCD before making changes so that you have a simple recovery method. See bcdedit /export /?  and bcdedit /import /? for syntax.

Beginner
Posts: 0
Comments: 6

#112

Mark:

Actually, I have tried many times using Reagentc but always giving error message:

Reagentc /enable
REAGENTC.EXE Operation failed: 57
The parameter is incorrect.

Reagentc /disable
REAGENTC.EXE Operation failed: 2
The system cannot find the file specified

reagentc /setreimage /path S:\recovery\windowsre /target c:\windows
REAGENTC.EXE Operation failed: b7
Cannot create a file when that file already exists.

I've tried to move the ReAgent.xml first to another folder and rerun to set WinRe path:
reagentc /setreimage /path S:\recovery\windowsre /target c:\windows
REAGENTC.EXE Operation failed: 2
The system cannot find the file specified

however to set image path is always working.
reagentc /setreimage /path R:\DellRestored\windowsre /target c:\windows
REAGENTC.EXE Operation successful.

attached is
- ReAgent.xml found in windows\system32\recovery
- Reagentc.exe /info > reagentcinfo.txt

I've followed as in the lnk below:
http://en.community.dell.com/support-forums/software-os/f/3524/t/19359150.aspx
and the problem is that any command line of reagentc executed is always giving error as I've mention above.

Thanks

Attachment Size
68187-96103.txt 497 bytes
68187-96106.txt 828 bytes
Beginner
Posts: 0
Comments: 6

#113

Mark:

For some info, I've tried to unhide the partition 1 & 2, and copy winre.wim to c:\windows\system32\recovery
Then run Reagentc /enable and operation successfuly (you might want to compare with the previous reagentcinfo.txt)

run Reagentc /info
===================================================================
Extended configuration for the Recovery Environment

Windows RE enabled: 1
Windows RE staged: 1
Setup enabled: 1
Custom Recovery Tool: 0
WinRE.WIM directory: \\?\GLOBALROOT\device\harddisk0\partition1\recovery\windowsre
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
BCD Id: 3fa5486f-4324-11e0-9225-f04da2b958fb
Setup Files: \\?\GLOBALROOT\device\harddisk0\partition2\DellRestore
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful
===================================================================

Reagent.xml still the same with the previous one

Another Reagentc command line still giving the same error (/setreimage and /disable)

Forum Star
Posts: 19
Comments: 2110

#114

Nenda:

I have looked carefully at the REAgentC commands and outputs and the reagent.xml files and compared them to the ones on my system, and I can't find any reason that they are unsuccessful. I'm handicapped by not knowing how the Dell recovery mechanism works, so I'm afraid that I can't help.

Beginner
Posts: 0
Comments: 6

#115

Mark:

Thank you for all of your effort, I really appreciate it. I'll keep trying to find the solution and when I've found it I'll post it here.
Again, Thank You.

Regards,
Nenda

Forum Star
Posts: 19
Comments: 2110

#116

Nenda:

I have spotted some things that look puzzling while comparing your two BCDs from reply #110:

1. MyBCD03 looks to be a BCD located on your C: partition (in C:\Boot\BCD). Is this correct?
2. MyBCD01 looks to be a BCD that is located on the first partition (the one assigned drive letter S: by Windows 7 installed on the third partition). Is this correct?
3. Could you describe how you listed BCD01? For example, did you make partition 1 active and then boot into Windows 7 to list it?

The reason for asking is that I see several anomalies in BCD01:
a) The second entry, "Windows Boot Loader" has the wrong ID for starting the "Recovery Sequence". The ID listed appears nowhere in the BCD. It should have the ID {7499d2b8-3e53-11de-8c2d-00188bacd860}
b) The third entry, "Windows Boot Loader" references an installation of Windows 7 located on a partition with drive letter E. Your previous posts use different drive letters (S, R, C, and D) assigned by the primary installation of Windows 7. Which partition was this referring to? It must be a partition that existed at the time that you listed BCD01 or else the "device" entry would have said "Unknown" instead of "E".
c) A similar comment applies to the second "Resume from Hibernate" entry (it also references a partition E).

Beginner
Posts: 0
Comments: 1

#117

Hey Mark, I'm having the exact same problem, and I tried to follow your steps, and not getting any where at this moment. Here's my bcdedit.

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
path \bootmgr
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {955b730f-6742-11df-9009-00262dd1a003}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {685d9a46-c0d2-11df-989a-f04da2462ef0}
device ramdisk=[C:]\Recovery\685d9a46-c0d2-11df-989a-f04da2462e
f0\Winre.wim,{685d9a47-c0d2-11df-989a-f04da2462ef0}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\685d9a46-c0d2-11df-989a-f04da2462e
f0\Winre.wim,{685d9a47-c0d2-11df-989a-f04da2462ef0}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {685d9a46-c0d2-11df-989a-f04da2462ef0}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {955b730f-6742-11df-9009-00262dd1a003}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures

Windows Boot Loader
-------------------
identifier {955b7311-6742-11df-9009-00262dd1a003}

Windows Boot Loader
-------------------
identifier {e9cfff1e-de32-11e0-8757-d5b21d3ad1e1}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{e9cfff1f-de32-11e0-8757-d5b21d3ad1e1}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{e9cfff1f-de32-11e0-8757-d5b21d3ad1e1}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {955b730f-6742-11df-9009-00262dd1a003}
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 {685d9a47-c0d2-11df-989a-f04da2462ef0}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\685d9a46-c0d2-11df-989a-f04da2462ef0\boot.sdi

Device options
--------------
identifier {955b7312-6742-11df-9009-00262dd1a003}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {e9cfff1f-de32-11e0-8757-d5b21d3ad1e1}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\Windows\system32>

Beginner
Posts: 0
Comments: 3

#118

I'm having the same problems & getting the same error codes using reagentc- apparently no one knows what they mean (exactly) or why we're getting them... I've tried moving both files (ReAgent.xml & Winre.wim) it either has no effect or produces a different error. Seems like no matter what I do I get an error!
I wish I knew which file it is referring to with error code b7 (file already exists). Guessing it's ReAgent.xml but moving it or changing the name gives another error so I don't know...

Why is this thread marked as SOLVED when it is not solved- based on my interpretation of the last page of posts?

Please post if anyone figures out any solutions... Or comes up with helpful info or helpful links! Thank you!!!

WHY????!!!!!! can't ::CORRECTION=WON'T:: Microsoft just publish full information about their OSes- including error codes & their meanings and solutions- as well as proper instructions/explanations of their commands & apps...??? It's such a pain- all this info should be readily available on THEIR site, but there's very little there and it's not helpful at all.

Forum Star
Posts: 19
Comments: 2110

#119

Michael and Jon:

My apologies for not being able to help with your BCD problems at the moment - I'm teaching two electronics courses and it's very demanding during exam week. I'll try to have a look next week when things settle down.

Jon - the thread was marked as "solved" by the original poster since the first 5 posts in the thread solved his problem. If you're looking for detailed documentation from Microsoft you can find it on TechNet here: http://technet.microsoft.com/en-us/library/default.aspx

Beginner
Posts: 0
Comments: 3

#120

Mark, thank you so much for such a speedy response- no apologies necessary! I think we all understand how busy life can get...

I was thinking after posting that the original issue of the thread was probably solved and this was really just a tangential discussion.

Thank for the link! I am actually familiar with the site, but it often seems like the information I need is not there- or I can't find it... And I've certainly done a fair amount of digging (on top of regular searches).

Beginner
Posts: 0
Comments: 1

#121

Hi Mark
I have Toshiba laptop; I formatted using an OEM DVD. After formatting, I tried to reformat the laptop using my hidden recovery program but I could not.
After I start my laptop while I am pressing the zero button, the message
**** HDD RECOVERY MODE ***** appears for seconds then the windows 7 starts.
Pressing on the zero button does not go to the screen that helps to format my laptop as before to choose 32 bit or 64 bit
I am enclosing the bcdoutput.txt and the harddisk.ping
I need your help to solve the problem of formatting my laptop using my recovery partition
Thank you in advance

Attachment Size
79926-97720.txt 9.4 KB
79926-97723.png 136.51 KB
d h
Beginner
Posts: 0
Comments: 1

#122

I'm having the same issue. I tried f8 to get to the advanced boot options and i pressed enter on "repair your computer" but it says windows is loading files and then takes me to my login screen. I tried to boot the cd/dvd drive as well with a repair disk and a back up disc i burned with dell local data back up and and it still wont work. I am simply trying to restore my computer to factory settings can anyone help me on this? i have been working on this for the past 3 days and have made no progress. I tried to contact dell but since my service tag is faded they will not assist me.

bcdedit/enum all had gave me this

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-us
inherit {globalsettings}
resumeobject {f6dc7a96-5e99-11df-9430-d31953fe70f4}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 4

Windows Boot Loader
-------------------
identifier {3172f022-05bb-11e1-b661-a7f4b9e6b724}
device partition=C:
path \Temp1234\Windows\system32\winload.exe
description Windows (TM) Code Name "Longhorn" Preinstallation Enviro
nment (recovered)
locale en-US
osdevice partition=C:
systemroot \Temp1234\Windows
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {f6dc7a98-5e99-11df-9430-d31953fe70f4}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {f6dc7a96-5e99-11df-9430-d31953fe70f4}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures
bootlog No

Windows Boot Loader
-------------------
identifier {f6dc7a98-5e99-11df-9430-d31953fe70f4}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{f6dc7a99-5e99-11df-9430-d31953fe70f4}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{f6dc7a99-5e99-11df-9430-d31953fe70f4}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {f6dc7a96-5e99-11df-9430-d31953fe70f4}
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 {f6dc7a99-5e99-11df-9430-d31953fe70f4}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Beginner
Posts: 0
Comments: 1

#123

Hi Mark,

I am having similar problems. When I hit F8 then 'Repair Computer' it takes me to Windows login. I am using Vista on Dell Inspiron 1525. If you could advise it would be much appreciated.

My bcdedit /enum all output is below:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {b78c570d-d2ac-11dc-aca7-e608095aa759}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
resume No

Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
device partition=D:
path \Windows\System32\boot\winload.exe
description Windows Recovery Environment
osdevice partition=D:
systemroot \Windows
nx OptIn
detecthal Yes
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows Vista
locale en-US
inherit {bootloadersettings}
recoverysequence {572bcd55-ffa7-11d9-aae0-0007e994107d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {b78c570d-d2ac-11dc-aca7-e608095aa759}
nx OptIn

Resume from Hibernate
---------------------
identifier {b78c570d-d2ac-11dc-aca7-e608095aa759}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

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

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows

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}

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

Many thanks

James

Beginner
Posts: 0
Comments: 1

#124

Someone help me!!! The option to repair my computer wont work and the prompt code just says access denied!

Beginner
Posts: 0
Comments: 4

#125

I am pretty clueless when reading these fixes, mostly because I don't understand the computer lingo. But I am in desperate need of help. I came home from work, sat down to start my computer, and it wouldn't start. I pressed F8, and tried to repair my computer and received this code 0xc00000e9.
Then I pressed F2, to do a startup repair and received this error message: 0XMUQW-0005T2-XD003G-60WE03K, product id WQ652UA#ABA

I have tried googling all of this, but have gotten nowhere.

So then I went online and purchased a Windows 7 recovery disk, started my computer and booted from cd. I ran the memtest and got this back: /boot/memtest.exe
status: 0xc000000f
Info: The selected entry could not be loaded because the application is missing or corrupt

I'm still puzzled on how to fix this.
I also ran the repair with it and received this:
NO OS files found on disk
Repair Action: Partition table repair
Result: Failed Error Code=0x490

I searched for how to fix this and put in this info on cmd line
DISKPART
LIST DISK
SELECT DISK#
LIST PARTITION
SELECT PARTITION #
ACTIVE
EXIT

I chose the disk #0, if that helps any and partition #3 (it seemed the most appropriate), I then had to reboot and it brought me right back to where I started from. I have sooooo many pics, programs, and videos on my computer and cannot afford to lose them. My computer is supposed to still be under warranty, considering I bought it in January 2011, called HP, they said it expired in July of 2011. Waiting on a call back from the place I purchased it, to get my receipt. In the meantime, please help...I really need to fix my pc.

Beginner
Posts: 0
Comments: 4

#126

Forgot to mention, I have an HP G42, windows 7 os

Beginner
Posts: 0
Comments: 3

#127

@sunny babies:

First of all, since your primary concern seems to be recovery of the data (pictures & videos) on your computer (hard drive) and not so much your operating system or the functionality of the repair function itself, I would recommend you to physically remove the hard drive from your computer (you'll have to look up how to do that elsewhere if you aren't sure how).
Hook up that hard drive to another computer, the average desktop computer probably has a free SATA port you can connect it to. Have another hard drive ready (preferably a new external hard drive which you can use as backup for all your personal & valuable files from now on). You'll have to figure out what drive letter has been assigned to the hard drive you took out of your computer.
Open the Users folder on that HD and find your account and open that. Copy all the important files you want to save to your external. There will probably be important files in many other locations on your HD.
You may need file recovery software if your files or partition do not show up & are missing.
The less you try to do to your drive before salvaging your personal media files, the better! Don't worry about getting your operation system running until you rescue your pics & videos.

Hope that helps!

Beginner
Posts: 0
Comments: 4

#128

Hello,
Thanks for your reply. I was able to take the hard drive and put it in another computer and transfer all of my files and pictures over to an external hard drive. So the next step, is how to fix it, if it can be fixed. This is where I'm at a standstill. Unfortunately, I didn't get a Windows 7 cd with my computer when I put it, seems they have been doing this a lot lately with the newer laptops. I was able to get a windows 7 repair disc by using my fiance's computer. After using that cd, I came up with the above previously noted errors. Does my hard drive still have a chance?

Beginner
Posts: 0
Comments: 1

#129

Hi Mark, Please help me.. I can't restore from my recovery partition. It doesn't bring the F10 resprawn option. I use Alienware M17X . I see that you have saved a lot of lives here. Please save me . Below is my bcedit info . I've also attached my disk management screenshot. Thanks

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {5df8ce96-0c05-11e1-90d4-b81fd3f2d572}
displayorder {current}
toolsdisplayorder {bdbdbd00-6057-11e0-a7f3-ce9adfd72085}
{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 {7984d1d4-0bde-11e1-86f3-b07674903f67}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {5df8ce96-0c05-11e1-90d4-b81fd3f2d572}
nx OptIn

Windows Boot Loader
-------------------
identifier {7984d1d4-0bde-11e1-86f3-b07674903f67}
device ramdisk=[C:]\Recovery\7984d1d4-0bde-11e1-86f3-b07674903f
67\Winre.wim,{7984d1d5-0bde-11e1-86f3-b07674903f67}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\7984d1d4-0bde-11e1-86f3-b07674903f
67\Winre.wim,{7984d1d5-0bde-11e1-86f3-b07674903f67}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {7984d1d6-0bde-11e1-86f3-b07674903f67}
device partition=\Device\HarddiskVolume2
path \Windows\system32\boot\winload.exe
description Windows (TM) Code Name "Longhorn" Preinstallation Enviro
nment (recovered)
osdevice partition=\Device\HarddiskVolume2
systemroot \Windows
detecthal Yes
winpe Yes

Resume from Hibernate
---------------------
identifier {5df8ce96-0c05-11e1-90d4-b81fd3f2d572}
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

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=\Device\HarddiskVolume2
path \ntldr
description Earlier Version of Windows

Real-mode Boot Sector
---------------------
identifier {bdbdbd00-6057-11e0-a7f3-ce9adfd72085}
device partition=C:
path \bdrescue.mbr
description Bitdefender Rescue Mode

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}

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

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

Device options
--------------
identifier {7984d1d5-0bde-11e1-86f3-b07674903f67}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\7984d1d4-0bde-11e1-86f3-b07674903f67\boot.sdi

C:\Windows\system32>

Attachment Size
86940-98749.png 70.93 KB
Beginner
Posts: 0
Comments: 3

#130

hi,
please help me...i will tell you exactly what is my problem and what i have done...and please reply asap :

problem (1) :-
i can't open my laptop...it appears message "File is possibly corrupt. File header checksum doesn't match computed checksum"
i repaired it by using vista disk recovery..i opened command prompt and typed these commands:

Diskpart
list disk
select disk 0
list partition
select partition 1
active

then i run the startup repair and the message "File is possibly corrupt. File header checksum doesn't match computed checksum" is gone
and the windows installed in (E:)

Problem (2) :-
when i done problem 1 ....i also can't open the windows...it appears a new repair tool consisting "test system" & "test memory" and i can't enter to the windows....beside..i done the 2 tests and all passed and still can't open the windows

"see the pictures..sorry for bad resolution" please reply asap...and thanks

Attachment Size
90465-99316.jpg 13.32 KB
90465-99319.jpg 13.75 KB
90465-99322.jpg 12.81 KB
Forum Hero
Posts: 613
Comments: 8748

#131

@Hossam,

At what point during boot up do you get the error message?

Does the F8 option work allowing you to start SAFE mode?

@Sunny Babes,

There are a number of possibilities that caused your problem;

1. Registry corruption caused by an incorrect shutdown of Windows.

2. A virus.

3. A failing hard drive.

Do you have a bootable antivirus CD?

The Windows 7 (and Vista) recovery CD is not as thorough as XP, you often have to run the startup repair option a number of times as it only fixes one fault at a time.

Do you

Beginner
Posts: 0
Comments: 4

#132

I fixed the problem. F8 wouldn't work, no. However, I took my hard drive out and put it in another computer and that computer recognized the error and automatically fixed it. Recovery cd wouldn't work, nothing would work, until I did this. I put the hard drive back in and the computer started right up.
Thanks for everything.

Beginner
Posts: 0
Comments: 3

#133

guys....sorry...i forgot to say that my problem is solved :) (by Mark)
thanks Mark and thanks for all how replied to me :)

Beginner
Posts: 0
Comments: 3

#134

Mark or anyone that can help.

Same problem as a lot of people here. Dell Studio running Win 7 Home.
Trying to restore to factory via f8 - Repair your Computer.
After getting the advanced options via f8, clicking on repair your computer just starts windows.

See bcd attached.

Let me know what else you might need.
Thanks
jerry

Attachment Size
90652-99340.txt 3.75 KB
Forum Star
Posts: 19
Comments: 2110

#135

jerry:

I don't see anything wrong with your BCD.

Are you sure that the path to the recovery folder is correct? To find out you could start Windows Disk Management console and assign a temporary drive letter (let's say X:, for example) to the second partition that's currently hidden. This will allow you to browse the partition in Windows Explorer. Check to see that you have a folder named X:\Recovery and that it contains the folder WindowsRE, which in turn contains the files Winre.wim and boot.sdi. You'll need to enable viewing of hidden and system files to see them.

If you don't find them then look for them in your C: drive.

Beginner
Posts: 0
Comments: 3

#136

Mark,
Thanks for the quick response. That is one of the reasons I need to do a factory restore. I can't open up the management console as I get an error "MMC can't initialize the span in". I have windows files corrupted.

If I remember right, there is a hidden partition.
I do find a Recovery directory in System32 but it only contains ReAgent.xml

Any ideas?

Forum Star
Posts: 19
Comments: 2110

#137

jerry:

Do you have a Windows 7 System Repair disk? You could access the other partition by booting from the System Repair Disk. If you don't have one, see if your PC can make one. Type "Repair" in the Windows 7 Start/Search box and choose "Create a System Repair Disk". If the PC is too corrupted to be able to do this then you could borrow a repair CD from a friend who has one or you could make one on a working Windows 7 PC.

Can you start Disk Management by typing "partition" in the Start/Search box and selecting "Create and Format Hard Disk Partitions"? This probably will result in the same MMC error message but it's worth a try.

If some of your Windows files are corrupted have you tried running the system file checker? From an elevated command prompt type: sfc /scannow

Beginner
Posts: 0
Comments: 3

#138

I do that the system repair disk and will boot to that in a minute.
I the meantime I ran the system file checker with the result below plus log attached.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 32% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

Forum Star
Posts: 19
Comments: 2110

#139

jerry:

You might find the following article useful. http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

One thing that the article mentions is that you may need to run the System File Checker more than once to fix all of the problems.

I extracted the following from your log. These are the log entries for "could not verify" and for "cannot repair". The "Cannot Repair" entries list 5 corrupted files. You may be able to replace them if you have access to a retail Windows 7 DVD of the same architecture (64-bit).

Another alternative is to do a repair install. This article explains how to do one: http://www.sevenforums.com/tutorials/3413-repair-install.html

Attachment Size
90674-99343.txt 6.67 KB
Beginner
Posts: 0
Comments: 9

#140

Similar problem?
Driver Signature Enforcement error and no F8 in Windows Boot Manager.

Sorry for the long message but I thought it might be useful to say the all story.
bcdedit /enum all is at the bottom.

This has nothing to do with Acronis unfortunately - I had been working for days on a new system on my wife's computer (software, settings, network, cleanings, backups, "aux petits oignons" as we say in French) and I was stupid enough to crash the system before having made any functional image with Acronis.
I consider myself as a noob, able to find and copy other people solutions but not always understanding what I'm doing (maybe one day).

1 disk with 3 partitions, Windows 7 64 Pro on C.

It started with me adding a user password to a perfectly functioning system and adding a DefaultPassword Key in the registry (never again). I got a Wrong Password screen at boot and typing the proper password would not change anything. In order to fix this, I applied the sticky Key method found on the web:

Boot from Windows Repair Disk and access the command prompt.
copy c:\windows\system32\sethc.exe c:\
copy /y c:\windows\system32\cmd.exe c:\windows\system32\sethc.exe

After this, the system couldn't boot (I can't remember the message at the time, I've seen so many now).

I then went into numerous options to recover my Bootloader (fixmbr, fixboot rebuildbcd, with bcd.old, bcd.old1, bcd.old2 hanging on C: now) and I finally applied this one:

bootrec.exe /fixmbr
bootsect.exe /nt60 all /force
attrib -h -s C:\boot\BCD
del C:\boot\BCD
bcdedit /createstore c:\boot\bcd.temp
bcdedit.exe /store c:\boot\bcd.temp /create {bootmgr} /d "Windows Boot Manager"
bcdedit.exe /import c:\boot\bcd.temp
bcdedit.exe /set {bootmgr} device partition=C:
bcdedit.exe /timeout 10
attrib -h -s C:\boot\bcd.temp
del c:\boot\bcd.temp
bcdedit.exe /create /d "Microsoft Windows" /application osloader
The entry {blablabla...} was successfully created.
bcdedit.exe /set {blablabla...} device partition=C:
bcdedit.exe /set {blablabla...} osdevice partition=C:
bcdedit.exe /set {blablabla...} path \Windows\system32\winload.exe
bcdedit.exe /set {blablabla...} systemroot \Windows
bcdedit.exe /displayorder {blablabla...}

Now I'm stuck in Windows Boot Manager:
File: \windows\system32\winload.exe
Status: 0xc0000428
Info: Windows cannot verify the digital signature for this file.

By pressing Enter, I get the next Windows Boot Manager page asking to select operating system "Microsoft Windows" but whether I press Enter or F8, I go back to previous page with wrong digital signature.

If I try an automated repair from Repair Disk, I get this Windows message:
Nom d’événement de problème: StartupRepairOffline
Signature du problème 01: 6.1.7600.16385
Signature du problème 02: 6.1.7600.16385
Signature du problème 03: unknown
Signature du problème 04: -1
Signature du problème 05: ExternalMedia
Signature du problème 06: 1
Signature du problème 07: MissingOsLoader
Version du système: 6.1.7601.2.1.0.256.1
Identificateur de paramètres régionaux: 1036

After demoralization and a few days break, I found this forum and Mark Wharton's powerful suggestions.
Here is the bcdedit /enum all list:

Gestionnaire de d‚marrage Windows
---------------------------------
identificateur          {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
displayorder            {ffb131e8-5053-11e1-8197-e4c0e063d282}
timeout                 10

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {ffb131e8-5053-11e1-8197-e4c0e063d282}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Microsoft Windows
osdevice                partition=C:
systemroot              \Windows

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {ffb131e9-5053-11e1-8197-e4c0e063d282}
device                  ramdisk=[C:]\Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\Winre.wim,{ffb131ea-5053-11e1-8197-e4c0e063d282}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (r‚cup‚r‚)
locale                 
osdevice                ramdisk=[C:]\Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\Winre.wim,{ffb131ea-5053-11e1-8197-e4c0e063d282}
systemroot              \windows
winpe                   Yes

Testeur de m‚moire Windows
--------------------------
identificateur          {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                 

Options de p‚riph‚rique
-----------------------
identificateur          {ffb131ea-5053-11e1-8197-e4c0e063d282}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\boot.sdi

Is this a lost cause or some great soul can help?
Thanks for reading.
Christophe

Forum Star
Posts: 19
Comments: 2110

#141

Christophe:

Can you access System Restore from a Windows Repair Disk? If so, and if you have a restore point from before the problem started, I would try this method first.

If you boot from the Windows Repair Disk, can you run REGEDIT, mount the registry hive on your main Windows partition and then remove the entry from the registry that caused this problem in the first place? I

F8 "Repair your computer" is probably not working because your Windows Boot Loader entry should look like this:

Chargeur de d‚marrage Windows
-----------------------------
identificateur {ffb131e8-5053-11e1-8197-e4c0e063d282}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows
recoverysequence        {ffb131e9-5053-11e1-8197-e4c0e063d282}
recoveryenabled         Yes
osdevice partition=C:
systemroot \Windows

However, the Windows Repair CD has the same capabilities as F8.

Finally, is this article of any help? http://answers.microsoft.com/en-us/windows/forum/windows_7-system/driver-signature-enforcement-error-screen-cant-be/f73ec888-b87b-4416-82a0-35f200a151c4

Beginner
Posts: 0
Comments: 9

#142

Hi Mark,

Thanks for your quick answer.

I could access System Restore from Repair CD but it is a function in Windows I have never used, I always relied on my Acronis images so no restore point.

There is a Registry Editor in Microsoft Diagnostics and Recovery Toolset on my Repair CD, I used it to suppress the DefaulPassword key I had created before, no improvement as I think my problem is beyond this now.

Your Windows Boot Loader entry should look like this:
recoverysequence {ffb131e9-5053-11e1-8197-e4c0e063d282}
recoveryenabled Yes

Any way I can fix these 2 lines through cmd.exe from Repair CD?

When I boot from disk and get to Driver Signature Enforcement error page, I don't have access to cmd.exe since I have no access to F8.
If I boot from Repair CD and type bcdedit.exe /set nointegritychecks ON, it says it cannot find the file (in French).
If I type
bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS, it says invalid command line.

I haven't tried yet the ReadyDriver solution suggested in your link as I thought, since I can't even press F8, my problem is somewhere else.

Thanks again.

Forum Star
Posts: 19
Comments: 2110

#143

Christophe:

Some of your commands may not have succeeded since none of the BCD entries are labeled as {current} or {default}. So you probably have to use the specific ID for each entry, in your case the ID is {ffb131e8-5053-11e1-8197-e4c0e063d282}. For example:

bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} recoverysequence {ffb131e9-5053-11e1-8197-e4c0e063d282}

bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} recoveryenabled yes

I can't find Disable_Integrity_Checks listed in the BCD reference documentation, but one article online has the option name spelled differently as DDISABLE_INTEGRITY_CHECKS (with two Ds for Driver Disable), so maybe try:

bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} loadoptions DDISABLE_INTEGRITY_CHECKS

I have no experience using this option.

Beginner
Posts: 0
Comments: 9

#144

Mark,

Typical situation where I don't know what I am doing but things seem to improve.

bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} recoverysequence {ffb131e9-5053-11e1-8197-e4c0e063d282}
OK
bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} recoveryenabled yes
OK
bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} loadoptions DDISABLE_INTEGRITY_CHECKS
OK

When I boot, no sign of any system, I systematically get into recovery tool, where I can choose a user (with functioning password or standart) then the only option left is an automated repair with no success (missingOsLoader).

Here is the new bcd enum:

Gestionnaire de d‚marrage Windows
---------------------------------
identificateur          {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
displayorder            {ffb131e8-5053-11e1-8197-e4c0e063d282}
timeout                 10

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {ffb131e8-5053-11e1-8197-e4c0e063d282}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Microsoft Windows
loadoptions             DDISABLE_INTEGRITY_CHECKS
recoverysequence        {ffb131e9-5053-11e1-8197-e4c0e063d282}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {ffb131e9-5053-11e1-8197-e4c0e063d282}
device                  ramdisk=[C:]\Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\Winre.wim,{ffb131ea-5053-11e1-8197-e4c0e063d282}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (r‚cup‚r‚)
locale                 
osdevice                ramdisk=[C:]\Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\Winre.wim,{ffb131ea-5053-11e1-8197-e4c0e063d282}
systemroot              \windows
winpe                   Yes

Testeur de m‚moire Windows
--------------------------
identificateur          {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                 

Options de p‚riph‚rique
-----------------------
identificateur          {ffb131ea-5053-11e1-8197-e4c0e063d282}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\boot.sdi

Any more good ideas?

Forum Star
Posts: 19
Comments: 2110

#145

Christophe:

That seems to be progress. Try setting the main Windows Boot Loader entry to be the default:

bcdedit /default {ffb131e8-5053-11e1-8197-e4c0e063d282}

I still don't understand the error message from Automated Repair (missing OsLoader). I can clearly see two OsLoader entries in your BCD. They have the French title Chargeur de d‚marrage Windows. Perhaps it's related to not having one of them set as the default OsLoader, so try the above command to see if it changes anything.

If there are no changes then I'm wondering if you have multiple BCDs on your disk and the system is using the wrong one? Try booting from a recovery CD and going to a command prompt. Find the drive letter of the Windows partition (as seen in the recovery environment), which may or may not be C. Assuming that it's C then try listing the contents and looking for files named BCD. You need to use the /a switch on the dir command to display hidden and protected OS files when looking:

C:
dir /a
cd Boot
dir /a

The BCD is usually located at C:\Boot\BCD. How many do you see and where are they located?

Beginner
Posts: 0
Comments: 9

#146

Hi Mark,

I agree with you, it "seems" to be progress...

bcdedit /default {ffb131e8-5053-11e1-8197-e4c0e063d282}
OK

Reboot: same as before, Recovery tool, automated repair with no success (missingOsLoader).

I tried:

bcdedit /set {default} recoveryenabled no
Back to Driver Signature Enforcement error and no F8 in Windows Boot Manager.

bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit /set {ffb131e8-5053-11e1-8197-e4c0e063d282} recoveryenabled yes
Back to previous state with automated repair (missingOsLoader).

C:
dir /a
Le volume dans le lecteur C n'a pas de nom.
 Le num‚ro de s‚rie du volume est 58A8-5A9A

 R‚pertoire de C:\

05/02/2012  15:01    <REP>          $Recycle.Bin
24/12/2011  13:05                 0 AdobeDebug.txt
05/02/2012  23:03            24576 BCD_Backup
05/02/2012  23:03            21504 BCD_Backup.LOG
05/02/2012  17:18                 0 BCD_Backup.LOG1
05/02/2012  17:18                 0 BCD_Backup.LOG2
05/02/2012  23:14            12288 BCD_Backupcdboot
05/02/2012  23:14             9216 BCD_Backupcdboot.LOG
05/02/2012  23:10                 0 BCD_Backupcdboot.LOG1
05/02/2012  23:10                 0 BCD_Backupcdboot.LOG2
06/02/2012  01:31    <REP>          Boot
21/11/2010  04:24           383786 bootmgr
21/11/2010  04:24           383786 bootmgr~1
19/12/2011  19:36             8192 BOOTSECT.BAK
20/12/2011  02:16               174 csb.log
14/07/2009  06:08    <JONCTION>     Documents and Settings [C:\Users]
05/02/2012  16:01     3156332544 hiberfil.sys
20/12/2011  02:16               206 Install.log
19/12/2011  21:21    <REP>          Intel
23/12/2011  23:47    <REP>          MSOCache
05/02/2012  16:01     4ÿ208ÿ443ÿ392 pagefile.sys
14/07/2009  04:20    <REP>          PerfLogs
29/01/2012  17:45    <REP>          Program Files
01/02/2012  15:40    <REP>          Program Files (x86)
01/02/2012  11:03    <REP>          ProgramData
19/12/2011  19:45    <REP>          Recovery
20/12/2011  02:16             3120 RHDSetup.log
21/11/2010  04:24           279040 sethc.exe
03/02/2012  14:01    <REP>          Softs'Ium
02/02/2012  19:18    <REP>          System Volume Information
05/02/2012  15:01    <REP>          Users
28/01/2012  11:09    <REP>          VueScan
05/02/2012  14:55    <REP>          Windows
              18 fichier(s)    7365901824 octets
              15 R‚p(s)  17242ÿ722304 octets libres

cd Boot
dir /a

Le volume dans le lecteur C n'a pas de nom.
 Le num‚ro de s‚rie du volume est 58A8-5A9A

 R‚pertoire de C:\Boot

06/02/2012  01:31    <REP>          .
06/02/2012  01:31    <REP>          ..
08/02/2012  18:23            20480 BCD
05/02/2012  17:41            12288 BCD.Backup.0001
05/02/2012  21:35            12288 BCD.Backup.0002
05/02/2012  23:08            12288 BCD.Backup.0003
05/02/2012  23:25            12288 BCD.Backup.0004
06/02/2012  01:31            12288 BCD.Backup.0005
08/02/2012  18:23            25600 BCD.LOG
22/07/2011  14:41                 0 BCD.LOG1
22/07/2011  14:41                 0 BCD.LOG2
05/02/2012  17:18            28672 bcd.old
05/02/2012  23:03            16384 bcd.old1
05/02/2012  23:14            12288 bcd.old2
06/02/2012  00:45             5120 bcd.temp.LOG
19/12/2011  19:36            65536 BOOTSTAT.DAT
05/02/2012  16:07    <REP>          cs-CZ
05/02/2012  16:07    <REP>          da-DK
05/02/2012  16:07    <REP>          de-DE
05/02/2012  16:07    <REP>          el-GR
05/02/2012  16:07    <REP>          en-US
05/02/2012  16:07    <REP>          es-ES
05/02/2012  16:07    <REP>          fi-FI
05/02/2012  16:07    <REP>          Fonts
05/02/2012  16:07    <REP>          fr-FR
05/02/2012  16:07    <REP>          hu-HU
05/02/2012  16:07    <REP>          it-IT
05/02/2012  16:07    <REP>          ja-JP
05/02/2012  16:07    <REP>          ko-KR
21/11/2010  04:24           485760 memtest.exe
05/02/2012  16:07    <REP>          nb-NO
05/02/2012  16:07    <REP>          nl-NL
05/02/2012  16:07    <REP>          pl-PL
05/02/2012  16:07    <REP>          pt-BR
05/02/2012  16:07    <REP>          pt-PT
05/02/2012  16:07    <REP>          ru-RU
05/02/2012  16:07    <REP>          sv-SE
05/02/2012  16:07    <REP>          tr-TR
05/02/2012  16:07    <REP>          zh-CN
05/02/2012  16:07    <REP>          zh-HK
05/02/2012  16:07    <REP>          zh-TW
              15 fichier(s)          721280 octets
              26 R‚p(s)  17242722304 octets libres

For information, 05/02/2012 is the day I started having problems and tried differents fixboot and fixbcd as mentioned in my 1st post.
Thanks again for your patience.

Forum Star
Posts: 19
Comments: 2110

#147

Christophe:

If you don't mind, please attach two files to your next post - the oldest and newest versions of the BCD visible in your directory listings above:

C:\Boot\bcd.old
C:\Boot\bcd

So that the forum software will allow attachment, re-name the files to:

bcd.old.txt
bcd.txt

I'll see if I can see anything in these that gives additional clues.

Beginner
Posts: 0
Comments: 9

#148

Whatever you say.

Attachment Size
90943-99352.txt 28 KB
90943-99355.txt 12 KB
90943-99358.txt 20 KB
Forum Star
Posts: 19
Comments: 2110

#149

Christophe:

There are so many items missing from your current BCD that it may be easier to go back to the oldest BCD, which looks almost complete.

From your recovery CD, assuming that C: is the drive letter of the Windows partition, first save a copy of the current BCD and then restore the oldest BCD:

cd Boot
attrib -h bcd
ren bcd bcd.new

attrib +h bcd.new

attrib -h bcd.old
ren bcd.old bcd
attrib +h bcd

With the old bcd now in use, try listing its contents to verify:

bcdedit /enum all

The output should look like the attached text file bcd.old (except mine is in English, yours will be in French and ignore the partition references in my file that say "unknown", which list that way because the specific disk sector locations are only available on your hard disk)

The "device" and "osdevice" entries for the recovery section will now need to be added since they're missing:

bcdedit /set {6cc32327-2a70-11e1-8ef7-ec5e305ff384} device ramdisk=[C:]\Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\Winre.wim,{6cc32328-2a70-11e1-8ef7-ec5e305ff384}

bcdedit /set {6cc32327-2a70-11e1-8ef7-ec5e305ff384} osdevice ramdisk=[C:]\Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\Winre.wim,{6cc32328-2a70-11e1-8ef7-ec5e305ff384}

Note that the recovery folder name is different here than in your newest BCD, so I'm assuming that the folder name did not change and is still located at C:\Recovery\cc32327-2a70-11e1-8ef7-ec5e305ff384. You could check this before entering the above commands.

If this still doesn't work, post the output of bcdedit /enum all again as a text file.

Attachment Size
90958-99361.txt 3.03 KB
Beginner
Posts: 0
Comments: 9

#150

Well, that was something to type in. But sorry, no improvement.

C:\Recovery\ cc32327-2a70-11e1-8ef7-ec5e305ff384 is the correct folder name.
Here is the last bcdedit /enum all

Gestionnaire de d‚marrage Windows
---------------------------------
identificateur          {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {default}
resumeobject            {6cc32325-2a70-11e1-8ef7-ec5e305ff384}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 5

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {default}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  fr-FR
inherit                 {bootloadersettings}
recoverysequence        {6cc32327-2a70-11e1-8ef7-ec5e305ff384}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {6cc32325-2a70-11e1-8ef7-ec5e305ff384}
nx                      OptIn

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {6cc32327-2a70-11e1-8ef7-ec5e305ff384}
device                  ramdisk=[C:]\recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\winre.wim,{6cc32328-2a70-11e1-8ef7-ec5e305ff384}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\winre.wim,{6cc32328-2a70-11e1-8ef7-ec5e305ff384}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Reprendre … partir de la mise en veille prolong‚e
-------------------------------------------------
identificateur          {6cc32325-2a70-11e1-8ef7-ec5e305ff384}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  fr-FR
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Testeur de m‚moire Windows
--------------------------
identificateur          {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Diagnostics m‚moire Windows
locale                  fr-FR
inherit                 {globalsettings}
badmemoryaccess         Yes

ParamŠtres EMS
--------------
identificateur          {emssettings}
bootems                 Yes

ParamŠtres du d‚bogueur
-----------------------
identificateur          {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

Erreurs de m‚moire RAM
----------------------
identificateur          {badmemory}

ParamŠtres globaux
------------------
identificateur          {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

ParamŠtres du chargeur de d‚marrage
-----------------------------------
identificateur          {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

ParamŠtres de l'hyperviseur
-------------------
identificateur          {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

ParamŠtres du chargeur de reprise
---------------------------------
identificateur          {resumeloadersettings}
inherit                 {globalsettings}

Options de p‚riph‚rique
-----------------------
identificateur          {6cc32328-2a70-11e1-8ef7-ec5e305ff384}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\6cc32327-2a70-11e1-8ef7-ec5e305ff384\boot.sdi

I wish I knew how to do this myself.