Issue with Dual Boot Setup - BitLocker Windows 10 + VeraCrypt Windows 10 on the same Disk

[Dared]

Hello!

I'm currently trying to set up a configuration with two Windows 10 instances. The first installation should be encrypted with BitLocker, and the second one with VeraCrypt.

Here was my expectation:

When I want to boot into the BitLocker Windows instance:
1. The Windows Boot Manager starts, and I select the BitLocker Windows instance.
2. The BitLocker Windows instance boots up.

When I want to boot into the VeraCrypt Windows instance:
1. The Windows Boot Manager starts, and I select the VeraCrypt Windows instance.
2. I enter the VeraCrypt password.
3. The VeraCrypt Windows instance boots up.

However, this is what actually happens:

When I want to boot into the BitLocker Windows instance:
1. I enter the VeraCrypt password.
2. The Recovery menu opens, and I enter the BitLocker Recovery Key.
3. The Windows Boot Menu opens, and I select the BitLocker Windows instance.
4. The BitLocker Windows instance boots up.

When I want to boot into the VeraCrypt Windows instance:
1. I enter the VeraCrypt password.
2. The Recovery menu opens, and I press F11 for "alternate operating system."
3. The Windows Boot Menu opens, and I select the VeraCrypt Windows instance.
4. The VeraCrypt Windows instance boots up.

The VeraCrypt Windows instance was configured with the settings "Normal => Encrypt the Windows system partition => Multi-Boot."

My hard drive partitioning is "EFI partition, BitLocker Windows instance, Recovery partition, VeraCrypt Windows instance."

Is there a way to adjust the system so that it functions as desired above, or is it not possible?

I appreciate any help you can provide!

[ledgeri]

What is your conclusion on the long term?

[Dared]

At some point, I gave up and used the second Windows installation without VeraCrypt encryption. According to ChatGPT, it should be possible to get this working with two separate EFI partitions, but I didn’t pursue that approach further:

Warning, the following might be AI nonsense!
Completely Separate Boot Paths (Best Practice)

Separate EFI System Partitions:

    Create two EFI partitions: one for BitLocker Windows, one for VeraCrypt Windows.

    Adjust UEFI boot entries so that:

        One UEFI entry boots directly into BitLocker-encrypted Windows.

        Another UEFI entry triggers VeraCrypt’s pre-boot authentication for the VeraCrypt-encrypted Windows.

Result:

You get a clean boot menu provided by your UEFI firmware (not the Windows Boot Manager), allowing clear separation:

    Select “BitLocker Windows” → Boots directly into BitLocker-protected Windows, no VeraCrypt screen, no recovery prompts.

    Select “VeraCrypt Windows” → VeraCrypt’s pre-boot authentication prompts for the password, then boots that system.

✅ Completely isolated bootloaders — no overlap or interference.
✅ No unexpected BitLocker recovery prompts (unless EFI partitions overlap or Secure Boot detects unauthorized changes).

[ledgeri]

Ohh, that is not good, i mean, your result...
Do you need to use your VC-password when loading the unecrypted windows?
Any ways, thanks for the reply! (First since i am registered)
I might will check out the dual EFI possibilities. Thanks for that idea!

[Dared]

I was able to completely remove VeraCrypt, so that there was no more password prompt.

I would really appreciate it if you shared your results here. If you manage to get it working, I might give it another try myself :).