I need to dual Windows 11 pro and Windows 10 pre-installed on separate drives

Windows 11 boots and shows drive with Windows 10, I've tried EasyBCD that doesn't seem to do much. the bios shows both drives but one is storage and the other boot and when i make changes they swap positions when it shows windows 10 drive as boot the system won't boot until i remove window 10 drive?

Your partition layout doesn't look like it should look for Windows 10 or 11.
But ignoring that, if you want dual boot then both OS partitions should be marked active, but currently only one is active.

mark C partition on disk 1 as active, that's the bare minimum you can do without changing layout.

edit:
see for more info:

see also this:

zebal only MBR needs and can be set as active.

• Drive 0 (I suppose it is Win 10) is MBR
• Drive 1 (I suppose it is Win 11) is GPT

You can choose between Win 10 and Win 11 by launching the boot menu during POST (F8?) IF your BIOS is set to boot as Legacy - MBR and UEFI - GPT.
It seems your system is configured to boot only as UEFI - GPT.
Win 11 requires a very specific BIOS configuration.
I recommend you to leave BIOS as it is. Don't change it.
You can modify the Win 10 drive from Legacy - MBR to UEFI - GPT. Easy task

Please clarify

The bios shows both drives but one is storage and the other boot and when i make changes they swap positions when it shows windows 10 drive as boot the system won't boot until i remove window 10 drive?

Click to expand...

Megahertz said:

zebal only MBR needs and can be set as active.

• Drive 0 (I suppose it is Win 10) is MBR
• Drive 1 (I suppose it is Win 11) is GPT

Click to expand...

Disk 1 is MBR also. The reason the computer will not boot from Disk 0 is because there is no FAT32 partition on it to boot from. If you look at the partitions on Disk 1 they are labelled as Primary Partitions with one of them marked as active. That means the disk is MBR. If disk 1 was GPT, then the partitions would be marked as Basic Data Partitions.

In order to make Disk 0 bootable on what is apparently this UEFI system, the 100MB System Reserved Partition needs to be reformatted as FAT32 and a BCD added to it. However, both disks are completely, 100% non-standard and should be converted to GPT to maintain compatibility with full version upgrades in the future. Disk 1 will probably convert OK using MBR2GPT, but disk 0 won't. Probably need a paid for 3rd party program to convert it to GPT.

If you have mixed MBR and GPT disks you must convert on of them to match the partition style (MBR or GPT) of the other. Otherwise you have to bypass boot priority with F12 (or F11 or F8 etc) while switcing on or restarting to boot into the non-default OS.

Well observed NavyLCDR. I suppose you concluded that drive 1, a NVMe is a MBR because it has the Fat32 partition set as active.

Is the current installation Legacy-MBR or UEFI-GPT?
Open Disk Manager. On top menu - View - Top - List disk

Megahertz said:

Well observed NavyLCDR. I suppose you concluded that drive 1, a NVMe is a MBR because it has the Fat32 partition set as active.

Click to expand...

I concluded that drive 1, an NVMe, is MBR because of the partition labels. The partitions are marked as "(Primary Partition)". That means the drive is MBR. If it was GPT, the partitions would be marked as "(Basic Data Partition)" or "(EFI System Partition)". To understand what is happening with MrKofax's computer we must understand some basic computer limitations (and debunk one commonly believed myth about booting in UEFI mode).

1. Legacy BIOS (or CSM) can only boot from an MBR disk. It cannot boot from a GPT disk.
2. UEFI mode must be used to boot directly from an NVMe SSD.
3. UEFI mode can boot from either MBR or GPT disks. UEFI mode does not require any partition to be marked as "Active" - it ignores the "Active" flag.
4. Most, but not all, computers require a FAT partition to boot from in UEFI mode. Usually FAT32.

Given the above limitations, MrKofax can boot from disk 0 in Legacy BIOS (CSM) mode, but probably not UEFI mode (because there is no FAT partition to boot in UEFI mode from).
MrKofax can boot from disk 1 in UEFI mode only because it is an NVMe disk and it does have a FAT partition to boot from.

The easy solution to MrKofax's problem of not being able to boot from disk 0 is to convert the existing NTFS System Reserved partition to FAT32 and put a UEFI compatible BCD on it.

Megahertz said:

Is the current installation Legacy-MBR or UEFI-GPT?
Open Disk Manager. On top menu - View - Top - List disk

Click to expand...

Your example is irrelevant to this thread and would cause further confusion to address it. However your example follows rule #1 above.

NavyLCDR said:

I concluded that drive 1, an NVMe, is MBR because of the partition labels. The partitions are marked as "(Primary Partition)". That means the drive is MBR. If it was GPT, the partitions would be marked as "(Basic Data Partition)" or "(EFI System Partition)".

Click to expand...

NavyLCDR this isn't always true.
It is true under Win 10 and Win 11.
It isn't true under Win 7 (my main OS)
All my drives are GPT and all partitions, under Win 7, except EFI and Recovery partitions, are labeled as "Primary Partition"


MrKofax your system is a mess.

• You have a NVMe that seems it was installed as UEFI-GPT (it has a 100MB FAT32 partition) and was converted to Legacy - MBR.
• I don't see a Recovery partition on the Win 10 and Win 11 drive. Did you disable them and deleted the partition?
• Your Win 10 drive has some useless partitions.

I suggest you convert both drives to UEFI-GPT
MrKofax what do you want to do?