Unable to boot - Start \EFI\Microsoft\Boot\Bootmgfw.efi - Unsupported
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Veracrypt 1.19 - Acer swift 3 - Windows 10 Home - single boot - secure boot disabled
Veracrypt boot test OK
Proceeded with full partition encryption. After reboot, it would not boot and kept running windows diagnostics in a reboot loop.
I then proceeded to boot with the rescue drive and attempt a permanent decryption, which completede successfully. Now when I boot, it still asks for password. But when I provide the right password, it still cannot proceed:
Enter password:
PIM (Leave empty for default):
Authorizing...
Sucess
start 122683392 len 0
Start \EFI\Microsoft\Boot\Bootmgfw.efi - Unsupported
Since I have used the rescue boot to permanently decrypt my partition, I now should be able to remove the veracrypt bootloader to boot normally, but even if I choose to remove veracrypt from boot menu (option z on the rescue boot), it still asks for a password and the subsequent error message remains.
Please help.
Fixed this by running chkdsk c: /F followed by bcdboot c:\windows /s c: from the recovery console on the recovery partition.
1.19 recovery has bug. Use 1.20b2
That would explain why I now have some corrupted windows files. Trying to use the DISM tool to repair windows, as I don't want to have to reinstall windows.
By the way, this seems like quite a serious malfunction in the 1.19 release. This should probably be fixed also in the release to avoid corrupted user data.
Last edit: tskjot 2017-01-04