this post was submitted on 13 Jul 2026
248 points (97.7% liked)

Programmer Humor

32245 readers
1553 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] artwork@lemmy.world 1 points 1 hour ago* (last edited 1 hour ago)

Windows never touched the main EFI entry in my cases, even at updating it from 10 to 11, and I clarified it 3 times.

With a few Google queries we may find it mentioned, yet I've just found a weak one at this moment:

If you are booting with Windows, you should simply be aware of the problem, because you can easily overcome it by temporarily changing the type code of the non-Windows ESP(s) if you run into problems. Note that Windows will boot just fine on a disk with multiple ESPs; it's just the installer that chokes on such disks.

Source

Some documentations found mentioned relatively similar:

The only Microsoft supported workaround for booting multiple installations of Windows in a uEFI environment is to use a dual boot configuration. This will make use of a single ESP and one MSR while still allowing the user to choose to boot to an installation on disk 1 or disk 2.

Source