Windows 7 Boot Partition.

Does it show up in Disk Management?

Mercurio, do you mean the MBR?
If so, I think it is included a part of a normal backup; it is optional to restore the MBR from a particular backup, however.

MudCrab: No. Seems to be hidden more thoroughly than most hidden partitions. (By the way, sent you a PM.)

Andromeda492: No. Seems Windows 7 has a new, private boot or system partition.

However this partition seems to only be created in specific scenarios. See MudCrabs reply directly below.

The Windows 7 boot partition is only created if you install it to an unallocated drive. If you install it to an existing partition, it won't be created. Instead, booting will be done from the Windows 7 partition. Perhaps you don't have one and that's why you can't find it. If it's there, it would show up in Disk Management. Does "Boot" show up on the Windows 7 partition in Disk Management?

Enable viewing of hidden and system files and check if the \BOOT folder and the bootmgr file exist on the Windows 7 partition.

Viewing the output from bcdedit would also tell you if the Windows 7 partition is the booting partition.

Yeah, \Boot folder exists on the Windows 7 Partition. It's also indicated in Disk Management as the boot partition and there is only one entry in bcdedit, the C: partition. I'll take that to mean I'm in the clear. Thanks. )

Wondering how the issue is handled for those that do have the System Partition.

For those that do have a separate Win 7 boot partition, it will show up in TI even though it is a hidden partition, and it can be backed up and restored normally.

I don't have that, but then, I've always done my partitioning with Seagate SeaTools before OS install.

I installed Win7 Ult on a prepartitioned disk - one containing my XP installation - and this partition was not created either. Both the /Boot and /Recovery folders are on the Win7 partition.

I actually created my own Win7 Boot/WinRE/Bitlocker partition later. Always make a full system backup first!

I shovelled out 300M of unallocated space at the front of the drive (using DD10 boot CD), then using MS bdehdcfg utility to create the partition. move the recovery environment, and maintain some space should I wish to enable bitlocker in the future. This process wipes the /Boot and /Recovery folders on the Win7 partition - moving them to the new boot partition. Tested it out - all OK.

After that - I restored my Win7 partition from backup - which brought those folders back. Now - I can set either partition active - and all will boot properly (though the extra partition forced me to make some changes to the XP boot.ini file - pointing to partition 4 instead of 3).

When used as I used it - the bdehdcfg utility required 300M unallocated free space - or it will take it from your Win7 partition (the docs say 100M min - but the code required 300). When Win7 installation creates this partition, it is marked as type 0x27 and hidden. This utility creates a standard 0x07 type - unhidden - and a drive letter will get assigned. So back to DD10 - I changed it to 0x27 and hid it - no more drive letter.

And FYI... TI will indeed see and backup the hidden type 0x27 partition.

Googling this partition suggests ways to remove or prevent installation. To me - keeping the Recovery Environment on a seperate partition makes sense - and as bitlocker will also use it (should I later enable) - that's why I went through the exercise.

