mmortal03

Hi Dave, After upgrading Grub2Win from the older version 2.3.x (2.3.8.6) to the newer version 2.4.x (2.4.3.3) -- which I'm aware added the new boot method of BIOS Direct Boot -- the Grub menu entry for Windows Boot Manager doesn't work. (I'm on a legacy BIOS/MBR laptop.) After selecting Windows Boot Manager, I get this very common error: Windows Boot Manager Windows failed to start. [...] File: \Boot\BCD Status: 0xc000000f Info: The Boot Configuration Data for your PC is missing or contains errors....

Hi Drummer, After upgrading Grub2Win from the older version 2.3.x (2.3.8.6) to the newer version 2.4.x (2.4.3.3) -- which I'm aware added the new boot method of BIOS Direct Boot -- the Grub menu entry for Windows Boot Manager doesn't work. (I'm on a legacy BIOS/MBR laptop.) After selecting Windows Boot Manager, I get this very common error: Windows Boot Manager Windows failed to start. [...] File: \Boot\BCD Status: 0xc000000f Info: The Boot Configuration Data for your PC is missing or contains errors....

There are a couple of ways around this issue. One way is to use a dummy plug. That's the method I prefer. Another way, which is a workaround, is to "break" the ACPI lid driver by installing a non-functional driver in its place. See here (and scroll down that thread to see an example of a dummy plug): https://superuser.com/a/1504519/228898

Yep, that definitely fixes it on both Mint and Debian! To be sure, the grub2win GUI still shows all-caps (which might confuse some people) but the correct case is being sent to the boot init logic. Looks like it's time to donate! Thanks!

Here is the diagnose.7z file.

I can confirm that it's the same issue on the Windows/Debian machine: grub2win is detecting and specifying an all-uppercase UUID, but on Linux, the partition UUID is properly seen by gparted as all lowercase. The boot init logic simply breaks in particular places when it is given an all-caps UUID (whenever then actual UUID is all lowercase). I also did some googling, and for ext4 I believe the standard is all lowercase for the UUID. I just made a "diagnose.7z" on the Windows/Debian laptop, and have...

Dave, looking at it with fresh eyes, I've finally figured out what's going wrong! It's definitely a bug. This might need to be fixed in grub2win rather than in Linux Mint (and Debian), but you will need to advise. What's happening in the latter case (where it gets stuck for 30 seconds) is that grub2win is incorrectly detecting and specifying an all-caps UUID for the boot init logic, but some portion of the initramfs scripts in Linux Mint is case sensitive -- and my UUID, according to Linux, is all...