Menu

Unexpected VeraCrypt Bootloader

2023-04-17
2023-04-19
  • antonio esposito

    Scenario:
    Veracrypt 1.24 update 7 64bit;
    -System disk (SSD) with a windows 7 partition and a data partition, fully encrypted;
    -three (3) data disks, obviously non-booting, fully encrypted
    Al of the above disks are connected thru the SATA lines.

    everything is OK. For maximum security I extract the SSD and take it with me when I leave home.

    problem: I get back home, turn on the PC forgetting to re-insert the SSD and... the VeraCrypt boot screen appears (!).
    Where does it came from? I believe the only disk with the VC bootloader is the system disk... which is not connected. Maybe fully encrypting a disk installs the VC bootloader on it? Which would be the purpose?

    To be precise, there are no other volumes (disk / USB drive / CD / else) connected to the PC.
    Thanx for any idea,
    Antonio

     
  • antonio esposito

    Hi again,

    Investigating I got some additional info:

    I tried to boot up the PC by connecting the 3 data disks one at a time: the UFO boot record is located on the second magnetic disk, which is the last I have added and therefore the last I encrypted.

    So,

    1. why Veracrypt has written its boot record on a data disk? (and only this one)
    2. I am going to back up the MBR on this disk and then replace it with a standard MBR (using something like MiniTool Partition Free); is there anything wrong in this procedure?

    Greetings

     

Log in to post a comment.

MongoDB Logo MongoDB