For more info on bdehdcfg (it's already on your disk - at least if your Win7 version supports Bitlocker):

http://technet.microsoft.com/en-us/library/ee732026(WS.10).aspx

Charles:

Good advice. When I installed Win 7 I had already created a boot partition for it, and the installer put the boot files on this partition and set the type to 0x027h. However, it put the WinRE files on the main Win 7 partition. I never thought that this was a good idea and I've been considering moving them to the boot partition.

I'll probably just do this manually by copy/pasting the "Recovery" folder while booted to VistaPE and then manually fixing the WinRE entries in the BCD. I don't understand why the installer would choose to put WinRE on the main Win 7 partition - what good is the recovery environment if the partition gets damaged?

My biggest fear is drive failure - particularly on notebooks and no RAID. No partition scheme or secure zone saves you then.

So I'm religious about full backups to alternate media weekly, and data replication across network(s) every few hours. In event of op system crash, unlikely I'll resort to WinRE with up-to-date backups handy.

For the curious, read through the use of the utility in the TechNet article. Though it appears specific to Bitlocker - it also transfers the bootloader and WinRE.

___________
Chip

Charles:

If you don't mind, could you post the output of bcdedit /enum all (from the BCD located on your boot partition)? I'd like to see how bdehdcfg configured the boot manager entry for WinRE.

***Edit*** Never mind, I was momentarily confused by the references to \windows in the boot manager entry, forgetting that these refer to the \windows folder on WinRE. I was successful in moving the recovery environment to the boot partition from its default location in the Win 7 partition. It all works fine.

If anyone is interested, here are the details. Previous values are in blue; changed values are in red:

Moving the Windows Recovery Environment (WinRE) from the Windows partition to the boot partition.

11/29/2009  MJW

Use a PE boot disk (I used VistaPE) to make the following changes:
1. Copy the folder C:\Recovery to the boot partition
2. Edit the BCD so that the entries point to the boot partition instead of to C:
3. Test
4. Delete the C:\Recovery folder

C:\Windows\system32>bcdedit /enum all (edited to leave only relevant entries)

Before:
=========================================================
Windows Boot Loader
-------------------
identifier          {1891464f-9a7d-11de-9ebe-fe9c458232f8}
device              ramdisk=[C:]\Recovery\1891464f-9a7d-11de-9ebe-fe9c458232
f8\Winre.wim,{18914650-9a7d-11de-9ebe-fe9c458232f8}
path                 \windows\system32\winload.exe
description       Windows Recovery Environment
inherit              {bootloadersettings}
osdevice           ramdisk=[C:]\Recovery\1891464f-9a7d-11de-9ebe-fe9c458232
f8\Winre.wim,{18914650-9a7d-11de-9ebe-fe9c458232f8}
systemroot       \windows
nx                     OptIn
winpe                Yes

Device options
--------------
identifier              {18914650-9a7d-11de-9ebe-fe9c458232f8}
description           Ramdisk Options
ramdisksdidevice  partition=C:
ramdisksdipath     \Recovery\1891464f-9a7d-11de-9ebe-fe9c458232f8\boot.sdi
==========================================================
After:

Windows Boot Loader
-------------------
identifier         {1891464f-9a7d-11de-9ebe-fe9c458232f8}
device             ramdisk=[\Device\HarddiskVolume1]\Recovery\1891464f-9a7d
-11de-9ebe-fe9c458232f8\Winre.wim,{18914650-9a7d-11de-9ebe-fe9c458232f8}
path                \windows\system32\winload.exe
description      Windows Recovery Environment
inherit              {bootloadersettings}
osdevice           ramdisk=[\Device\HarddiskVolume1]\Recovery\1891464f-9a7d
-11de-9ebe-fe9c458232f8\Winre.wim,{18914650-9a7d-11de-9ebe-fe9c458232f8}
systemroot       \windows
nx                     OptIn
winpe                Yes

Device options
--------------
identifier               {18914650-9a7d-11de-9ebe-fe9c458232f8}
description            Ramdisk Options
ramdisksdidevice   boot
ramdisksdipath      \Recovery\1891464f-9a7d-11de-9ebe-fe9c458232f8\boot.sdi

Note that your {GUID} references in the BCD will be different.

Hadn't visited the thread recently.

I had to do a few bcdedits to get everything the way I wanted it - I see you also figured it out.

Chip

Chip:

I liked the idea so much that I've moved WinRE to the boot partition on all 3 of my Windows 7 PCs (work, home, laptop). Thanks for the inspiration.

I guess I'm the odd man out as I don't have a SRP. After reading this interesting thread I thought I'd try the robocopy/BING method of removing a SRP, but in reverse. It does work. You can create a SRP if you don't have one with this method.

Brian:

Do you understand why so many people want to remove the SRP from Windows 7? I see so many postings on the net where people hate this with a passion and just want to get rid of it. I don't understand. To me, having an independent partition that the PC boots from is a good idea.

I think part of the problem is that a lot of people just aren't aware of it. They backup the Windows partition and then run into problems after restoring, for example. So it's a bad first experience.

In other cases, they may need the partition table slot used by the SRP for another partition.

Personally, I don't have a problem with it. I use it or not, as I want. My main computer has it. Some of my test setups have it, some don't.

Hi guys,

Good to talk to you again.

Like MudCrab, I can take it or leave it, but I'd rather leave it. I have images of both installations in my test computer and I'm comfortable working with both. The Ghost 2003 people don't like a SRP as they can't have four {boot} in their BCD store (Win7 won't boot) and that makes their restores difficult at times. Maybe they should move on from Ghost 2003.

I don't use BitLocker and I gather it is only present in Ultimate and Enterprise Win7 so most people won't be using it either. I'm not concerned about having a recovery environment when I can just restore my OS from an image if there is a problem. Having an extra partition slot by not having a SRP is a big plus in my opinion. I can always use that slot. And I only have to backup and restore one partition instead of two.

The Dell computers I've seen recently don't have a 100 MB SRP. They have the booting files in the Dell Recovery Partition which is about 10 GB. So if you are upgrading to a new HD, this partition has to be restored as well as the Win7 partition. The Recovery Partition is the System, Active partition. Not the Win7 partition. No wonder we are seeing restore problems in the forums.

Mark Wharton (If you're available) or others:

*I am trying to move the winre.wim to the boot partition and set the parameters right for that.

Just info below from left to right in Disk Management
{GUIDs}
Hidden Dell Diagnostic partition \Device\HarddiskVolume1
{1f8184a2-14de-11df-9734-f08c6d8c50b0} = BOOT PARTITION R: \Device\HarddiskVolume2
{4411bd70-3260-11e1-ab83-806e6f6e6963} = Window 7 OS C: \Device\HarddiskVolume3

I think I've grasped what I have from the BCDedit /enum all
Which is:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=R:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 21
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows 7
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {4411bd70-3260-11e1-ab83-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
device ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {4411bd70-3260-11e1-ab83-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Microsoft Windows 7
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=R:
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 {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi

Device options
--------------
identifier {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

***********************
***********************
***********************

And I think what it needs to become is this:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=R:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 21
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows 7
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {4411bd70-3260-11e1-ab83-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
device ramdisk=[\Device\HardDiskVolume2]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HardDiskVolume2]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {4411bd70-3260-11e1-ab83-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Microsoft Windows 7
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=R:
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 {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi

Device options
--------------
identifier {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
description Ramdisk Options
ramdisksdidevice boot
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

***************************
***************************
***************************

**Can you double-check it to see if I missed anything? I DID notice that there was a recovery path on both GUIDs -dunno if that is right.

***I don't understand the commands used to get us this output*(the above is theoretical as I don't know how to make it that way) -can you show me what commands I would have to make to get this outcome (if it is right)? I wish there was a way to just dump the edited text version back.

Cosmo

Cosmo:

Could you post a screen shot from Disk Management showing the layout of your disk? You can use the Snipping Tool to create one; type "snip" in the Windows 7 Start/Search box.

I have the picture -and I tried using the add pic icon within the rich text editior -but it didn't work. How do I do it? Well, I'll put it in as an attachment until I know how to put it on the screen.

With Visual BCD I can make the changes rather easily -can you look over my entries (listed in first msg) and see if you find any mistakes?

I am not getting the 'Repair your computer' option anymore so I can't tell if it would error out on F8 with my other changes like it was doing before when it got 0x00000225.

Here's a better one.

I guess I should update with current bcdedit /enum all as I have been trying to get it right on my own.

C:\windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=R:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {4204ea64-3317-11e1-b9d3-001c2306439a}
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 {4204ea64-3317-11e1-b9d3-001c2306439a}
nx OptIn
detecthal Yes

Windows Boot Loader
-------------------
identifier {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
device ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {4204ea64-3317-11e1-b9d3-001c2306439a}
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=R:
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 {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi

Device options
--------------
identifier {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
A device attached to the system is not functioning.

Cosmo:

The second to last item in the BCD was probably for booting into an OEM recovery partition. Your current System Reserved partition isn't big enough to hold the referenced folder (1f8184a4-14de-11df-9734-f08c6d8c50b0), so I'm assuming that it's no longer present on your disk. Also, there isn't a boot menu entry for it, so you can delete this item:
==========================================================
Device options
--------------
identifier {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi
===========================================================

The last item in your BCD needs repaired. It should be edited to look like this:
===========================================================
Device options
--------------
identifier {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
ramdisksdidevice partition=R:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

============================================================
I'm assuming that you have already moved the folder "Recovery\75331424-308f-11e1-948d-9303e25eee7c" and its contents to your System Reserved partition.

If you want you can also change the label on the second Windows Boot Loader entry that currently has the description "Windows Recovery Environment (recovered)". You can remove the word "(recovered)" from the description. This is just a cosmetic change.

Assuming that this works, you may then want to remove the drive letter from the System Reserved partition. You can do this with Windows Disk Management. This will hide the partition so that nobody accidentally messes with it, and is the way that the Windows 7 installer sets up this partition (as hidden). If you ever want to change a file in the partition, just assign a drive letter to it, make your changes, then remove the drive letter when done.

OK, all those changes have been made.

I have a couple questions for you:

*You said, "Your current System Reserved partition isn't big enough to hold the referenced folder (1f8184a4-14de-11df-9734-f08c6d8c50b0)." -how is it that you know how big (1f8184a4-14de-11df-9734-f08c6d8c50b0) is? 

* I still don't have the 'Repair My Computer' option back -is there a way to force that back?

Thanks for your help,

Cosmo

btw -I deleted the entry with (1f8184a4-14de-11df-9734-f08c6d8c50b0) as you suggested, I made all the changes -I was just curious how you knew it was a big folder. It was a media direct partition with a barebones version of Win7 just for running DVDs etc.

Thx

Cosmo

Here's a current /enum all -thx for the help.

I still don't have the 'Repair my Comupter' option -how do I get that back?

C:\windows\system32>BCDedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=R:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {4204ea64-3317-11e1-b9d3-001c2306439a}
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 {4204ea64-3317-11e1-b9d3-001c2306439a}
nx OptIn
detecthal Yes

Windows Boot Loader
-------------------
identifier {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
device ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale
osdevice ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {4204ea64-3317-11e1-b9d3-001c2306439a}
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=R:
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 {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
ramdisksdidevice partition=R:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

Cosmo:

Your System Reserved partition contains 572 MB of data. Media Direct or OEM Recovery partitions occupy GB of space, so my conjecture was that you didn't have the folder.

Have you checked the name of the folder in R:\Recovery to verify that its name is 75331424-308f-11e1-948d-9303e25eee7c? This folder's size should be about 163 MB. Have you checked the contents of the folder to verify that it contains boot.sdi and WinRE.wim?

Other than that, I see 4 small differences between the working F8 recovery entries on my BCD compared to yours. You could try adding the following three items to the second Windows Boot Loader entry (the one that has the description "Windows Recovery Environment"):

change--> "locale" to "locale en-us"
add --> nx OptIn
add --> inherit {bootloadersettings}

On the last BCD item, "Device options", add the following:

description Ramdisk Options

If this still doesn't work, let me know precisely what you are doing to enter the recovery environment and describe what you see on the screen. This is what you should see:

Mark,

thx for following up & for even having this knowledge/ experience in your head.

Two things I don't know how to do.

1.) I don't know how to create this setting "inherit {bootloadersettings}" I saw it but Visual BCD doesn't seem to have an option of creating it -do you know a BCDedit command to create it?

2.) How do you include a screenshot within a post on this forum?

a.) What I have checked/done since your last post:

> Folder inside Recovery folder has boot.sdi & WinRE.wim

> name of file in Recovery was: 75331424-308f-11e1-948d-9303e25eee7c

> Changed it to: 75331424-308f-11e1-948d-9303e25eee7c

History: I started this whole adventure about a week ago with the 'Repair Your Computer' at the F8 startup (I think caused by my choosing to change the image so that boot partition changed from 100mb to 839mb)sending me to screen that said this:
____________________________________________________________________________________
Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem:

1. Insert your windows installation disc and restart your computer.
2. Choose your language settings, and then click next
3. Click "repair your computer."

Status: 0x00000225
Info: The boot selection failed because a required device is inaccessible.
_____________________________________________________________________________________
after doing startup repairs and working with the BCD I lost the 'Repair Your Computer' option somehow.

All repairs made except I don't know how to create this setting "inherit {bootloadersettings}" via BCDedit

Cosmo

Cosmo:

1. From an elevated command prompt, type: bcdedit /set {99be7a2d-3268-11e1-a7f7-e22372dd74b6} inherit {bootloadersettings} to add the missing entry manually. You may want to copy/paste this.

2. In your last post, item 2a) the from and to folder names are the same. Were they different?

3. To include an inline screenshot, first attach the file to your post. After submitting the post, go back and edit it using the rich-text editor mode. Copy the URL next to your file attachment. Select a location in your text to insert your picture and choose the Insert/Edit Image button (looks like mountain peaks). Paste the attachment's URL into the Image Properties dialog box.

4. Is F8 working now or not?

1. bcdedit /set {99be7a2d-3268-11e1-a7f7-e22372dd74b6} inherit {bootloadersettings}
*Operation succeeded*

2. In your last post, item 2a) the from and to folder names are the same. Were they different?
*I think so, but now that I changed it I can't be sure.*

3. To include an inline screenshot, first attach the file to your post. After submitting the post, go back and edit it using the rich-text editor mode. Copy the URL next to your file attachment. Select a location in your text to insert your picture and choose the Insert/Edit Image button (looks like mountain peaks). Paste the attachment's URL into the Image Properties dialog box.
*Thanks for the instruction*

4. Is F8 working now or not?
*I get to F8 screen and it has safe mode and all but the 'Repair Your Computer' option is still gone. Drat!
__________________

Cosmo:

Please post the output from an elevated command prompt window for the following command:

reagentc /info

C:\windows\system32>reagentc /info
Extended configuration for the Recovery Environment

Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition3\Recovery\75
331424-308f-11e1-948d-9303e25eee7c
BCD Id: 75331424-308f-11e1-948d-9303e25eee7c
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful

Ah, I see that it is pointed towards partition3 -shouldn't it be pointed towards Partition2(the boot partition) since I moved the Recovery partition and all the other flags are pointing there?

Cosmo:

Yes; the partition reference is incorrect.

Try this from an elevated command prompt window:

reagentc /setreimage /path R:\Recovery\75331424-308f-11e1-948d-9303e25eee7c

Then check again: reagnetc /info

If this doesn't result in the correct path then attach a copy of the file C:\Windows\System32\Recovery\ReAgent.xml

reagentc /setreimage /path R:\Recovery\75331424-308f-11e1-948d-9303e25eee7c
REAGENTC.EXE: Operation Failed: b7
Cannot create a file when that file already exists.

How do we wipe it out so that we can use this command?

Cosmo:

I've been experimenting with this in a VM and so far have been unsuccessful in getting the /setreimage path command to work. From some online references, it appears that you have to do this when booted to the Windows Recovery Environment (it can't be done while Windows is running). Let me try this and I'll let you know if I can figure out a way that works.

Meanwhile, please attach a copy of your C:\Windows\System32\Recovery\ReAgent.xml file. Attach it as a text file.

<?xml version='1.0' encoding='utf-8' standalone='yes'?>

That's an empty file that you probably opened by double-clicking on it. Open the file with Notepad instead.

Cosmo:

I've given up on the use of the ReAgentC tool. Apparently you need to do an reagentc /disable command first before the reagentc /setreimage command will work without giving an error message. But once you disable WinRE using the first command, the entries for WinRE in the BCD and the files in the \Recovery folder are deleted. The reagentc/disable and the reagentc/enable commands work fine on a system with a working F8 WinRE recovery environment, but it's tricky to make a change to the environment. I tried experimenting with this and got my VM's recovery environment to stop working and couldn't fix it, so I had to restore the virtual hard disk file from yesterday to recover. So I don't recommend that you experiment with ReAgentC on your working system.

One thing that I did notice is that even if the ReAgentC tool fails, the F8 function still works if the BCD entries for it are correct. So if your "Repair your Computer" function isn't working then it must have something to do with the BCD entries.

Maybe if we delete the current BCD entries and re-create them then we might get your system fixed. If you feel like doing this then post again your current BCD (as a txt file attachment, please) and I'll take another look.

This was the xml from the system32\recovery location opened by notepad:

<?xml version='1.0' encoding='utf-8'?>

How do I go about deleting the BCD files? I remember somebody told me you could delete the BCD and startup repair would make a new one -do you know if this is true?

Did the GUIDs change since my first /enum all posting?

lemme try that again

Since the drive letters change when in Recovery environment I used the command:
D:\Windows\system32>reagentc.exe /enable /auditmode /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition2\recovery\75331424-308f-11e1-948d-9303e25eee7c
Directory set to: \\?\GLOBALROOT\device\harddisk0\partition2\recovery\75331424-308f-11e1-948d-9303e25eee7c
REAGENTC.EXE: Operation successful

D:\Windows\System32>

and a reagentc /info shows it at partition2 -however
a reboot to the OS and reagentc /info STILL shows it at partition3 -Drat!!

At this point I can see that I can set the boot key option so that I can assign an F-key to boot to it -but stubbornly, that is not what I want, I want the STANDARD winre.wim to be run and I want the stinking 'Repair Your Computer' back.

Cosmo

Cosmo:

When you used the ReAgentC command in the recovery environment you were changing the recovery environment's xml file on the x: drive, which is a RAMdisk whose contents evaporate when you reboot. You would have needed to add the target to your command:

D:\Windows\system32>reagentc.exe /enable /auditmode /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition2\recovery\75331424-308f-11e1-948d-9303e25eee7c /target D:\Windows

However, I think you'll get the "can't create a file when that file already exists" error since the recovery folder already exists. If you try this, make a backup copy of the existing C:\Windows\System32\Recovery\ReAgent.xml file first in case you need to recover.

You can recreate the BCD with the BootRec tool (on a recovery disk) but I don't think this tool automatically creates the entries for the F8 function. If you try this, back up your BCD first.

Please attach your current BCD as a text file. There must be something we're missing in there.

C:\windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=R:
path \bootmgr
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {4204ea64-3317-11e1-b9d3-001c2306439a}
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 {4204ea64-3317-11e1-b9d3-001c2306439a}
nx OptIn
detecthal Yes

Windows Boot Loader
-------------------
identifier {4204ea66-3317-11e1-b9d3-001c2306439a}
device ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{4204ea67-3317-11e1-b9d3-001c2306439a}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{4204ea67-3317-11e1-b9d3-001c2306439a}
systemroot \windows
winpe Yes

Windows Boot Loader
-------------------
identifier {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
device ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
osdevice ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {4204ea64-3317-11e1-b9d3-001c2306439a}
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=R:
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 {4204ea67-3317-11e1-b9d3-001c2306439a}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

Device options
--------------
identifier {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
ramdisksdidevice partition=R:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

C:\windows\system32>

also added same/current BCD as attachment

Cosmo:

I think I see what's wrong with your BCD. I thought that you had already done the first three items on the list below, so at this point I'm not trusting Visual BCD. Do these with bcdedit:

1. *delete this Boot Loader item
Windows Boot Loader
-------------------
identifier              {4204ea66-3317-11e1-b9d3-001c2306439a}
device                  ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{4204ea67-3317-11e1-b9d3-001c2306439a}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered)
locale
osdevice                ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{4204ea67-3317-11e1-b9d3-001c2306439a}
systemroot              \windows
winpe                   Yes

From an elevated command prompt: bcdedit /delete {4204ea66-3317-11e1-b9d3-001c2306439a}

2. *Delete this Device options item:
Device options
--------------
identifier              {4204ea67-3317-11e1-b9d3-001c2306439a}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

bcdedit /delete {4204ea67-3317-11e1-b9d3-001c2306439a}

3. Add this line (indicated by a *) to the Ramdisk options section:

Device options
--------------
identifier              {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
*description        Ramdisk Options
ramdisksdidevice        partition=R:
ramdisksdipath          \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

bcdedit /set {99be7a2e-3268-11e1-a7f7-e22372dd74b6} description "Ramdisk Options"

4. Finally, add these lines (*) to the primary Windows 7 Boot Loader item:

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \windows\system32\winload.exe
description             Windows 7
locale                  en-us
inherit                 {bootloadersettings}
*recoverysequence    {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
*recoveryenabled        yes
osdevice                partition=C:
systemroot              \windows
resumeobject            {4204ea64-3317-11e1-b9d3-001c2306439a}
nx                      OptIn
detecthal               Yes

bcdedit /set recoverysequence {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
bcdedit /set recoveryenabled yes

==================================================================

Item 4 is the reason that you aren't seeing the "Repair your computer" item when you press F8. These were clearly missing from your very first BCD post. I apologize for not seeing that earlier. The attached file is what you should end up with after making the above changes.

Before I saw your last post I backed up BCD as you suggested and I looked to see if I backed it up earlier -surprisingly I did; I restored it back as far as I could go and I got the 'Repair Your Computer' option back but it still doesn't boot into it.

This is what I guess I started with -I will copy/paste the text below and include as attachment -then I guess the question is, would you like us to start from where it is now or would you like me to restore back to where it was last and make the adjustments you suggested.

Cosmo

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=R:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {75331422-308f-11e1-948d-9303e25eee7c}
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 {75331424-308f-11e1-948d-9303e25eee7c}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {75331422-308f-11e1-948d-9303e25eee7c}
nx OptIn

Windows Boot Loader
-------------------
identifier {75331424-308f-11e1-948d-9303e25eee7c}

Windows Boot Loader
-------------------
identifier {75331426-308f-11e1-948d-9303e25eee7c}
device ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{75331427-308f-11e1-948d-9303e25eee7c}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{75331427-308f-11e1-948d-9303e25eee7c}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {75331422-308f-11e1-948d-9303e25eee7c}
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=R:
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 {75331425-308f-11e1-948d-9303e25eee7c}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

Device options
--------------
identifier {75331427-308f-11e1-948d-9303e25eee7c}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

C:\Windows\system32>

Cosmo:

I think it will be easier if you restore back to the last BCD (the one in post #44) and go from there.

OK, reset to Post #44. The command from your step 1 looks the same as the one for step 2 - but making the adjustments as listed

Cosmo

The GUIDs in the commands for steps 1 and 2 are different (in the 8th hex digit).

Doh! missed the fact that they were different -thx for pointing out where.

Changes made.
Repair your Computer & Access to Recovery environment WORK!!
No errors. Issue resolved!

******Perfect Functionality!!!!*******

Mark, your help and stick-toitiveness is rare and this kind of help is a great service in an area that is lacking.
I can't tell you how happy I am to have this working!

You Rock!

Cosmo

BCD Final

=========================================================================

C:\windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=R:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {current}
resumeobject            {4204ea64-3317-11e1-b9d3-001c2306439a}
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        {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \windows
resumeobject            {4204ea64-3317-11e1-b9d3-001c2306439a}
nx                      OptIn
detecthal               Yes

Windows Boot Loader
-------------------
identifier              {99be7a2d-3268-11e1-a7f7-e22372dd74b6}
device                  ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[R:]\Recovery\75331424-308f-11e1-948d-9303e25eee
7c\Winre.wim,{99be7a2e-3268-11e1-a7f7-e22372dd74b6}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {4204ea64-3317-11e1-b9d3-001c2306439a}
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=R:
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              {99be7a2e-3268-11e1-a7f7-e22372dd74b6}
description             Ramdisk Options
ramdisksdidevice        partition=R:
ramdisksdipath          \Recovery\75331424-308f-11e1-948d-9303e25eee7c\boot.sdi

C:\windows\system32>