Multi Boot Problems

When I try to access your attachment from #5 I get: Access denied

Hi Pentagon,
If you are unable to get access to the attachment on #5 then I assume others can’t which might explain why I have had little reaction to my post.
The attachment was a pdf but I will add it here in the main body text.
Microsoft Windows [Version 10.0.19045.4046]
(c) Microsoft Corporation. All rights reserved.

C:\windows\system32>bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=D:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {1b88fc9e-d815-11ee-b564-001e4f483239}
displayorder {current}
{320064c9-dcf6-11e6-b810-a59dd9419a62}
{ntldr}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \windows\system32\winload.exe
description Windows 10
locale en-us
inherit {bootloadersettings}
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \windows
resumeobject {1b88fc9e-d815-11ee-b564-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 {bootloadersettings}
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 {ntldr}
device partition=D:
path \ntldr
description Windows XP Pro

C:\windows\system32>

Also since I used EasyBCD yesterday it has further messed up the boot menu as below where XP has now disappeared!
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 {1b88fcb1-d815-11ee-b564-001e4f483239}
resumeobject {1b88fcb0-d815-11ee-b564-001e4f483239}
displayorder {1b88fcb1-d815-11ee-b564-001e4f483239}
{1b88fcad-d815-11ee-b564-001e4f483239}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {1b88fcb1-d815-11ee-b564-001e4f483239}
device partition=H:
path \windows\system32\winload.exe
description Windows 7
locale en-us
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=H:
systemroot \windows
resumeobject {1b88fcb0-d815-11ee-b564-001e4f483239}
nx OptIn
detecthal Yes

Windows Boot Loader
-------------------
identifier {1b88fcad-d815-11ee-b564-001e4f483239}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {6274ad62-da4f-11ee-b5a9-806e6f6e6963}

And here’s my Disc Management view:

Hope you can shed some light on all this.
Thanks

Yes, I did that...deleted all menu entries then added all back in EasyBCD... but that was when it failed to add XP and gave me win 10 and win7 boot loader identifiers the same. As in my post above.

Also my question about which version to buy was not about EasyBCD but their recovery tools EasyRE. So I guess you are saying I need to buy the Win 10 version, as only my Win 10 is working atm, and it hopefully will repair the 7 and XP windows?

davesurrey said:

And here’s my Disc Management view:

Where?
The current bootmanager is in the XP-Partition. Did you run EasyBCD from WIN10?
The lower part of diskmanagement with the diagram is helpful.

Yes I ran EasyBCD (and all the other helper apps) from Win 10. That’s the only one that I can get to boot.

As an aside…I’ve been multi-booting for years including a lot of Linux distros with grub and never had so much confusion as this. I’m starting to wonder if it really is a boot issue or something else (UEFI?).

The Disc Management was a jpg screen shot and it seems that it doesn’t work if I put it in the text body so I have attached it here. It’s also in post #3.


- - - Updated - - -

Not near the PC in question atm . Will post the lower part of Disc Management tomorrow. Apologies.

Well if it was Windows 7-10 I would assume the msconfig and then you would adjust if you saw the boot options or just booted into a selected OS.

Usually there is also a file that you would edit presented on a drive, this file contains the directions and selection of the OS you wish to boot from.

Now if all three OS are installed on this machine and you have booted into them via the selection screen method, ask yourself "Why is it booting into Windows 10 only and not going to the boot selection screen ?

Again I thinking about that file you should be able to edit, and using msconfig to set boot or even disable or limit the counter on the list to boot into whichever OS you want.

Do not worry, as long as your operating systems are in tact you could also try making a boot-loader on a USB thumb drive, and having the computer boot that first and then you select which OS to boot into.

You should see when you boot the selectin menue WIN 7 and Microsoft Windows.
According the displayorder entries WIN 7 is on the 1st place.

Do you get a Blue screen when you try WIN7?
When you run EASYBCD and select
Add new Entry you have to uncheck "Automatically detect current drive"
and select Type: Windows NT/2K/XP/2K3

No BSOD.
Before EasyBCD did its worst it worked like this...
Boot into Win 10 works well.
Selecting Win 7 or Win XP on what I think is called the Metro screen and the PC goes back to the Bios then starts to boot into 7 or XP and I see the start of the splash screen of 7 or XP for a few seconds as if it is trying to boot but then it crashes out to the Bios screen again. No BSOD.

- - - Updated - - -

When I first noticed booting problems last week I took a clone of the disk in case I messed up anything. I think it may be best I revert to that tomorrow as using some of these "helper" apps may have caused more problems than they solved.
I'll get back with some screen shots then.
Thanks

- - - Updated - - -

Yes I selected the correct Type in EasyBCD and unchecked "auto detect current drive" by following the instruction on their site, which are very clear.

I would not use "Metro" Bootmenue
bcdedit /set {1b88fcad-d815-11ee-b564-001e4f483239} bootmenupolicy legacy

Unfortunately you have lost your Recovery Environment that a USB-Boot-Medium is needed.