GetEfiBootDeviceNumber error on reencryption
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
I'm hoping someone can help me with this one.
My existing encrypted Windows 10 system partition with UEFI is installed on an old SSD. I decrypted the content of the drive and copy them to a new unencrypted SSD. I fix up the UEFI partition so that the new SSD can boot without issues.
When I run VeraCrypt to encrypt the partition again, I run into this error:
The requested system device cannot be found.
Source veracrypt:elevator::GetEfiBootDeviceNumber:617
Anyone know how to fix this? Is it possible or system drives just can't be upgraded ...
After messing around with it for a day, I found a work around for this problem.
I decided to convert the new SSD to MBR and not use EFI, and I was able to re-encrypt the new drive. After I got it working, I tested using GPT EFI again on another HDD drive, but the system encryption worked on the HDD. I'm not sure if it's because if the new SSD is nvme or not. I'm tempted to try again with EFI on the new SSD, but after spending so much time on it, I'll save that for the next OS upgrade!
Final update. I decided to try using EFI again on the new SSD. I did the same steps as before (create an unencrypted partition and copy the old decrypted OS content over), except this time, instead of copying the old EFI that containing the VC boot loaders, I created a new EFI partition and formatted it blank -- copying VC boot loaders might have trigger the GetEfiBootDeviceNumber error. I rebuild the Windows BCD on the new EFI and boot into Windows.
Now, I found something interesting and maybe consider a bug. Upon booting into Windows, VeraCrypt automatically created its boot loader in the EFI as well as overwritten Windows boot manager, even though at this time, the system is not encrypted. If I reboot, VeraCrypt asks for a password and after entering the old password, authentication is successful but decryption fails because the content is not encrypted. I need to boot into Windows recovery to rebuild the EFI again. When I get back into Windows this time, I encrypt the sys partition and that seems to work now.