Multi Boot Problems

I swopped the HDD for the one cloned a few days ago before I started to try to fix this boot problem. It exhibits the same problem but at least it shows the 3 versions of Windows at boot up.
Windows 10 boots up fine.
Also I tool Pentagon’s suggestion and did
“bcdedit /set {id} bootmenupolicy legacy” and after a couple of reboots it went from the “Metro” screen to the legacy one.
Not sure why this would make a difference as I have a laptop that boots into Win10/Win7and 2 Linux distros and uses Metro for the Windows choice. But at this stage I won’t rule anything out.
Based on the cloned disc:


Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=D:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {94ce2e56-6ae6-11ee-9bf0-001e4f483239}
resumeobject {94ce2e55-6ae6-11ee-9bf0-001e4f483239}
displayorder {94ce2e56-6ae6-11ee-9bf0-001e4f483239}
{320064c9-dcf6-11e6-b810-a59dd9419a62}
{466f5a88-0af2-4f76-9038-095b170dc21c}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {94ce2e56-6ae6-11ee-9bf0-001e4f483239}
device partition=C:
path \WINDOWS\system32\winload.exe
description Windows 10
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {acef3384-acab-11ea-b202-001e4f483239}
displaymessageoverride StartupRepair
recoveryenabled Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {94ce2e55-6ae6-11ee-9bf0-001e4f483239}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {320064c9-dcf6-11e6-b810-a59dd9419a62}
device partition=H:
path \Windows\system32\winload.exe
description Windows 7 Pro 64bits
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {320064ca-dcf6-11e6-b810-a59dd9419a62}
recoveryenabled Yes
osdevice partition=H:
systemroot \Windows
resumeobject {320064c8-dcf6-11e6-b810-a59dd9419a62}
nx OptIn

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=D:
path \ntldr
description Windows XP Pro

As before it boot to Win 10. But choosing either Win 7 or Win XP it only starts what looks like a boot as I see the respective initial boot splash screens for a few seconds before it reverts back to the BIOS splash screen.

Hopefully this will allow someone to tell me what my next move should be, before I give up and do a compete reinstall.

The BCD entries are OK and ntldr based Windows systems have to run in legacy. XP-64 detects GPT but doesn't run on GPT.

But to me the whole disk looks like a GPT-Disk and what is the sence of the EFI-Partition in the end?
Any error in the bcd-settings would result in a BSOD.

That’s what I have been thinking all along. I can’t see what is the error in the boot menus. I am wondering if this Dell stores a setup in its “Bios?”

I can confirm the XP is a 32 bit version.
As regards the disc it is very much not GPT. Please see below.

The partition at the end was for a Windows 11 install (yes I know it should be NTFS) or for a Linux distro and is currently blank.
Is it possible that there is something in the “bios/NVRam” that is causing these problems?



- - - Updated - - -

Also the cloned disk was smaller and didn't have the extra partitions at the end but still behaved the same. So I doubt that has anything to do with what is happening.

In Win 10 the FastBoot option is disabled?
C:\WINDOWS\system32>powercfg /H off
The bootmenupolicy is still showing Standard
What happens if you change {default} in msconfig to WIN 7?
reagentc /info ?

Yes fast boot is disabled.
Did cmd> powercfg /H off...no difference
Not sure how you are seeing that bootmenupolicy is standard...as the Metro icons have gone and now the windows choice is just lines of text.
I've changed the default in msconfig before but did it again and still it makes no difference ...Win 10 loads but Win 7 doesn't load.
Did cmd> reagentc /info. See below.

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: acef3384-acab-11ea-b202-001e4f483239
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

What I did notice in msconfig is that in the General Tab >Start Up Selection was pointing at Selective StartUp and not Normal. I changed it back to Normal but after reboot it keeps going back to Selective???

look in Windows 10 Boot Loader: last entry. There it is Standard

bcdedit /set {94ce2e56-6ae6-11ee-9bf0-001e4f483239} bootmenupolicy Legacy

it's good that your Recovery Environment is activated, that you don't need any USB-Bootstick.
It's interesting, as your Recovery is on the Win XP partition!
Run the test:
hold <Shift> and select <Start> + <Reboot>
Select Troubleshoot and let it reboot up to "Command Prompt"

Just looked and it says Legacy which I expected it to as the Metro icons have gone.
How do you get them back BTW?

I assume the Boot menu I attached was taken just before I changed to legacy. However it didn't solve the problem.

Not sure what you mean by
"hold <Shift> and select <Start> + <Reboot>
Select Troubleshoot and let it reboot up to "Command Prompt""
If you are saying that's how to get to a cmd prompt then thanks but I am aware how to do that.

What do you think to my suggestion that it could be something in the bios that is affecting this?

If no more suggestions from anyone then I am going to just do a new install as I've spent far too much time on this.
Thanks for you help.

I just wanted to check if it boots to Recovery from the XP-partition.
Run XP and WIN7 in VMs.

Okay let's try, but please spell out how to do that.
Start from OFF?
Switch ON whilst holding Shift Key?

Or Boot into 10 and go to Troubleshoot??
Sorry but not clear.

Hold <Shift> go to <Start> On/Off ==> Reboot

or type cmd (admin) reagentc /boottore and reboot normally