El Don

Thank you for investigating this. I will wait for a fix, In the meantime I will use the UEFI boot menu to boot Windows directly.

Thank you again, Package versions: shim-x64-16.1-5.x86_64 grub2-efi-x64-2.12-58.fc44.x86_64 grub2-common-2.12-58.fc44.noarch SecureBoot: enabled Also worth noting, a potentially related issue was filed last week on rhboot/shim — issue #795 — reporting that Fedora 44's shim-x64-16.1-5 ships with IMAGE_DLLCHARACTERISTICS_NX_COMPAT not set on all shim binaries, which specifically affects Lenovo hardware. This may be related to the broken EFI state during DCS chainloading under Secure Boot.

Thank you for the suggestion. I actually tried this exact entry at the beginning of the troubleshooting, The result is the same — password accepted, screen goes black for less than a second, reboots back to GRUB. Based on your diagnostic statement, this confirms the issue is generic to Secure Boot + GRUB/shim chainloading.

Thank you for the detailed response. Here are the results of all the tests: 1. DcsProp content (current) <?xml version="1.0" encoding="utf-8"?> <VeraCrypt> <configuration> <config key="PasswordType">0</config> <config key="PasswordMsg">Password: </config> <config key="PasswordPicture">login.bmp</config> <config key="HashMsg">(0) TEST ALL (1) SHA512 (2) WHIRLPOOL (3) SHA256 (4) BLAKE2S (5) STREEBOG Hash: </config> <config key="Hash">1</config> <config key="HashRqt">0</config> <config key="PimMsg">PIM...

I have a dual boot setup with Windows 11 encrypted with veracrypt (VeraCrypt 1.26.24 full system encryption) and Fedora 44 on a Lenovo laptop with NVMe drive. Problem: After entering the correct password, VeraCrypt decrypts successfully but then freezes or reboots back to the bootloader instead of booting Windows. What works: Booting VeraCrypt directly from UEFI boot menu works perfectly every time Running efibootmgr --bootnext <windows-entry>in fedora then reboot works perfectly What fails: GRUB...