From f48c21a54ba461c0356d5a9358ae7e441ab269c3 Mon Sep 17 00:00:00 2001 From: Mounir IDRASSI Date: Thu, 10 Aug 2023 01:27:57 +0200 Subject: Documentation: Update Windows build guide to mention Windows Test Mode and steps to avoid signature check failures --- doc/chm/VeraCrypt User Guide.chm | Bin 3164071 -> 3164333 bytes doc/html/CompilingGuidelineWin.html | 23 +++++++++++++++++------ 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/doc/chm/VeraCrypt User Guide.chm b/doc/chm/VeraCrypt User Guide.chm index 8161127c..33bf7435 100644 Binary files a/doc/chm/VeraCrypt User Guide.chm and b/doc/chm/VeraCrypt User Guide.chm differ diff --git a/doc/html/CompilingGuidelineWin.html b/doc/html/CompilingGuidelineWin.html index eb35541a..ec08af4f 100644 --- a/doc/html/CompilingGuidelineWin.html +++ b/doc/html/CompilingGuidelineWin.html @@ -1147,9 +1147,14 @@ Below are the procedure steps. Clicking on any of the link takes directly to the
  • This distribution package is damaged

    - On Windows 10 or higher you might get the error message above. It occurs, if the authenticode signature check fails.
    - Currently this check works incorrectly, so it might fail every time. A workaround is to skip the verification.
    - Please see https://sourceforge.net/p/veracrypt/discussion/technical/thread/83d5a2d6e8/ for further details. + On Windows 10 or higher you might get the error message above. In order to avoid this, you will need to:
    + + Please see https://sourceforge.net/p/veracrypt/discussion/technical/thread/83d5a2d6e8/#db12 for further details.
    +
    + Another approach is to disable the signature verification in the VeraCrypt code. This should be done only for testing purposes and not for production use:
    1. Open the file "src/Common/Dlgcode.c" @@ -1175,10 +1180,16 @@ Below are the procedure steps. Clicking on any of the link takes directly to the
  • - Certificate failure
    + Driver Installation Failure during VeraCrypt Setup from Custom Builds

    Windows validates the signature for every driver which is going to be installed.
    - This validation can fail during the installation process of VeraCrypt for two reasons: + For security reasons, Windows allows only drivers signed by Microsoft to load.
    + So, when using a custom build:
    + + Potential Causes for Installation Failure under "Test Mode":
    1. The certificate used for signing is not trusted by Windows
      @@ -1194,7 +1205,7 @@ Below are the procedure steps. Clicking on any of the link takes directly to the Go to the top menu "Digital Signatures". Her you will find two signatures in the Signature list
      2. Check both by double clicking on it. If the headline says "The certificate in the signature cannot be verified", the corresponding signing certificate was not imported correctly.
      - Click on "View Certificate" and then on "Install Certificate..." to import the certificate to your certificate storage. For the Root certificates, you may need to choose "Place all certificates in the following store", and select the "Trusted Root Certification Authorities" store.
      + Click on "View Certificate" and then on "Install Certificate..." to import the certificate to Local Machine certificate storage. For the Root certificates, you may need to choose "Place all certificates in the following store", and select the "Trusted Root Certification Authorities" store.

    -- cgit v1.2.3