Solved Fixing Boot Manager on SSD, Win7 installed with other HDD active

[ChrisRoss]

Found some other posts on this subject and it appears I need the Boot files copied to my SSD so it can boot without the other drive active. Situation is:

Win7 installed on SSD while first system disk still connected now won't boot unless first system disk also installed. First system disk has Win XP installed. Not normally an issue as it boots up with both drives but assume I'd be better having the ability to boot independently. Here is result from bcdedit /enum all:


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=E:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {504f5c04-70b6-11e1-b7a7-bf5493004b3c}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 0

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
loadoptions DDISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {504f5c06-70b6-11e1-b7a7-bf5493004b3c}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {504f5c04-70b6-11e1-b7a7-bf5493004b3c}
nx OptIn

Windows Boot Loader
-------------------
identifier {504f5c06-70b6-11e1-b7a7-bf5493004b3c}
device ramdisk=[C:]\Recovery\504f5c06-70b6-11e1-b7a7-bf5493004b3c\Winre.wim,{504f5c07-70b6-11e1-b7a7-bf5493004b3c}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\504f5c06-70b6-11e1-b7a7-bf5493004b3c\Winre.wim,{504f5c07-70b6-11e1-b7a7-bf5493004b3c}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {504f5c04-70b6-11e1-b7a7-bf5493004b3c}
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=E:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=E:
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}
{hypervisorsettings}

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

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

Device options
--------------
identifier {504f5c07-70b6-11e1-b7a7-bf5493004b3c}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\504f5c06-70b6-11e1-b7a7-bf5493004b3c\boot.sdi

and here is screen shot of disk manager:


Ideally I'd like to leave the spinning disc bootable from a boot menu if required but to normally boot to the SSD without going through the boot menu. From what I've read I think I only need to copy the boot files to the SSD. Currently it boots straight from the SSD but fails if I disconnect the XP HDD which has the boot files. Only found this out when trouble shooting a boot problem after installing some new hardware.

In the screen shot disk 0 is the original spinning disc with XP. Disk 1 is my data storage array. Disk 2 is the SSD with Win 7.

Appreciate any guidance on fixing this.

Thanks

Chris

 

[gregrocker]

You configured a Dual Boot with XP by not unplugging the HD first before install.

Please post back a screenshot of your maximized Win7 Disk Mgmt drive map and listings, using the SNipping Tool in Start Menu.

Normal method is to Mark Active Win7 partition or it's 100mb System Reserved partition, unplug XP HD, set WIn7 HD first to boot in BIOS setup, then run Startup Repair - Run 3 Separate Times.

Once Win7 starts on its own and holds the System Active boot flags, you can plug back in the XP HD, boot it when needed by tapping the one-time BIOS Boot Menu key at boot.

 

[ChrisRoss]

Thanks Greg,

I have attached snip of disk management. Believe I have disk 2 showing as active. Before I made it active I tried a repair install with just the SSD attached and install could not find the SSD. Is making it active enough to allow the install program to find the SSD?

If that's the case all I need do is run repair install 3 times with XP HDD unplugged??

Thanks again for the advice.

Chris

 

[gregrocker]

System flag only on E (XP?) means it is dual booting both OS's. You'll need to write the System boot files to C by marking it Active and running Startup Repair repeatedly until Win7 starts on its own and holds the System Flag.

Unplug all other HD's, swap the cable from XP HD to Win7 so C is in Disk0 position and is set first HD to boot in BIOS setup. Then run the Repairs until it starts.

 

[edwar]

The simple thing to do is Start Over by connecting only the SSD to the system and install Win 7 on it.

 

[ChrisRoss]

Ok, all fixed, the SSD will boot by itself and is marked system/boot/page file/active etc. Boot order is sorted in BIOs so all is right with the world. Thanks for the assistance.

 

[gregrocker]

Glad to help.