Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost full, I have no possibility of installing other OSes ;-( This 100 MB partition being ridiculously small and not expandable, it does not also cannot benefit from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

Hello,
A new problem occurs when we succeed in forcing the activation of the EFI partition on the Debian disk and the second Windows disk present also has its own EFI partition containing its boot loader:
Under Debian active EFI partitions are read and write protected for security reasons.
But when you have 2 EFI partitions on a system, only the mounted and therefore active partition is read and write protected.
So if I boot on Debian, the Windows EFI partition is not read/write protected. And if I start Windows, it's the Debian EFI partition that won't be read and write protected.
It would therefore be necessary for all the EFI partitions present on the different disks of a computer to be mounted, even if only one of these EFI partitions is needed to boot the OS you are working on, to make all EFI partitions on this PC are read and write protected.
Best regards.
Philippe

Hello,

The problem persists under Debian 13. This bug, which was reported two years ago, has not been addressed ?

Can we hope that one day someone will take care of this ?

This problem is very annoying if you extract the non-Debian disk containing the boot/efi, and if this disk fails/dies, etc., you lose the Debian boot loader and Debian no longer works ;-(

Regards.