diff options
| author | Helmut K. C. Tessarek <tessarek@evermeet.cx> | 2025-01-31 23:18:26 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-31 23:18:26 +0100 |
| commit | 498dff9013d18e5978ab77c14ea2b2d0229603a4 (patch) | |
| tree | 7f172f9c2945691ac9b1fb08f963a2263fd6942f /doc | |
| parent | c71fa14dc09fd7f31282f6ce4fdf3db547b9b827 (diff) | |
| download | VeraCrypt-498dff9013d18e5978ab77c14ea2b2d0229603a4.tar.gz VeraCrypt-498dff9013d18e5978ab77c14ea2b2d0229603a4.zip | |
refactor: use the term unmount instead of dismount (#1478)
* refactor: use UNMOUNT instead of DISMOUNT in code
This change updates the term DISMOUNT in constants to UNMOUNT.
Other occurrences (e.g. variable names) are left alone for now.
* refactor(ui): use unmount instead of dismount
This change updates the GUI text and replaces dismount with unmount.
* docs: update term dismount -> unmount
* refactor(cmdline): add unmount
This change adds an argument 'unmount' for command line usage, while
trying to deprecate the old disnount argument.
The current dismount argument/flag will still work to not introduce
a breaking change.
* docs: mention that /dismount is deprecated
This change fixes the shorthand version of the argument /unmount
It also adds back the info for /dismount and that it is deprecated.
Diffstat (limited to 'doc')
32 files changed, 106 insertions, 102 deletions
diff --git a/doc/chm/VeraCrypt.hhc b/doc/chm/VeraCrypt.hhc index 57e101b2..3c2223c7 100644 --- a/doc/chm/VeraCrypt.hhc +++ b/doc/chm/VeraCrypt.hhc @@ -98,4 +98,4 @@ <LI> <OBJECT type="text/sitemap"> - <param name="Name" value="Normal Dismount vs Force Dismount "> - <param name="Local" value="Normal Dismount vs Force Dismount.html"> + <param name="Name" value="Normal Unmount vs Force Unmount "> + <param name="Local" value="Normal Unmount vs Force Unmount.html"> </OBJECT> diff --git a/doc/html/Beginner's Tutorial.html b/doc/html/Beginner's Tutorial.html index c39ee596..531a71c2 100644 --- a/doc/html/Beginner's Tutorial.html +++ b/doc/html/Beginner's Tutorial.html @@ -190,5 +190,5 @@ You can copy files (or folders) to and from the VeraCrypt volume just as you wou Note that VeraCrypt never saves any decrypted data to a disk – it only stores them temporarily in RAM (memory). Even when the volume is mounted, data stored in the volume is still encrypted. When you restart Windows or turn off your computer, the volume - will be dismounted and all files stored on it will be inaccessible (and encrypted). Even when power supply is suddenly interrupted (without proper system shut down), all files stored on the volume will be inaccessible (and encrypted). To make them accessible + will be unmounted and all files stored on it will be inaccessible (and encrypted). Even when power supply is suddenly interrupted (without proper system shut down), all files stored on the volume will be inaccessible (and encrypted). To make them accessible again, you have to mount the volume. To do so, repeat Steps 13-18.</p> -<p>If you want to close the volume and make files stored on it inaccessible, either restart your operating system or dismount the volume. To do so, follow these steps:<br> +<p>If you want to close the volume and make files stored on it inaccessible, either restart your operating system or unmount the volume. To do so, follow these steps:<br> <br> @@ -197,3 +197,3 @@ Note that VeraCrypt never saves any decrypted data to a disk – it only sto Select the volume from the list of mounted volumes in the main VeraCrypt window (marked with a red rectangle in the screenshot above) and then click -<strong>Dismount </strong>(also marked with a red rectangle in the screenshot above). To make files stored on the volume accessible again, you will have to mount the volume. To do so, repeat Steps 13-18.</p> +<strong>Unmount </strong>(also marked with a red rectangle in the screenshot above). To make files stored on the volume accessible again, you will have to mount the volume. To do so, repeat Steps 13-18.</p> <h2>How to Create and Use a VeraCrypt-Encrypted Partition/Device</h2> diff --git a/doc/html/Command Line Usage.html b/doc/html/Command Line Usage.html index c463b04c..004eccc8 100644 --- a/doc/html/Command Line Usage.html +++ b/doc/html/Command Line Usage.html @@ -57,3 +57,3 @@ <td> -<p>It must be followed by a parameter indicating the file and path name of a VeraCrypt volume to mount (do not use when dismounting) or the Volume ID of the disk/partition to mount.<br> +<p>It must be followed by a parameter indicating the file and path name of a VeraCrypt volume to mount (do not use when unmounting) or the Volume ID of the disk/partition to mount.<br> The syntax of the volume ID is <strong>ID:XXXXXX...XX</strong> where the XX part is a 64 hexadecimal characters string that represent the 32-Bytes ID of the desired volume to mount.<br> @@ -76,3 +76,3 @@ You can also specify the Volume ID of the partition/device-hosted volume to moun <td><em>/beep</em> or <em>/b</em></td> -<td>Beep after a volume has been successfully mounted or dismounted.</td> +<td>Beep after a volume has been successfully mounted or unmounted.</td> </tr> @@ -84,4 +84,8 @@ You can also specify the Volume ID of the partition/device-hosted volume to moun <tr> +<td><em>/unmount</em> or <em>/u</em></td> +<td>Unmount volume specified by drive letter (e.g., /u x). When no drive letter is specified, unmounts all currently mounted VeraCrypt volumes.</td> +</tr> +<tr> <td><em>/dismount</em> or <em>/d</em></td> -<td>Dismount volume specified by drive letter (e.g., /d x). When no drive letter is specified, dismounts all currently mounted VeraCrypt volumes.</td> +<td>Deprecated. Please use /unmount or /u.</td> </tr> @@ -89,3 +93,3 @@ You can also specify the Volume ID of the partition/device-hosted volume to moun <td><em>/force</em> or <em>/f</em></td> -<td>Forces dismount (if the volume to be dismounted contains files being used by the system or an application) and forces mounting in shared mode (i.e., without exclusive access).</td> +<td>Forces unmount (if the volume to be unmounted contains files being used by the system or an application) and forces mounting in shared mode (i.e., without exclusive access).</td> </tr> @@ -316,3 +320,3 @@ If it is followed by <strong>n</strong> or <strong>no</strong>: the password dia <p>veracrypt /q /v d:\myvolume</p> -<p>Dismount a volume mounted as the drive letter <em>X</em> (the main program window will not be displayed):</p> +<p>Unmount a volume mounted as the drive letter <em>X</em> (the main program window will not be displayed):</p> <p>veracrypt /q /d x</p> diff --git a/doc/html/Documentation.html b/doc/html/Documentation.html index 9f6f6587..db4969bf 100644 --- a/doc/html/Documentation.html +++ b/doc/html/Documentation.html @@ -61,3 +61,3 @@ </li></ul> -</li><li><strong><a href="Normal%20Dismount%20vs%20Force%20Dismount.html">Normal Dismount vs Force Dismount</a></strong> +</li><li><strong><a href="Normal%20Unmount%20vs%20Force%20Unmount.html">Normal Unmount vs Force Unmount</a></strong> </li><li><strong><a href="Avoid%20Third-Party%20File%20Extensions.html">Avoid Third-Party File Extensions</a></strong> diff --git a/doc/html/FAQ.html b/doc/html/FAQ.html index e310f3e8..df1bfe8d 100644 --- a/doc/html/FAQ.html +++ b/doc/html/FAQ.html @@ -229,3 +229,3 @@ VeraCrypt volumes</a> are independent of the operating system. You will be able <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> -Before you unplug or turn off the device, you should always dismount the VeraCrypt volume in VeraCrypt first, and then perform the '<em style="text-align:left">Eject</em>' operation if available (right-click the device in the '<em style="text-align:left">Computer</em>' +Before you unplug or turn off the device, you should always unmount the VeraCrypt volume in VeraCrypt first, and then perform the '<em style="text-align:left">Eject</em>' operation if available (right-click the device in the '<em style="text-align:left">Computer</em>' or '<em style="text-align:left">My Computer</em>' list), or use the '<em style="text-align:left">Safely Remove Hardware</em>' function (built in Windows, accessible via the taskbar notification area). Otherwise, data loss may occur.</div> @@ -478,5 +478,5 @@ documentation</a>.</div> <br style="text-align:left"> -<strong style="text-align:left">Do I have to dismount VeraCrypt volumes before shutting down or restarting Windows?</strong></div> +<strong style="text-align:left">Do I have to unmount VeraCrypt volumes before shutting down or restarting Windows?</strong></div> <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> -No. VeraCrypt automatically dismounts all mounted VeraCrypt volumes on system shutdown/restart.</div> +No. VeraCrypt automatically unmounts all mounted VeraCrypt volumes on system shutdown/restart.</div> <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> @@ -488,3 +488,3 @@ No. VeraCrypt automatically dismounts all mounted VeraCrypt volumes on system sh Partitions/drives</a> may be better as regards performance. Note that reading and writing to/from a file container may take significantly longer when the container is heavily fragmented. To solve this problem, defragment the file system in which the container - is stored (when the VeraCrypt volume is dismounted).</div> + is stored (when the VeraCrypt volume is unmounted).</div> <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> diff --git a/doc/html/Hibernation File.html b/doc/html/Hibernation File.html index cc0888f1..0641c06c 100644 --- a/doc/html/Hibernation File.html +++ b/doc/html/Hibernation File.html @@ -46,3 +46,3 @@ <p>When a computer hibernates (or enters a power-saving mode), the content of its system memory is written to a so-called hibernation file on the hard drive. You can configure VeraCrypt (<em>Settings</em> > -<em>Preferences</em> > <em>Dismount all when: Entering power saving mode</em>) to automatically dismount all mounted VeraCrypt volumes, erase their master keys stored in RAM, and cached passwords (stored in RAM), if there are any, before a computer hibernates +<em>Preferences</em> > <em>Unmount all when: Entering power saving mode</em>) to automatically unmount all mounted VeraCrypt volumes, erase their master keys stored in RAM, and cached passwords (stored in RAM), if there are any, before a computer hibernates (or enters a power-saving mode). However, keep in mind, that if you do not use system encryption (see the chapter diff --git a/doc/html/Hidden Volume.html b/doc/html/Hidden Volume.html index 56f38e2b..bb415d36 100644 --- a/doc/html/Hidden Volume.html +++ b/doc/html/Hidden Volume.html @@ -48,3 +48,3 @@ It may happen that you are forced by somebody to reveal the password to an encry The principle is that a VeraCrypt volume is created within another VeraCrypt volume (within the free space on the volume). Even when the outer volume is mounted, it should be impossible to prove whether there is a hidden volume within it or not*, because free - space on <em style="text-align:left">any </em>VeraCrypt volume is always filled with random data when the volume is created** and no part of the (dismounted) hidden volume can be distinguished from random data. Note that VeraCrypt does not modify the file + space on <em style="text-align:left">any </em>VeraCrypt volume is always filled with random data when the volume is created** and no part of the (unmounted) hidden volume can be distinguished from random data. Note that VeraCrypt does not modify the file system (information about free space, etc.) within the outer volume in any way.</div> diff --git a/doc/html/Incompatibilities.html b/doc/html/Incompatibilities.html index 4c9e4bce..a87ed56d 100644 --- a/doc/html/Incompatibilities.html +++ b/doc/html/Incompatibilities.html @@ -66,3 +66,3 @@ Please note that this not a bug in VeraCrypt (the issue is caused by inappropria <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> -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.</div> +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.</div> <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> diff --git a/doc/html/Introduction.html b/doc/html/Introduction.html index 1a946be2..28009ec9 100644 --- a/doc/html/Introduction.html +++ b/doc/html/Introduction.html @@ -52,3 +52,3 @@ Let's suppose that there is an .avi video file stored on a VeraCrypt volume (the <p>Note that VeraCrypt never saves any decrypted data to a disk – it only stores them temporarily in RAM (memory). Even when the volume is mounted, data stored in the volume is still encrypted. When you restart Windows or turn off your computer, the volume - will be dismounted and files stored in it will be inaccessible (and encrypted). Even when power supply is suddenly interrupted (without proper system shut down), files stored in the volume are inaccessible (and encrypted). To make them accessible again, you + will be unmounted and files stored in it will be inaccessible (and encrypted). Even when power supply is suddenly interrupted (without proper system shut down), files stored in the volume are inaccessible (and encrypted). To make them accessible again, you have to mount the volume (and provide the correct password and/or keyfile). For a quick start guide, please see the chapter Beginner's Tutorial.</p> diff --git a/doc/html/Issues and Limitations.html b/doc/html/Issues and Limitations.html index eed2e222..4fa1e0e3 100644 --- a/doc/html/Issues and Limitations.html +++ b/doc/html/Issues and Limitations.html @@ -47,4 +47,4 @@ Also, there are other entries whose name start with "#{" and "\?? </li> -<li>On some Windows machines, VeraCrypt may hang intermittently when mounting or dismounting a volume. Similar hanging may affect other running applications during VeraCrypt mounting or dismounting operations. -This issue is caused by a conflict between VeraCrypt waiting dialog displayed during mount/dismount operations and other software installed on the machine (e.g. Outpost Firewall Pro). +<li>On some Windows machines, VeraCrypt may hang intermittently when mounting or unmounting a volume. Similar hanging may affect other running applications during VeraCrypt mounting or unmounting operations. +This issue is caused by a conflict between VeraCrypt waiting dialog displayed during mount/unmount operations and other software installed on the machine (e.g. Outpost Firewall Pro). In such situations, the issue can be solved by disabling VeraCrypt waiting dialog in the Preferences: use menu "Settings -> Preferences" and check the option "Don't show wait message dialog when performing operations". @@ -81,3 +81,3 @@ Note: The only exception is the multi-boot configuration where a running VeraCry systems (encrypted or unencrypted) installed on other drives connected to the computer (when drive #0 is disconnected, drive #1 becomes drive #0, etc.) -</li><li>When the notebook battery power is low, Windows may omit sending the appropriate messages to running applications when the computer is entering power saving mode. Therefore, VeraCrypt may fail to auto-dismount volumes in such cases. +</li><li>When the notebook battery power is low, Windows may omit sending the appropriate messages to running applications when the computer is entering power saving mode. Therefore, VeraCrypt may fail to auto-unmount volumes in such cases. </li><li>Preserving of any timestamp of any file (e.g. a container or keyfile) is not guaranteed to be reliably and securely performed (for example, due to filesystem journals, timestamps of file attributes, or the operating system failing to perform it for various @@ -105,3 +105,3 @@ link </a>explains how to disable it in Windows 8 and this <a href="https://www.t </li> -<li>Windows system Repair/Recovery Disk can't be created when a VeraCrypt volume is mounted as a fixed disk (which is the default). To solve this, either dismount all volumes or mount volumes are removable media. +<li>Windows system Repair/Recovery Disk can't be created when a VeraCrypt volume is mounted as a fixed disk (which is the default). To solve this, either unmount all volumes or mount volumes are removable media. </li><li>Further limitations are listed in the section <a href="Security%20Model.html"> diff --git a/doc/html/Main Program Window.html b/doc/html/Main Program Window.html index 30ee175b..c232633f 100644 --- a/doc/html/Main Program Window.html +++ b/doc/html/Main Program Window.html @@ -47,3 +47,3 @@ Note: There is a more comfortable way of mounting VeraCrypt partitions/devices & the volume will be mounted.</p> -<p>Important: Note that when you exit the VeraCrypt application, the VeraCrypt driver continues working and no VeraCrypt volume is dismounted.</p> +<p>Important: Note that when you exit the VeraCrypt application, the VeraCrypt driver continues working and no VeraCrypt volume is unmounted.</p> <h3 id="AutoMountDevices">Auto-Mount Devices</h3> @@ -58,9 +58,9 @@ If the password you enter is wrong, mounting is attempted using cached passwords Drive letters will be assigned starting from the one that is selected in the drive list in the main window.</p> -<h3>Dismount</h3> -<p>This function allows you to dismount the VeraCrypt volume selected in the drive list in the main window. To dismount a VeraCrypt volume means to close it and make it impossible to read/write from/to the volume.</p> -<h3>Dismount All</h3> +<h3>Unmount</h3> +<p>This function allows you to unmount the VeraCrypt volume selected in the drive list in the main window. To unmount a VeraCrypt volume means to close it and make it impossible to read/write from/to the volume.</p> +<h3>Unmount All</h3> <p>Note: The information in this section applies to all menu items and buttons with the same or similar caption (for example, it also applies to the system tray menu item -<em>Dismount All</em>).<br> +<em>Unmount All</em>).<br> <br> -This function allows you to dismount multiple VeraCrypt volumes. To dismount a VeraCrypt volume means to close it and make it impossible to read/write from/to the volume. This function dismounts all mounted VeraCrypt volumes except the following:</p> +This function allows you to unmount multiple VeraCrypt volumes. To unmount a VeraCrypt volume means to close it and make it impossible to read/write from/to the volume. This function unmounts all mounted VeraCrypt volumes except the following:</p> <ul> @@ -68,4 +68,4 @@ This function allows you to dismount multiple VeraCrypt volumes. To dismount a V </li><li>VeraCrypt volumes that are not fully accessible to the user account (e.g. a volume mounted from within another user account). -</li><li>VeraCrypt volumes that are not displayed in the VeraCrypt application window. For example, system favorite volumes attempted to be dismounted by an instance of VeraCrypt without administrator privileges when the option '<em>Allow only administrators to - view and dismount system favorite volumes in VeraCrypt</em>' is enabled. </li></ul> +</li><li>VeraCrypt volumes that are not displayed in the VeraCrypt application window. For example, system favorite volumes attempted to be unmounted by an instance of VeraCrypt without administrator privileges when the option '<em>Allow only administrators to + view and unmount system favorite volumes in VeraCrypt</em>' is enabled. </li></ul> <h3>Wipe Cache</h3> @@ -89,7 +89,7 @@ Note: You can clear the volume history by selecting <em>Tools</em> -> <em>Cle <h3>Exit</h3> -<p>Terminates the VeraCrypt application. The driver continues working and no VeraCrypt volumes are dismounted. When running in ‘portable’ mode, the VeraCrypt driver is unloaded when it is no longer needed (e.g., when all instances of the main application - and/or of the Volume Creation Wizard are closed and no VeraCrypt volumes are mounted). However, if you force dismount on a</p> +<p>Terminates the VeraCrypt application. The driver continues working and no VeraCrypt volumes are unmounted. When running in ‘portable’ mode, the VeraCrypt driver is unloaded when it is no longer needed (e.g., when all instances of the main application + and/or of the Volume Creation Wizard are closed and no VeraCrypt volumes are mounted). However, if you force unmount on a</p> <p>VeraCrypt volume when VeraCrypt runs in portable mode, or mount a writable NTFS-formatted volume on Windows Vista or later, the VeraCrypt driver may <em>not</em> be unloaded when you exit VeraCrypt (it will be unloaded only when you shut down or restart the system). This prevents various problems caused by a bug in Windows (for instance, it would be impossible to start VeraCrypt again as long as there are - applications using the dismounted volume).</p> + applications using the unmounted volume).</p> <h3>Volume Tools</h3> diff --git a/doc/html/Multi-User Environment.html b/doc/html/Multi-User Environment.html index 99456293..94c0f5e0 100644 --- a/doc/html/Multi-User Environment.html +++ b/doc/html/Multi-User Environment.html @@ -48,7 +48,7 @@ Moreover, on Windows, the password cache is shared by all logged on users (for m Also note that switching users in Windows XP or later (<em>Fast User Switching</em> functionality) does -<em>not</em> dismount a successfully mounted VeraCrypt volume (unlike system restart, which dismounts all mounted VeraCrypt volumes).<br> +<em>not</em> unmount a successfully mounted VeraCrypt volume (unlike system restart, which unmounts all mounted VeraCrypt volumes).<br> <br> On Windows 2000, the container file permissions are ignored when a file-hosted VeraCrypt volume is to be mounted. On all supported versions of Windows, users without administrator privileges can mount any partition/device-hosted VeraCrypt volume (provided that - they supply the correct password and/or keyfiles). A user without administrator privileges can dismount only volumes that he or she mounted. However, this does not apply to system favorite volumes unless you enable the option (disabled by default) -<em>Settings</em> > ‘<em>System Favorite Volumes</em>’ > ‘<em>Allow only administrators to view and dismount system favorite volumes in VeraCrypt</em>’.</p> + they supply the correct password and/or keyfiles). A user without administrator privileges can unmount only volumes that he or she mounted. However, this does not apply to system favorite volumes unless you enable the option (disabled by default) +<em>Settings</em> > ‘<em>System Favorite Volumes</em>’ > ‘<em>Allow only administrators to view and unmount system favorite volumes in VeraCrypt</em>’.</p> </div> diff --git a/doc/html/Normal Dismount vs Force Dismount.html b/doc/html/Normal Unmount vs Force Unmount.html index 4ebd52c8..72da246b 100644 --- a/doc/html/Normal Dismount vs Force Dismount.html +++ b/doc/html/Normal Unmount vs Force Unmount.html @@ -31,3 +31,3 @@ <img src="arrow_right.gif" alt=">>" style="margin-top: 5px"> -<a href="Normal%20Dismount%20vs%20Force%20Dismount.html">Normal Dismount vs Force Dismount</a> +<a href="Normal%20Unmount%20vs%20Force%20Unmount.html">Normal Unmount vs Force Unmount</a> </p></div> @@ -35,8 +35,8 @@ <div class="wikidoc"> -<h1>Normal Dismount vs Force Dismount</h1> -<p>Understanding the distinction between "Normal Dismount" and "Force Dismount" operation is important due to the potential impact on user data.</p> +<h1>Normal Unmount vs Force Unmount</h1> +<p>Understanding the distinction between "Normal Unmount" and "Force Unmount" operation is important due to the potential impact on user data.</p> -<h2>Normal Dismount Process</h2> +<h2>Normal Unmount Process</h2> -<p>During a normal dismount process, VeraCrypt performs the following steps:</p> +<p>During a normal unmount process, VeraCrypt performs the following steps:</p> @@ -52,23 +52,23 @@ -<h2>Force Dismount Process</h2> +<h2>Force Unmount Process</h2> -<p>The Force Dismount process is distinct but largely similar to the Normal Dismount. It essentially follows the same steps but disregards any failures that might occur during steps 1 and 2, and carries on with the rest of the procedure. However, if there are files open by the user or if the volume I/O cache has not yet been flushed, this could result in potential data loss. This situation parallels forcibly removing a USB device from your computer while Windows is still indicating its active usage.</p> +<p>The Force Unmount process is distinct but largely similar to the Normal Unmount. It essentially follows the same steps but disregards any failures that might occur during steps 1 and 2, and carries on with the rest of the procedure. However, if there are files open by the user or if the volume I/O cache has not yet been flushed, this could result in potential data loss. This situation parallels forcibly removing a USB device from your computer while Windows is still indicating its active usage.</p> -<p>Provided all applications using files on the mounted volume have been successfully closed and the I/O cache is fully flushed, neither data loss nor data/filesystem corruption should occur when executing a 'force dismount'. As in a normal dismount, the encryption keys are erased from RAM upon successful completion of a 'Force Dismount'.</p> +<p>Provided all applications using files on the mounted volume have been successfully closed and the I/O cache is fully flushed, neither data loss nor data/filesystem corruption should occur when executing a 'force unmount'. As in a normal unmount, the encryption keys are erased from RAM upon successful completion of a 'Force Unmount'.</p> -<h2>How to Trigger Force Dismount</h2> +<h2>How to Trigger Force Unmount</h2> -<p>There are three approaches to trigger a force dismount in VeraCrypt:</p> +<p>There are three approaches to trigger a force unmount in VeraCrypt:</p> <ol> - <li>Through the popup window that appears if a normal dismount attempt is unsuccessful.</li> - <li>Via Preferences, by checking the "force auto-dismount" option in the "Auto-Dismount" section.</li> - <li>Using the command line, by incorporating the /force or /f switch along with the /d or /dismount switch.</li> + <li>Through the popup window that appears if a normal unmount attempt is unsuccessful.</li> + <li>Via Preferences, by checking the "force auto-unmount" option in the "Auto-Unmount" section.</li> + <li>Using the command line, by incorporating the /force or /f switch along with the /d or /unmount switch.</li> </ol> -<p>In order to avoid inadvertent data loss or corruption, always ensure to follow suitable precautions when dismounting a VeraCrypt volume. This includes</p> +<p>In order to avoid inadvertent data loss or corruption, always ensure to follow suitable precautions when unmounting a VeraCrypt volume. This includes</p> <ol> - <li>Ensuring all files on the volume are closed before initiating a dismount.</li> + <li>Ensuring all files on the volume are closed before initiating a unmount.</li> <li>Allowing some time after closing all files to ensure Windows has completely flushed the I/O cache.</li> - <li>Take note that some antivirus software may keep file handles open on the volume after performing a scan, hindering a successful Normal Dismount. If you experience this issue, you might consider excluding the VeraCrypt volume from your antivirus scans. Alternatively, consult with your antivirus software provider to understand how their product interacts with VeraCrypt volumes and how to ensure it doesn't retain open file handles.</li> + <li>Take note that some antivirus software may keep file handles open on the volume after performing a scan, hindering a successful Normal Unmount. If you experience this issue, you might consider excluding the VeraCrypt volume from your antivirus scans. Alternatively, consult with your antivirus software provider to understand how their product interacts with VeraCrypt volumes and how to ensure it doesn't retain open file handles.</li> </ol> diff --git a/doc/html/Portable Mode.html b/doc/html/Portable Mode.html index b26cb35b..006c7d0f 100644 --- a/doc/html/Portable Mode.html +++ b/doc/html/Portable Mode.html @@ -66,5 +66,5 @@ Note: To extract files from the VeraCrypt self-extracting package, run it, and t <p>Note: When running in ‘portable’ mode, the VeraCrypt driver is unloaded when it is no longer needed (e.g., when all instances of the main application and/or of the Volume Creation Wizard are closed and no VeraCrypt volumes are mounted). However, - if you force dismount on a VeraCrypt volume when VeraCrypt runs in portable mode, or mount a writable NTFS-formatted volume on Windows Vista or later, the VeraCrypt driver may + if you force unmount on a VeraCrypt volume when VeraCrypt runs in portable mode, or mount a writable NTFS-formatted volume on Windows Vista or later, the VeraCrypt driver may <em>not</em> be unloaded when you exit VeraCrypt (it will be unloaded only when you shut down or restart the system). This prevents various problems caused by a bug in Windows (for instance, it would be impossible to start VeraCrypt again as long as there are - applications using the dismounted volume).</p> + applications using the unmounted volume).</p> <h3>Tools -> Traveler Disk Setup</h3> diff --git a/doc/html/Program Menu.html b/doc/html/Program Menu.html index c7ea0534..cbc52b84 100644 --- a/doc/html/Program Menu.html +++ b/doc/html/Program Menu.html @@ -43,5 +43,5 @@ <em>Auto-Mount Devices.</em></a></p> -<h3>Volumes -> Dismount All Mounted Volumes</h3> +<h3>Volumes -> Unmount All Mounted Volumes</h3> <p>See the section <a href="Main%20Program%20Window.html"> -<em>Dismount All.</em></a></p> +<em>Unmount All.</em></a></p> <h3>Volumes -> Change Volume Password</h3> @@ -188,4 +188,4 @@ If this option is checked and if there are two or more favorite volumes, then du </li><li>VeraCrypt volumes that are not fully accessible to the user account (e.g. a volume mounted from within another user account). -</li><li>VeraCrypt volumes that are not displayed in the VeraCrypt application window. For example, system favorite volumes attempted to be dismounted by an instance of VeraCrypt without administrator privileges when the option '<em>Allow only administrators to - view and dismount system favorite volumes in VeraCrypt</em>' is enabled. </li></ul> +</li><li>VeraCrypt volumes that are not displayed in the VeraCrypt application window. For example, system favorite volumes attempted to be unmounted by an instance of VeraCrypt without administrator privileges when the option '<em>Allow only administrators to + view and unmount system favorite volumes in VeraCrypt</em>' is enabled. </li></ul> <h4>VeraCrypt Background Task – Enabled</h4> @@ -197,6 +197,6 @@ If this option is checked and if there are two or more favorite volumes, then du <em>VeraCrypt Background Task</em></a>. Note that this option cannot be disabled when VeraCrypt runs in portable mode.</p> -<h4>Auto-dismount volume after no data has been read/written to it for</h4> -<p>After no data has been written/read to/from a VeraCrypt volume for <em>n</em> minutes, the volume is automatically dismounted.</p> -<h4>Force auto-dismount even if volume contains open files or directories</h4> -<p>This option applies only to auto-dismount (not to regular dismount). It forces dismount (without prompting) on the volume being auto-dismounted in case it contains open files or directories (i.e., file/directories that are in use by the system or applications).</p> +<h4>Auto-unmount volume after no data has been read/written to it for</h4> +<p>After no data has been written/read to/from a VeraCrypt volume for <em>n</em> minutes, the volume is automatically unmounted.</p> +<h4>Force auto-unmount even if volume contains open files or directories</h4> +<p>This option applies only to auto-unmount (not to regular unmount). It forces unmount (without prompting) on the volume being auto-unmounted in case it contains open files or directories (i.e., file/directories that are in use by the system or applications).</p> <p> </p> diff --git a/doc/html/Protection of Hidden Volumes.html b/doc/html/Protection of Hidden Volumes.html index 3e3e5890..ce320d21 100644 --- a/doc/html/Protection of Hidden Volumes.html +++ b/doc/html/Protection of Hidden Volumes.html @@ -63,4 +63,4 @@ Both passwords must be correct; otherwise, the outer volume will not be mounted. <em style="text-align:left">not</em> actually mount the hidden volume. It only decrypts its header (in RAM) and retrieves information about the size of the hidden volume (from the decrypted header). Then, the outer volume is mounted and any attempt to save - data to the area of the hidden volume will be rejected (until the outer volume is dismounted). -<strong style="text-align:left">Note that VeraCrypt never modifies the filesystem (e.g., information about allocated clusters, amount of free space, etc.) within the outer volume in any way. As soon as the volume is dismounted, the protection is lost. When + data to the area of the hidden volume will be rejected (until the outer volume is unmounted). +<strong style="text-align:left">Note that VeraCrypt never modifies the filesystem (e.g., information about allocated clusters, amount of free space, etc.) within the outer volume in any way. As soon as the volume is unmounted, the protection is lost. When the volume is mounted again, it is not possible to determine whether the volume has used hidden volume protection or not. The hidden volume protection can be activated only by users who supply the correct password (and/or keyfiles) for the hidden volume (each @@ -68,3 +68,3 @@ Both passwords must be correct; otherwise, the outer volume will not be mounted. </strong><br style="text-align:left"> -As soon as a write operation to the hidden volume area is denied/prevented (to protect the hidden volume), the entire host volume (both the outer and the hidden volume) becomes write-protected until dismounted (the VeraCrypt driver reports the 'invalid parameter' +As soon as a write operation to the hidden volume area is denied/prevented (to protect the hidden volume), the entire host volume (both the outer and the hidden volume) becomes write-protected until unmounted (the VeraCrypt driver reports the 'invalid parameter' error to the system upon each attempt to write data to the volume). This preserves plausible deniability (otherwise certain kinds of inconsistency within the file system could indicate that this volume has used hidden volume protection). When damage to hidden @@ -83,3 +83,3 @@ Moreover, the field <em style="text-align:left">Hidden Volume Protected </em>in Note that when damage to hidden volume is prevented, <em style="text-align:left"> -no</em> information about the event is written to the volume. When the outer volume is dismounted and mounted again, the volume properties will +no</em> information about the event is written to the volume. When the outer volume is unmounted and mounted again, the volume properties will <em style="text-align:left">not </em>display the string "<em style="text-align:left">damage prevented</em>".<em style="text-align:left"><br style="text-align:left"> @@ -102,3 +102,3 @@ The type of the mounted outer volume is <em style="text-align:left">Outer</em>: type "Outer" but "Normal"). The reason is that, during the time when an outer volume is mounted with the hidden volume protection enabled, the adversary -</strong></em><strong style="text-align:left">can</strong><em style="text-align:left"><strong style="text-align:left"> find out that a hidden volume exists within the outer volume (he/she will be able to find it out until the volume is dismounted and possibly +</strong></em><strong style="text-align:left">can</strong><em style="text-align:left"><strong style="text-align:left"> find out that a hidden volume exists within the outer volume (he/she will be able to find it out until the volume is unmounted and possibly even some time after the computer has been powered off - see <a href="Unencrypted%20Data%20in%20RAM.html" style="text-align:left; color:#0080c0; text-decoration:none.html"> diff --git a/doc/html/Release Notes.html b/doc/html/Release Notes.html index dfca8b81..a01ee225 100644 --- a/doc/html/Release Notes.html +++ b/doc/html/Release Notes.html @@ -46,3 +46,3 @@ <ul> -<li>Fix regression that blocked dismounting of volumes. (GH #1467)</li> +<li>Fix regression that blocked unmounting of volumes. (GH #1467)</li> </ul> @@ -251,3 +251,3 @@ <li>Don't allow selecting exFAT/BTRFS filesytem if they are not present or not compatible with the created volume.</li> -<li>Fix wrong dismount message displayed when mounting a volume.</li> +<li>Fix wrong unmount message displayed when mounting a volume.</li> <li>Hide PIM during entry and re-ask PIM when user entered a wrong value.</li> @@ -499,3 +499,3 @@ <li>Add switch /signalExit to support notifying <a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/waitfor" target="_blank">WAITFOR</a> Windows command when VeraCrypt.exe exits if /q was specified in CLI (cf documentation for usage).</li> -<li>Don't display mount/dismount examples in help dialog for command line in Format and Expander.</li> +<li>Don't display mount/unmount examples in help dialog for command line in Format and Expander.</li> <li>Documentation and translation updates.</li> @@ -773,3 +773,3 @@ <li>Fix current application losing focus when VeraCrypt is run in command line with /quit /silent switches.</li> -<li>Fix some cases of external applications freezing during mount/dismount.</li> +<li>Fix some cases of external applications freezing during mount/unmount.</li> <li>Fix rare cases of secure desktop for password dialog not visible which caused UI to block.</li> @@ -1062,3 +1062,3 @@ incorrect Impersonation Token Handling. </li></ul> </li><li>Add possibility to show system encryption password in Windows GUI and bootloader -</li><li>Solve "Class Already exists" error that was happening for some users. </li><li>Solve some menu items and GUI fields not translatable </li><li>Make volumes correctly report Physical Sector size to Windows. </li><li>Correctly detect switch user/RDP disconnect operations for autodismount on session locked. +</li><li>Solve "Class Already exists" error that was happening for some users. </li><li>Solve some menu items and GUI fields not translatable </li><li>Make volumes correctly report Physical Sector size to Windows. </li><li>Correctly detect switch user/RDP disconnect operations for autounmount on session locked. </li><li>Add manual selection of partition when resuming in-place encryption. </li><li>Add command line option (/cache f) to temporarily cache password during favorites mounting. @@ -1097,3 +1097,3 @@ incorrect Impersonation Token Handling. </li></ul> <ul> -<li>Solve issue volumes not auto-dismounting when quitting VeraCrypt<strong>.</strong> +<li>Solve issue volumes not auto-unmounting when quitting VeraCrypt<strong>.</strong> </li><li>Solve issue VeraCrypt window not reopening by clicking dock icon. </li></ul> @@ -1134,3 +1134,3 @@ incorrect Impersonation Token Handling. </li></ul> </li><li>Correct a random crash when clicking the link for more information on keyfiles -</li><li>Implement option to auto-dismount when user session is locked </li><li>Add self-test vectors for SHA-256 </li><li>Modern look-and-feel by enabling visual styles </li><li>few minor fixed. </li></ul> +</li><li>Implement option to auto-unmount when user session is locked </li><li>Add self-test vectors for SHA-256 </li><li>Modern look-and-feel by enabling visual styles </li><li>few minor fixed. </li></ul> </li></ul> diff --git a/doc/html/Removable Medium Volume.html b/doc/html/Removable Medium Volume.html index 63c59c55..2be8297c 100644 --- a/doc/html/Removable Medium Volume.html +++ b/doc/html/Removable Medium Volume.html @@ -49,4 +49,4 @@ NTFS health checks as <a href="https://blogs.msdn.microsoft.com/b8/2012/05/09/redesigning-chkdsk-and-the-new-ntfs-health-model/" target="_blank"> -explained here</a>. Big thanks to Liran Elharar for discovering this. </li><li>Windows may use caching methods and write delays that are normally used for removable media (for example, USB flash drives). This might slightly decrease the performance but at the same increase the likelihood that it will be possible to dismount the volume - quickly without having to force the dismount. </li><li>The operating system may tend to keep the number of handles it opens to such a volume to a minimum. Hence, volumes mounted as removable media might require fewer forced dismounts than other volumes. +explained here</a>. Big thanks to Liran Elharar for discovering this. </li><li>Windows may use caching methods and write delays that are normally used for removable media (for example, USB flash drives). This might slightly decrease the performance but at the same increase the likelihood that it will be possible to unmount the volume + quickly without having to force the unmount. </li><li>The operating system may tend to keep the number of handles it opens to such a volume to a minimum. Hence, volumes mounted as removable media might require fewer forced unmounts than other volumes. </li><li>Under Windows Vista and earlier, the ‘<em>Computer</em>’ (or ‘<em>My Computer</em>’) list does not show the amount of free space on volumes mounted as removable (note that this is a Windows limitation, not a bug in VeraCrypt). diff --git a/doc/html/Removing Encryption.html b/doc/html/Removing Encryption.html index c2baf5c6..3f3bf139 100644 --- a/doc/html/Removing Encryption.html +++ b/doc/html/Removing Encryption.html @@ -45,3 +45,3 @@ for non-system partition/drive). If you need to remove encryption (e.g., if you <li>Mount the VeraCrypt volume. </li><li>Move all files from the VeraCrypt volume to any location outside the VeraCrypt volume (note that the files will be decrypted on the fly). -</li><li>Dismount the VeraCrypt volume. </li><li>delete it (the container) just like you delete any other file. </li></ol> +</li><li>Unmount the VeraCrypt volume. </li><li>delete it (the container) just like you delete any other file. </li></ol> <p>If in-place decryption of non-system partitions/drives is not desired, it is also possible in this case to follow the steps 1-3 described above.<br> diff --git a/doc/html/Security Model.html b/doc/html/Security Model.html index 79e154d2..edac59d2 100644 --- a/doc/html/Security Model.html +++ b/doc/html/Security Model.html @@ -53,3 +53,3 @@ </li><li>Preserve/verify the integrity or authenticity of encrypted or decrypted data. -</li><li>Prevent traffic analysis when encrypted data is transmitted over a network. </li><li>Prevent an attacker from determining in which sectors of the volume the content changed (and when and how many times) if he or she can observe the volume (dismounted or mounted) before and after data is written to it, or if the storage medium/device allows +</li><li>Prevent traffic analysis when encrypted data is transmitted over a network. </li><li>Prevent an attacker from determining in which sectors of the volume the content changed (and when and how many times) if he or she can observe the volume (unmounted or mounted) before and after data is written to it, or if the storage medium/device allows the attacker to determine such information (for example, the volume resides on a device that saves metadata that can be used to determine when data was written to a particular sector). @@ -67,5 +67,5 @@ Known Issues & Limitations</a>). </li></ul> <em>Settings</em> > ‘<em>System Encryption</em>’ > ‘<em>Allow pre-boot authentication to be bypassed by pressing the Esc key</em>’; note that this option can be enabled or disabled only by an administrator). -</li><li>Dismount, using VeraCrypt, (and, in the VeraCrypt application window, see the path to and properties of) any VeraCrypt volume mounted by him or her. However, this does not apply to ‘system favorite volumes’, which he or she can dismount (etc.) +</li><li>Unmount, using VeraCrypt, (and, in the VeraCrypt application window, see the path to and properties of) any VeraCrypt volume mounted by him or her. However, this does not apply to ‘system favorite volumes’, which he or she can unmount (etc.) regardless of who mounted them (this can be prevented by enabling the option <em> -Settings</em> > ‘<em>System Favorite Volumes</em>’ > ‘<em>Allow</em> only administrators to view and dismount system favorite volumes in VeraCrypt’; note that this option can be enabled or disabled only by an administrator). +Settings</em> > ‘<em>System Favorite Volumes</em>’ > ‘<em>Allow</em> only administrators to view and unmount system favorite volumes in VeraCrypt’; note that this option can be enabled or disabled only by an administrator). </li><li>Create a file-hosted VeraCrypt volume containing a FAT or no file system (provided that the relevant folder permissions allow it). @@ -89,3 +89,3 @@ Settings</em> > ‘<em>System Favorite Volumes</em>’ > ‘<e <li>Mount any file-hosted or partition/device-hosted VeraCrypt volume provided that the file/device permissions allow it. -</li><li>Dismount, using VeraCrypt, (and, in the VeraCrypt application window, see the path to and properties of) any VeraCrypt volume mounted by him or her. +</li><li>Unmount, using VeraCrypt, (and, in the VeraCrypt application window, see the path to and properties of) any VeraCrypt volume mounted by him or her. </li><li>Create a file-hosted or partition/device-hosted VeraCrypt volume provided that the relevant folder/device permissions allow it. diff --git a/doc/html/Security Requirements for Hidden Volumes.html b/doc/html/Security Requirements for Hidden Volumes.html index 3b5dbdb3..7ac28c40 100644 --- a/doc/html/Security Requirements for Hidden Volumes.html +++ b/doc/html/Security Requirements for Hidden Volumes.html @@ -46,3 +46,3 @@ hidden VeraCrypt volume</a>, you must follow the security requirements and preca <li style="text-align:left; margin-top:0px; margin-bottom:0px; padding-top:0px; padding-bottom:0px"> -If an adversary has access to a (dismounted) VeraCrypt volume at several points over time, he may be able to determine which sectors of the volume are changing. If you change the contents of a +If an adversary has access to a (unmounted) VeraCrypt volume at several points over time, he may be able to determine which sectors of the volume are changing. If you change the contents of a <a href="Hidden%20Volume.html" style="text-align:left; color:#0080c0; text-decoration:none.html"> diff --git a/doc/html/Sharing over Network.html b/doc/html/Sharing over Network.html index 829838b9..f1969f0f 100644 --- a/doc/html/Sharing over Network.html +++ b/doc/html/Sharing over Network.html @@ -47,3 +47,3 @@ <em>System Favorite Volumes</em></a>).</p> -</li><li>A dismounted VeraCrypt file container is stored on a single computer (for example, on a server). This encrypted file is shared over a network. Users on other computers or systems will locally mount the shared file. Thus, the volume will be mounted simultaneously +</li><li>A unmounted VeraCrypt file container is stored on a single computer (for example, on a server). This encrypted file is shared over a network. Users on other computers or systems will locally mount the shared file. Thus, the volume will be mounted simultaneously under multiple operating systems. diff --git a/doc/html/System Favorite Volumes.html b/doc/html/System Favorite Volumes.html index 491a6698..3dd06b74 100644 --- a/doc/html/System Favorite Volumes.html +++ b/doc/html/System Favorite Volumes.html @@ -54,4 +54,4 @@ each time the operating system starts. </li></ul> System favorite volumes <strong>can be configured to be available within VeraCrypt only to users with administrator privileges -</strong>(select <em>Settings </em>> ‘<em>System Favorite Volumes</em>’ > ‘<em>Allow only administrators to view and dismount system favorite volumes in VeraCrypt</em>’). This option should be enabled on servers to ensure that - system favorite volumes cannot be dismounted by users without administrator privileges. On non-server systems, this option can be used to prevent normal VeraCrypt volume actions (such as ‘<em>Dismount All</em>’, auto-dismount, etc.) from affecting +</strong>(select <em>Settings </em>> ‘<em>System Favorite Volumes</em>’ > ‘<em>Allow only administrators to view and unmount system favorite volumes in VeraCrypt</em>’). This option should be enabled on servers to ensure that + system favorite volumes cannot be unmounted by users without administrator privileges. On non-server systems, this option can be used to prevent normal VeraCrypt volume actions (such as ‘<em>Unmount All</em>’, auto-unmount, etc.) from affecting system favorite volumes. In addition, when VeraCrypt is run without administrator privileges (the default on Windows Vista and later), system favorite volumes will not be displayed in the drive letter list in the main VeraCrypt application window.</p> diff --git a/doc/html/Troubleshooting.html b/doc/html/Troubleshooting.html index 3eece663..e3cfb49f 100644 --- a/doc/html/Troubleshooting.html +++ b/doc/html/Troubleshooting.html @@ -316,3 +316,3 @@ Replace the motherboard with a different one (different type and/or brand). </li <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> -<em style="text-align:left">When mounting or dismounting a VeraCrypt volume, the system crashes (a 'blue screen' error screen appears or the +<em style="text-align:left">When mounting or unmounting a VeraCrypt volume, the system crashes (a 'blue screen' error screen appears or the <span style="text-align:left">computer abruptly restarts)</span>.</em></div> diff --git a/doc/html/Unencrypted Data in RAM.html b/doc/html/Unencrypted Data in RAM.html index 9c4de777..96fe5813 100644 --- a/doc/html/Unencrypted Data in RAM.html +++ b/doc/html/Unencrypted Data in RAM.html @@ -42,7 +42,7 @@ It is important to note that VeraCrypt is <em style="text-align:left">disk</em> Keep in mind that most programs do not clear the memory area (buffers) in which they store unencrypted (portions of) files they load from a VeraCrypt volume. This means that after you exit such a program, unencrypted data it worked with may remain in memory - (RAM) until the computer is turned off (and, according to some researchers, even for some time after the power is turned off*). Also note that if you open a file stored on a VeraCrypt volume, for example, in a text editor and then force dismount on the VeraCrypt - volume, then the file will remain unencrypted in the area of memory (RAM) used by (allocated to) the text editor. This also applies to forced auto-dismount.</div> + (RAM) until the computer is turned off (and, according to some researchers, even for some time after the power is turned off*). Also note that if you open a file stored on a VeraCrypt volume, for example, in a text editor and then force unmount on the VeraCrypt + volume, then the file will remain unencrypted in the area of memory (RAM) used by (allocated to) the text editor. This also applies to forced auto-unmount.</div> <div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px"> -Inherently, unencrypted master keys have to be stored in RAM too. When a non-system VeraCrypt volume is dismounted, VeraCrypt erases its master keys (stored in RAM). When the computer is cleanly restarted (or cleanly shut down), all non-system VeraCrypt volumes - are automatically dismounted and, thus, all master keys stored in RAM are erased by the VeraCrypt driver (except master keys for system partitions/drives — see below). However, when power supply is abruptly interrupted, when the computer is reset (not +Inherently, unencrypted master keys have to be stored in RAM too. When a non-system VeraCrypt volume is unmounted, VeraCrypt erases its master keys (stored in RAM). When the computer is cleanly restarted (or cleanly shut down), all non-system VeraCrypt volumes + are automatically unmounted and, thus, all master keys stored in RAM are erased by the VeraCrypt driver (except master keys for system partitions/drives — see below). However, when power supply is abruptly interrupted, when the computer is reset (not cleanly restarted), or when the system crashes, <strong style="text-align:left"> @@ -72,5 +72,5 @@ Hibernation File</a>).</td> (e.g. -50 °C). New types of memory modules allegedly exhibit a much shorter decay time (e.g. 1.5-2.5 seconds) than older types (as of 2008).</span><br style="text-align:left"> -<span style="text-align:left; font-size:10px; line-height:12px">** Before a key can be erased from RAM, the corresponding VeraCrypt volume must be dismounted. For non-system volumes, this does not cause any problems. However, as Microsoft currently does not - provide any appropriate API for handling the final phase of the system shutdown process, paging files located on encrypted system volumes that are dismounted during the system shutdown process may still contain valid swapped-out memory pages (including portions - of Windows system files). This could cause 'blue screen' errors. Therefore, to prevent 'blue screen' errors, VeraCrypt does not dismount encrypted system volumes and consequently cannot clear the master keys of the system volumes when the system is shut down +<span style="text-align:left; font-size:10px; line-height:12px">** Before a key can be erased from RAM, the corresponding VeraCrypt volume must be unmounted. For non-system volumes, this does not cause any problems. However, as Microsoft currently does not + provide any appropriate API for handling the final phase of the system shutdown process, paging files located on encrypted system volumes that are unmounted during the system shutdown process may still contain valid swapped-out memory pages (including portions + of Windows system files). This could cause 'blue screen' errors. Therefore, to prevent 'blue screen' errors, VeraCrypt does not unmount encrypted system volumes and consequently cannot clear the master keys of the system volumes when the system is shut down or restarted.</span></p> diff --git a/doc/html/Using VeraCrypt Without Administrator Privileges.html b/doc/html/Using VeraCrypt Without Administrator Privileges.html index 742ae0e9..1bb1bbb9 100644 --- a/doc/html/Using VeraCrypt Without Administrator Privileges.html +++ b/doc/html/Using VeraCrypt Without Administrator Privileges.html @@ -42,3 +42,3 @@ <br> -After a system administrator installs VeraCrypt on the system, users without administrator privileges will be able to run VeraCrypt, mount/dismount any type of VeraCrypt volume, load/save data from/to it, and create file-hosted VeraCrypt volumes on the system. +After a system administrator installs VeraCrypt on the system, users without administrator privileges will be able to run VeraCrypt, mount/unmount any type of VeraCrypt volume, load/save data from/to it, and create file-hosted VeraCrypt volumes on the system. However, users without administrator privileges cannot encrypt/format partitions, cannot create NTFS volumes, cannot install/uninstall VeraCrypt, cannot change passwords/keyfiles for VeraCrypt partitions/devices, cannot backup/restore headers of VeraCrypt diff --git a/doc/html/VeraCrypt Background Task.html b/doc/html/VeraCrypt Background Task.html index 2ded6d50..bc56155b 100644 --- a/doc/html/VeraCrypt Background Task.html +++ b/doc/html/VeraCrypt Background Task.html @@ -41,3 +41,3 @@ <ol> -<li>Hot keys </li><li>Auto-dismount (e.g., upon logoff, inadvertent host device removal, time-out, etc.) +<li>Hot keys </li><li>Auto-unmount (e.g., upon logoff, inadvertent host device removal, time-out, etc.) </li><li>Auto-mount of favorite volumes </li><li>Notifications (e.g., when damage to hidden volume is prevented) </li><li>Tray icon </li></ol> diff --git a/doc/html/VeraCrypt Hidden Operating System.html b/doc/html/VeraCrypt Hidden Operating System.html index 8881b925..fcaeef57 100644 --- a/doc/html/VeraCrypt Hidden Operating System.html +++ b/doc/html/VeraCrypt Hidden Operating System.html @@ -221,3 +221,3 @@ When an attacker gets hold of your computer when a VeraCrypt volume is mounted ( limit the time the volume is mounted to a minimum. Obviously, this may be impossible or difficult if the sensitive data is stored on an encrypted system partition or on an entirely encrypted system drive (because you would also have to limit the time you work - with the computer to a minimum). Hence, you can answer that you created a separate partition (encrypted with a different key than your system partition) for your most sensitive data and that you mount it only when necessary and dismount it as soon as possible + with the computer to a minimum). Hence, you can answer that you created a separate partition (encrypted with a different key than your system partition) for your most sensitive data and that you mount it only when necessary and unmount it as soon as possible (so as to limit the time the volume is mounted to a minimum). On the system partition, you store data that is less sensitive (but which you need to access often) than data you store on the non-system partition (i.e. on the outer volume). diff --git a/doc/html/VeraCrypt RAM Encryption.html b/doc/html/VeraCrypt RAM Encryption.html index 5bfb6aa5..033a4522 100644 --- a/doc/html/VeraCrypt RAM Encryption.html +++ b/doc/html/VeraCrypt RAM Encryption.html @@ -60,3 +60,3 @@ <li>For each I/O request for a volume, the master keys are decrypted only for the duration of that request and then securely wiped.</li> - <li>Upon volume dismounting, the encrypted master keys are securely removed from memory.</li> + <li>Upon volume unmounting, the encrypted master keys are securely removed from memory.</li> <li>At Windows shutdown or reboot, the memory region allocated during startup is securely wiped.</li> diff --git a/doc/html/ru/Command Line Usage.html b/doc/html/ru/Command Line Usage.html index c3fc1efe..e0d41dfa 100644 --- a/doc/html/ru/Command Line Usage.html +++ b/doc/html/ru/Command Line Usage.html @@ -84,3 +84,3 @@ <tr> -<td> <em>/dismount</em> или <em>/d</em></td> +<td> <em>/unmount</em> или <em>/d</em></td> <td>Размонтировать том с указанной буквой диска (пример: <code>/d x</code>). Если буква диска не указана, то будут размонтированы все смонтированные на данный момент тома VeraCrypt.</td> diff --git a/doc/html/ru/Documentation.html b/doc/html/ru/Documentation.html index 00fcc0ea..81f74c84 100644 --- a/doc/html/ru/Documentation.html +++ b/doc/html/ru/Documentation.html @@ -61,3 +61,3 @@ </li></ul> -</li><li><strong><a href="Normal%20Dismount%20vs%20Force%20Dismount.html">Обычное размонтирование против принудительного</a></strong> +</li><li><strong><a href="Normal%20Unmount%20vs%20Force%20Unmount.html">Обычное размонтирование против принудительного</a></strong> </li><li><strong><a href="Avoid%20Third-Party%20File%20Extensions.html">О рисках, связанных со сторонними расширениями файлов</a></strong> diff --git a/doc/html/ru/Normal Dismount vs Force Dismount.html b/doc/html/ru/Normal Unmount vs Force Unmount.html index 1bc91dcf..1d02e6db 100644 --- a/doc/html/ru/Normal Dismount vs Force Dismount.html +++ b/doc/html/ru/Normal Unmount vs Force Unmount.html @@ -31,3 +31,3 @@ <img src="arrow_right.gif" alt=">>" style="margin-top: 5px"> -<a href="Normal%20Dismount%20vs%20Force%20Dismount.html">Чем обычное размонтирование отличается от принудительного</a> +<a href="Normal%20Unmount%20vs%20Force%20Unmount.html">Чем обычное размонтирование отличается от принудительного</a> </p></div> @@ -65,3 +65,3 @@ <li>Через настройки программы, включив опцию <em>Принудительное авторазмонтирование даже при открытых файлах или папках</em> в группе параметров <em>Автоматическое размонтирование</em>.</li> - <li>Через командную строку, указав ключ /force или /f вместе с ключом /d или /dismount.</li> + <li>Через командную строку, указав ключ /force или /f вместе с ключом /d или /unmount.</li> </ol> |