This project has moved and is read-only. For the latest updates, please go here.

Windows 1.18 System Encryption Questions

Topics: Technical Issues
Aug 19, 2016 at 11:51 AM

thanks for the new version 1.18.

I've done Pre-Test for system encryption and noticed the following things:
  • No verification if Rescue Folders are written correctly on USB (like GTP's CD Check)
  • No hint on Secure Boot before Pre-Test (fails on Pre-Test when Secure Boot enabled)
  • Boot order issue (Windows before Veracrypt) Anything you can do about it?
Doing full encryption now, I'll report how it's working.
Aug 19, 2016 at 2:41 PM

Windows loader sometime changes the order.

To fix boot menu there are several possibility:
  1. Some BIOS can have option - lock boot menu.
  2. VeraCrypt has DcsBml driver to block boot menu modification after successful login.
Secure Boot can be tested in setup wizard before system encryption. We postponed the modification. Too complex release.
Aug 20, 2016 at 9:23 AM
Edited Aug 20, 2016 at 9:28 AM
Hi MinIsMin,

VeraCrypt enforce the verification of Rescue Disk content on the USB key if you don't check "Skip Rescue Disk Verification". So, if the Rescue Disk zip was not correctly decompressed on a USB key that is connected to the machine, the wizard will refuse to continue with the error shown in the screenshot below.

Can you please clarify what led you to believe that VeraCrypt doesn't check the Rescue Disk content on the USB key?

For the other 2 questions, Alex has already answered.

Aug 20, 2016 at 9:36 AM
Thank you for your fast responses.
  • I'm currently in the encryption state so I can't look at the box "Skip Rescue Disk Verification".
    Maybe I selected the box and forgot it.
  • My BIOS doesn't a lock option but it seems working now
  • t to the detection of Secure Boot