From f5bbb5e33ffbeeae32c92ccefac831f5ab01488e Mon Sep 17 00:00:00 2001 From: Mounir IDRASSI Date: Mon, 3 Jul 2017 00:39:25 +0200 Subject: Documentation: Update Incompatibilities section to mention both Outpost Firewall or Outpost Security Suite and to point to corresponding ticket at Sourceforce. --- doc/html/Incompatibilities.html | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'doc/html/Incompatibilities.html') diff --git a/doc/html/Incompatibilities.html b/doc/html/Incompatibilities.html index e3226b88..06de7db0 100644 --- a/doc/html/Incompatibilities.html +++ b/doc/html/Incompatibilities.html @@ -62,12 +62,14 @@ 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).
-

Outpost Firewall 9.1

+

Outpost Firewall and Outpost Security Suite

-if Outpost Firewall 9.1 is installed with Proactive Protection enabled, the machine freezes completely for 5-10 seconds during the volume mount/dismount operation. This is caused by a conflict between Outpost System Guard option that protects "Active Desktop" objects and VeraCrypt waiting dialog displayed during mount/dismount operations.
+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/dismount operation. This is caused by a conflict between Outpost System Guard option that protects "Active Desktop" objects and VeraCrypt waiting dialog displayed during mount/dismount 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.
-- cgit v1.2.3