doc/html/en/Incompatibilities.html
Documentation Incompatibilities
Note: The issue described below does not affect you if you use a non-cascade encryption algorithm (i.e., AES, Serpent, or Twofish).* The issue also does not affect you if you do not use system encryption (pre-boot authentication).
Acresso FLEXnet Publisher activation software, formerly Macrovision SafeCast, (used for activation of third-party software, such as Adobe Photoshop) writes data to the first drive track. If this happens when your system partition/drive is encrypted by VeraCrypt, a portion of the VeraCrypt Boot Loader will be damaged and you will not be able to start Windows. In that case, please use your VeraCrypt Rescue Disk to regain access to your system. There are two ways to do so:
For information on how to use your VeraCrypt Rescue Disk, please see the chapter VeraCrypt Rescue Disk.
Possible permanent solution : decrypt the system partition/drive, and then re-encrypt it using a non-cascade encryption algorithm (i.e., AES, Serpent, or Twofish).*
Please note that this not a bug in VeraCrypt (the issue is caused by inappropriate design of the third-party activation software).
If Outpost Firewall or Outpost Security Suite is installed with Proactive Protection enabled, the machine freezes completely for 5-10 seconds during the volume mount/unmount operation. This is caused by a conflict between Outpost System Guard option that protects "Active Desktop" objects and VeraCrypt waiting dialog displayed during mount/unmount operations.
A workaround that fixes this issue is to disable VeraCrypt waiting dialog in the Preferences: use menu "Settings -> Preferences" and check the option "Don't show wait message dialog when performing operations".
More information can be found at https://sourceforge.net/p/veracrypt/tickets/100/
* The reason is that the VeraCrypt Boot Loader is smaller than the one used for cascades of ciphers and, therefore, there is enough space in the first drive track for a backup of the VeraCrypt Boot Loader. Hence, whenever the VeraCrypt Boot Loader is damaged, its backup copy is run automatically instead.
See also: Known Issues & Limitations, Troubleshooting