This project has moved. For the latest updates, please go here.

Encrypt whole system in XP issue

Topics: Technical Issues
Apr 20, 2016 at 10:34 AM
Hello,

I encrypted the whole system, created the rescue disc, then system didn't load because of "wrong password". (the password is correct), so put the rescue disc, system loaded and appeared, the attached message.
So, i changed the password and created second rescue boot disc.
Again system didn't boot because of "wrong password" exactly as the first time, so i used again the new rescue disc and here is that message again every time i boot.
http://blog.v-p.ro/?p=251
(i uploaded as is as text is not selectable)
Apr 20, 2016 at 1:32 PM
Check for install products that are not compatible with VeraCrypt that can cause this issue. Sometimes other software can bundle the incompatible software as part of their installation of their product.

https://veracrypt.codeplex.com/wikipage?title=Incompatibilities
Apr 20, 2016 at 2:05 PM
Thanks for the answer, however it doesn't help - i encrypt AES only so, issue doesn;t apply.
Apr 20, 2016 at 2:28 PM
XP has vulnerabilities that M$ will never patch. Newer Windows may well have loads of other vulnerabilities, but there is a chance that M$ will patch those. If you can't run a supported Windows OS, then migrate to Linux, there are excellent options in that world (and others).

XP is definitely vulnerable, no-one should be using it at all, unless they are paying huge sums to M$ for continued support OR they run the machine completely stand alone.
Coordinator
Apr 20, 2016 at 2:28 PM
This strange since before the encryption is performed, a test boot is performed and obviously it succeeded since your system was encrypted.

The only explanation is that something in your PC changes the volume header stored on the disk and that's why the password verification fails.
It succeeds with the Rescue Disk since it contains a copy of the volume header that was not tampered with.

The fact that even changing the password doesn't help means that the volume header on the disk keeps being modified by something on your machine...this is not normal at all and VeraCrypt can not do anything to prevent it.

Try unintalling any software or driver that may perform such disk modifications and during your tests, use the Rescue Disk repair menu to restore the volume header and VeraCrypt bootloader before booting to see if the error persists.

Can you share details about the type of software that you have on your machine?
Apr 20, 2016 at 3:28 PM
Thank you for the answer. Please have a look at programs installed .
http://blog.v-p.ro/?p=256