Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange behavior after updating Windows 10 #7

Open
douliah opened this issue Aug 24, 2018 · 0 comments
Open

Strange behavior after updating Windows 10 #7

douliah opened this issue Aug 24, 2018 · 0 comments

Comments

@douliah
Copy link

douliah commented Aug 24, 2018

Hi,

I encountered a strange behavior regarding my hard drive encrypted with VeraCrypt.

First of all, please let me explain the situation: I have one internal SSD with Windows 10 encrypted with VeraCrypt, and another unencrypted external SSD with Windows10 on it. After upgrading Windows 10 on my unencrypted SSD, I rebooted and choosed to use my encrypted SSD. The prompt for VeraCrypt appeared as normal (with "password OK"), but after I got a BSOD with the message "Unable to boot error: 0x000000F".

I tried to decrypt the partition using my external SSD with VeraCrypt tool on the encrypted SSD, but VeraCrypt seems to not recognize the encryption.

After that, I tried to use VeraCrypt rescue disk, but I made a big mistake on it, as I wanted to repair the bootloader from the rescue disk prompt ("option : m"), but I choosed the MBR of the rescue disk itself...as such, my rescue disk is not working anymore....

Do you have any clue regarding this particular situation?

EDIT : I was able to boot on my VeraCrypt rescue disk again. I tried many restoration options, and even a decrypt process (which was taking 2hours with a final message : "Decrypt ok"). However, it seems that I still could not boot on Windows...instead, a new error messaged is displayed: "Error 0x000000e"

Thanks,

Douliah

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant