Deleted Windows Bootloader on Encrypted Partition...tips on recovering?
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hi guys,
I was messing around with my Window's boot manager after encrypting my partition with Veracrypt. Long story short, it's gone. I can't boot up Windows after unlocking the partition with Veracrypt's bootloader. I've attempted to repair the bootfile, but I'm unable to since the Window's partition is encrypted.
I did not make a rescue-disk at the time of encryption. All I have is my password to the partition. However, I do have my laptop set up to dual boot Ubuntu, on which I've tried to mount the Window's partition with no avail. I get an error that states, "No such file or directory: /sys/block/sda/sda/start VeraCrypt::File::Open:232"
Any help would be greatly appreciated.
Update: I've managed to mount the drive. Currently searching for ways to recreate the Window's bootmanager for UEFI without having to open a command prompt. I do have a backup bootmgr file.
Update: Messed something up and now I can't mount the Window's partition because it's hibernated...
Your system is EFI. Right?
Does EFI system partion remain correct?
To start VeraCrypt loader you can execute from ESP EFI\VeraCrypt\DcsBoot.efi (from external efi shell or rEFInd or grub)
Also you can mount VeraCrypt volume from Windows PE and restore boot loader via bcdboot tool.
Here is what occurs when I try to run bcdboot
A:\ is my mounted VeraCrypt volume
b:\ is the letter corresponding to the ESP
Could this be occurring because I'm running bcdboot from a Windows 10 OS rather than a Windows 8 (the OS of the encrypted partition).
Last edit: Max G 2017-01-25
@Alex
Yes, it's EFI. The EFI system partition is correct. I have fixed the EFI partition, however, the Windows Bootloader itself is corrupted (on the C:\ drive I believe). I get an error stating that the winloader.efi not found.
Can you elaborate on mounting the VeraCrypt volume from Windows PE? I'm not sure how that would work. Currently, I'm able to mount the partition on a separate Windows 10 OS, but I'm unable to correctly modify the boot files residing on the encrypted partition (I think).
@Alex
So what I'm getting stuck on is the bcdboot part. http://woshub.com/how-to-repair-uefi-bootloader-in-windows-8/
If I boot up a Windows Repair disk to run this command, I'm unable to create the BCD store because my C:\Windows is encrypted.
If I run bcdboot on the Windows 10 OS with the encrypted partition mounted, I get a "BFSVC Error: Failed to set element application device. Stats = [c00000b]"
Last edit: Max G 2017-01-25
In portable mode VeraCrypt can work from Windows PE disk.(unzip it to repair disk folder. Rename modules "xxx-x64" to "xxx")
Probably the problem is in setup correct BCD.
It is neccessary to edit BCD on ESP. Use BOOTICE tool to select correct location of winload.efi (disk and partition)
I've managed to mount the drive in Windows PE, but I'm still getting the same error when trying to run bcdboot (BFSVC Error: Failed to set element application device.)
Last edit: Max G 2017-01-25
FIXED. Thanks @Alex for the Windows PE tip. I ended up importing a backup I made of my BCD to the ESP and I'm able to boot up again!
How did you mount the VeraCrypt volume in the Win PE environment in order to fix the BCD? I have a similar issue, but I couldn't manage to execute the VeraCrypt EFI file to decrypt and mount the drive in WinPE. It said "No such interface supported"