[EBCD-526] EasyBCD does not find Windows XP install

#1
I have a Win 7 and Win 8.1 dual UEFI boot on a GPT disk (Disk 0). I installed Windows XP on an MBR disk (Disk 2). When I try to add an XP boot entry with EasyBCD (running on the Win 7 install), I get an error that EasyBCD failed to detect a valid installation of Windows NT-2003 on all mounted drives and was unable to continue.

When I select Disk 2 as the boot disk, it boots the XP install just fine. I recently did a clean install of Windows XP on Disk 2.

Thanks in advance for any help.



Here is the detailed display mode settings:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=S:
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {5760b6dc-58bc-11e3-9bb8-a226aa93e6e2}
resumeobject {5760b6de-58bc-11e3-9bb8-a226aa93e6e2}
displayorder {5760b6dc-58bc-11e3-9bb8-a226aa93e6e2}
{5760b6df-58bc-11e3-9bb8-a226aa93e6e2}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 3
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {5760b6dc-58bc-11e3-9bb8-a226aa93e6e2}
device partition=C:
path \Windows\system32\winload.efi
description Windows 7
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {5f81e2d6-596a-11e3-93eb-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {5760b6df-58bc-11e3-9bb8-a226aa93e6e2}
device partition=D:
path \WINDOWS\system32\winload.efi
description Windows 8.1
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {5760b6e0-58bc-11e3-9bb8-a226aa93e6e2}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=D:
systemroot \WINDOWS
resumeobject {5760b6de-58bc-11e3-9bb8-a226aa93e6e2}
nx OptIn
bootmenupolicy Standard
 

Attachments

Terry60

Knows where his towel is.
Staff member
#2
Can you post the contents of boot.ini from your XP partition please.
 
#3
Can you post the contents of boot.ini from your XP partition please.
Here it is:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect

Again, thank you for your help.
 

Terry60

Knows where his towel is.
Staff member
#4
OK
That shows your XP OS folder has the standard name, so EasyBCD should have no trouble locating it for that reason, and the fact that you can boot it independently shows that the XP kernel must be present and correct. They're the two things EasyBCD needs to identify XP.
Assuming you are not using an old out-of-date build (if you are, get the latest here and try again), I can only infer that it maybe a problem to do with the mix of GPT/MBR disk types, but that's pure speculation.
You could try booting XP via the BIOS override, installing a copy of EasyBCD on there, pointing it at the EFI System partition (File > Select BCD store - you'll need to give the partition a letter temporarily so that Explorer can navigate there) and try adding an XP entry to the W8 BCD from XP).
Failing those providing a solution, you'll need to wait around for CG to appear to confirm/deny that GPT/MBR is an issue.
 
#5
OK
That shows your XP OS folder has the standard name, so EasyBCD should have no trouble locating it for that reason, and the fact that you can boot it independently shows that the XP kernel must be present and correct. They're the two things EasyBCD needs to identify XP.
Assuming you are not using an old out-of-date build (if you are, get the latest here and try again), I can only infer that it maybe a problem to do with the mix of GPT/MBR disk types, but that's pure speculation.
You could try booting XP via the BIOS override, installing a copy of EasyBCD on there, pointing it at the EFI System partition (File > Select BCD store - you'll need to give the partition a letter temporarily so that Explorer can navigate there) and try adding an XP entry to the W8 BCD from XP).
Failing those providing a solution, you'll need to wait around for CG to appear to confirm/deny that GPT/MBR is an issue.
Windows XP does not allow access to GPT disks for me. Therefore, I would not be able to assign a drive letter and point EasyBCD to the BCD store on the GPT disk. I did try several things manually. From my Win 7 install, I put the Windows XP ntldr, boot.ini, and ntdectect.com in the \EFI\Windows\Boot folder and then manually adjusted the settings of boot.ini and a XP BCD entry, but I still get the error that the \EFE\Windows\Boot\ntldr file was missing.

Then I used EasyBCD to add a backup Windows 8 install Disk 1 (MBR disk) entry to my boot options. When I select that from the boot menu, the screen goes dark and nothing else happens. Again, the Windows 8 backup install boots fine when that disk is selected in BIOS. My BIOS does support compatibility boot mode, but I am thinking that once the boot process starts down the UEFI path, switching mid-stream in the boot manager to an MBR disk doesn't work.

As usual, any further inputs on this issue will be appreciated.
 

Terry60

Knows where his towel is.
Staff member
#6
Sorry, you didn't state what flavour XP you use, so I'm now assuming it's x86 if you can't see the GPT disk.
In that case, you'll need to wait for CG to reappear regarding whether detection of MBR XP from GPT 8.1 is possible.
At least you can still boot via the BIOS override.
 
#7
Sorry, you didn't state what flavour XP you use, so I'm now assuming it's x86 if you can't see the GPT disk.
In that case, you'll need to wait for CG to reappear regarding whether detection of MBR XP from GPT 8.1 is possible.
At least you can still boot via the BIOS override.
You are correct Terry in that I am running XP x86 and I can boot the the XP install via BIOS. I will check in periodically for further guidance.


Thanks again.
 

mqudsi

Mostly Harmless
Staff member
#8
The output of bootgrabber.exe /tlist from XP and from Windows 8 should help determine whether or not EasyBCD can properly see one disk from the other in opposing/alternate EFI/BIOS configurations.
Off the top of my head, I don't see a problem accessing an MBR-style disk from an EFI-based OS, but I'd rather not venture more of a guess than that at this time.
 
#9
The output of bootgrabber.exe /tlist from XP and from Windows 8 should help determine whether or not EasyBCD can properly see one disk from the other in opposing/alternate EFI/BIOS configurations.
Off the top of my head, I don't see a problem accessing an MBR-style disk from an EFI-based OS, but I'd rather not venture more of a guess than that at this time.
GC,

Thanks for the response. Let me provide some additional information:
- My main Win 7 install (with UEFI boot) is on D0, P3. D0 is the GPT-formatted disk.
- My Win 8.1 install (with UEFI boot) is on D0, P4.
- I have a Win 8 backup install (with BIOS/MBR boot) on D1, P1. D1 is a MBR-formatted disk.
- My Win XP install (with BIOS/MBR boot) is on D2, P1. D2 is a MBR-formatted disk.
- I recently installed a Linux system on D2, P2.
-- (An interesting note here. I copied over a Win 7 BCD file (installed in C:\Boot) and a bootmgr file
-- (installed in C:\) I then used BCDedit to update the BCD information for a dual XP-Linux boot.
-- It worked.)
- As noted above, my XP install does not have drivers to read GPT-formatted disks.

Again, any additional input would be appreciated.




Output from Win 7 install:

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>

WARN: Unable to get volume information for \\?\Volume{ad7030aa-574d-11e3-871e-806e6f6e6963}\
WARN: Unable to get volume information for \\?\Volume{1b7408b2-5a66-11e3-b348-94de80a7e0d0}\
WARN: No active partition detected on disk 0.
D0,5,0,5,512110190592,0
P1,,40,104857600,53424128,No,multi(0)disk(0)rdisk(0)partition(1),No,
P2,,22,134217728,134217728,No,multi(0)disk(0)rdisk(0)partition(2),No,
P3,C:\,162,209715200000,158896369664,No,multi(0)disk(0)rdisk(0)partition(3),No,NTFS
P4,E:\,162,209348198400,194298515456,No,multi(0)disk(0)rdisk(0)partition(4),No,NTFS
P5,,164,367001600,68734976,No,multi(0)disk(0)rdisk(0)partition(5),No,
D1,3,3,0,1000204886016,1
P1,E:\,7,107374182400,92958494720,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,NTFS
P2,H:\,7,268195332096,63682011136,Yes,multi(0)disk(0)rdisk(1)partition(2),No,NTFS
P3,V:\,7,624391356416,80922476544,Yes,multi(0)disk(0)rdisk(1)partition(3),No,NTFS
D2,3,3,0,2000398934016,2
P1,F:\,7,209715200000,199415586816,Yes,multi(0)disk(0)rdisk(2)partition(1),Yes,NTFS
P2,,131,209715200000,209715200000,Yes,multi(0)disk(0)rdisk(2)partition(2),No,
P3,,130,33554432000,33554432000,Yes,multi(0)disk(0)rdisk(2)partition(3),No,


Output from Win XP install:

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>

WARN: Unable to get volume information for \\?\Volume{974f74c8-6785-11e3-99a7-806d6172696f}\
WARN: No active partition detected on disk 0.
D0,1,1,0,512110190592,2
P1,,238,512110190080,512110190080,Yes,multi(0)disk(0)rdisk(2)partition(1),No,
D1,3,3,0,1000204886016,1
P1,D:\,7,107374182400,92962689024,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,NTFS
P2,H:\,7,268195332096,63686205440,Yes,multi(0)disk(0)rdisk(1)partition(2),No,NTFS
P3,V:\,7,624391356416,80926670848,Yes,multi(0)disk(0)rdisk(1)partition(3),No,NTFS
D2,3,3,0,2000398934016,0
P1,C:\,7,209715200000,199416201216,Yes,multi(0)disk(0)rdisk(0)partition(1),Yes,NTFS
P2,E:\,131,209715200000,209715200000,Yes,multi(0)disk(0)rdisk(0)partition(2),No,
P3,,130,33554432000,33554432000,Yes,multi(0)disk(0)rdisk(0)partition(3),No,
 
#10
GC,

Thanks for the response. Let me provide some additional information:
- My main Win 7 install (with UEFI boot) is on D0, P3. D0 is the GPT-formatted disk.
- My Win 8.1 install (with UEFI boot) is on D0, P4.
- I have a Win 8 backup install (with BIOS/MBR boot) on D1, P1. D1 is a MBR-formatted disk.
- My Win XP install (with BIOS/MBR boot) is on D2, P1. D2 is a MBR-formatted disk.
- I recently installed a Linux system on D2, P2.
-- (An interesting note here. I copied over a Win 7 BCD file (installed in C:\Boot) and a bootmgr file
-- (installed in C:\) I then used BCDedit to update the BCD information for a dual XP-Linux boot.
-- It worked.)
- As noted above, my XP install does not have drivers to read GPT-formatted disks.

Again, any additional input would be appreciated.




Output from Win 7 install:

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>

WARN: Unable to get volume information for \\?\Volume{ad7030aa-574d-11e3-871e-806e6f6e6963}\
WARN: Unable to get volume information for \\?\Volume{1b7408b2-5a66-11e3-b348-94de80a7e0d0}\
WARN: No active partition detected on disk 0.
D0,5,0,5,512110190592,0
P1,,40,104857600,53424128,No,multi(0)disk(0)rdisk(0)partition(1),No,
P2,,22,134217728,134217728,No,multi(0)disk(0)rdisk(0)partition(2),No,
P3,C:\,162,209715200000,158896369664,No,multi(0)disk(0)rdisk(0)partition(3),No,NTFS
P4,E:\,162,209348198400,194298515456,No,multi(0)disk(0)rdisk(0)partition(4),No,NTFS
P5,,164,367001600,68734976,No,multi(0)disk(0)rdisk(0)partition(5),No,
D1,3,3,0,1000204886016,1
P1,E:\,7,107374182400,92958494720,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,NTFS
P2,H:\,7,268195332096,63682011136,Yes,multi(0)disk(0)rdisk(1)partition(2),No,NTFS
P3,V:\,7,624391356416,80922476544,Yes,multi(0)disk(0)rdisk(1)partition(3),No,NTFS
D2,3,3,0,2000398934016,2
P1,F:\,7,209715200000,199415586816,Yes,multi(0)disk(0)rdisk(2)partition(1),Yes,NTFS
P2,,131,209715200000,209715200000,Yes,multi(0)disk(0)rdisk(2)partition(2),No,
P3,,130,33554432000,33554432000,Yes,multi(0)disk(0)rdisk(2)partition(3),No,


Output from Win XP install:

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>

WARN: Unable to get volume information for \\?\Volume{974f74c8-6785-11e3-99a7-806d6172696f}\
WARN: No active partition detected on disk 0.
D0,1,1,0,512110190592,2
P1,,238,512110190080,512110190080,Yes,multi(0)disk(0)rdisk(2)partition(1),No,
D1,3,3,0,1000204886016,1
P1,D:\,7,107374182400,92962689024,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,NTFS
P2,H:\,7,268195332096,63686205440,Yes,multi(0)disk(0)rdisk(1)partition(2),No,NTFS
P3,V:\,7,624391356416,80926670848,Yes,multi(0)disk(0)rdisk(1)partition(3),No,NTFS
D2,3,3,0,2000398934016,0
P1,C:\,7,209715200000,199416201216,Yes,multi(0)disk(0)rdisk(0)partition(1),Yes,NTFS
P2,E:\,131,209715200000,209715200000,Yes,multi(0)disk(0)rdisk(0)partition(2),No,
P3,,130,33554432000,33554432000,Yes,multi(0)disk(0)rdisk(0)partition(3),No,
Some additional info -

I can add my backup Win8 install on D1, P1 to the UEFI boot menu (on D0) with EasyBCD. Note that D1 is a MBR-formatted disk. When I am in the UEFI boot menu (on D0), I can select either my Win7 install (on D0, P3) or my Win 8 install (on D0, P4), and both boot fine. When I select my Win8 backup install from the boot menu, the screen just goes black, and nothing else happens.

I noticed that D0, P4 and D1, P1 are both assigned drive letter E:, but D0, P4 should be assigned drive letter D: ???

Thanks.
 

mqudsi

Mostly Harmless
Staff member
#11
That does look OK.

What happens when you run

bootgrabber.exe /bootcfg /vv

?
 
#12
That does look OK.

What happens when you run

bootgrabber.exe /bootcfg /vv

?
It looks like bootgrabber has some problem getting the correct boot information ...


Output from Win 7 install (Disk0, Partition3, UEFI boot/GPT-formatted HD):

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>

WARN: Unable to get volume information for \\?\Volume{ad7030aa-574d-11e3-871e-80
6e6f6e6963}\
WARN: Unable to get volume information for \\?\Volume{1b7408b2-5a66-11e3-b348-94
de80a7e0d0}\
WARN: No active partition detected on disk 0.
ERRR: Unable to detect correct boot device, quitting.


Output from Win XP install (Disk2, Partition1, BIOS boot/MBR-formatted HD):


BootGrabber utility.
Copyright NeoSmart Technologies 2009-2011 <http://neosmart.net/>

WARN: Unable to get volume information for \\?\Volume{974f74c8-6785-11e3-99a7-80
6d6172696f}\
WARN: No active partition detected on disk 0.
 

mqudsi

Mostly Harmless
Staff member
#13
Ah, makes sense. The GPT disk is the boot device and BG is unable to read it (because it sees only the protective MBR). This is normally considered a fatal error (no valid boot partition) and there's no point in BG continuing because no matter how well-formed of a boot.ini you have, without a boot partition it's useless.

Aside from making BG read GPT disks (a real pain and probably unnecessary for now), it's possible to make BG just ignore this error when a GPT disk is detected.. Interesting, thanks.

---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------

Filed as [EBCD-526].