Windows 10 system encryption - black screen after entering password in...
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hello,
very short - I guess the bootloader configuration does not work properly. I get a blackscreen after password-input.
Iam running a fresh Win-10 at version 10.0.18362 in UEFI mode.
My mainboard is a Gigabyte one: Z97P-D3
So my problem is: I have tried 3 different versions of VeraCrypt and followed several tips I could find in the foums. Here the results:
1.23 Hotfix 2: I passed the test, could fully encrypt but then after encryption was done, I could normaly enter the password but then I saw the windows circles moving and after 20 seconds there was just only black. My screen told me: signal lost.
1.24 Beta 2: Same problem but I noticed reboot worked during encryption, but after successful encryption I had a black screen again.
1.24 Beta 5: At pretest-boot I can enter password but i get to my dear black screen. Unable to boot windows.
I used the beta-versions because I was told they include some fixes for some uefi problems with hp and asus/acer?. So maybe there is some help for gigabyte setup.
My HDD has 4 partitions.
1x 500MB - Winows default recovery
1x 200GB - Windows Installation
1x 100MB - Windows default boot loader (EFI & VeraCrypt loader)
1x 700GB - unecnrypted partition for some games etc.
So what I tried and found out:
VeraCrypt (VC) creates its own folder with config file on EFI partition and replaces bootx64.efi in EFI\boot\bootx64.efi with its own version.
So I followd some guides, where you replace bootmgfw.efi in microsoft\boot with veracrypt dcs loader and set a postexec in the config to the original bootmgfw_ms.efi...
I also restored original bootx64.efi of windows because I also can boot VeraCrypt loader from bios/it even works without that replacement. I did some changes with bcdedit and tried some combinations pointing to bootx64 or bootmgfw and did the same procedure in the VC-config file. Okay this might be a crazy procedure but I tried most things I could imagine. And I could not figure out why it has worked sometimes and why it stoped work. I also had a szenario where I was in a loop: enter the password, success, enter again pw.
Of course also Secure-Boot is disabled in bios.
So maybe you have some ideas how to fix this. Iam really sure there is something wrong with the co-op config of VeraCrypt and MS-Win Bootloader. (Running newest win 10 at this moment) . It feels like it cannot initialize corret boot of windows.
If you need some more detailed data - I will provide.