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/html/Normal Unmount vs Force Unmount.html | |
| parent | c71fa14dc09fd7f31282f6ce4fdf3db547b9b827 (diff) | |
| download | VeraCrypt-master.tar.gz VeraCrypt-master.zip | |
* 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/html/Normal Unmount vs Force Unmount.html')
| -rw-r--r-- | doc/html/Normal Unmount vs Force Unmount.html | 77 |
1 files changed, 77 insertions, 0 deletions
diff --git a/doc/html/Normal Unmount vs Force Unmount.html b/doc/html/Normal Unmount vs Force Unmount.html new file mode 100644 index 00000000..72da246b --- /dev/null +++ b/doc/html/Normal Unmount vs Force Unmount.html @@ -0,0 +1,77 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> +<head> +<meta http-equiv="content-type" content="text/html; charset=utf-8" /> +<title>VeraCrypt - Free Open source disk encryption with strong security for the Paranoid</title> +<meta name="description" content="VeraCrypt is free open-source disk encryption software for Windows, Mac OS X and Linux. In case an attacker forces you to reveal the password, VeraCrypt provides plausible deniability. In contrast to file encryption, data encryption performed by VeraCrypt is real-time (on-the-fly), automatic, transparent, needs very little memory, and does not involve temporary unencrypted files."/> +<meta name="keywords" content="encryption, security"/> +<link href="styles.css" rel="stylesheet" type="text/css" /> +</head> +<body> + +<div> +<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a> +</div> + +<div id="menu"> + <ul> + <li><a href="Home.html">Home</a></li> + <li><a href="/code/">Source Code</a></li> + <li><a href="Downloads.html">Downloads</a></li> + <li><a class="active" href="Documentation.html">Documentation</a></li> + <li><a href="Donation.html">Donate</a></li> + <li><a href="https://sourceforge.net/p/veracrypt/discussion/" target="_blank">Forums</a></li> + </ul> +</div> + +<div> +<p> +<a href="Documentation.html">Documentation</a> +<img src="arrow_right.gif" alt=">>" style="margin-top: 5px"> +<a href="Normal%20Unmount%20vs%20Force%20Unmount.html">Normal Unmount vs Force Unmount</a> +</p></div> + +<div class="wikidoc"> +<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 Unmount Process</h2> + +<p>During a normal unmount process, VeraCrypt performs the following steps:</p> + +<ol> + <li>Requests the Windows operating system to lock the volume, prohibiting further I/O operations.</li> + <li>Requests Windows to gracefully eject the volume from the system. This step is analogous to user-initiated device ejection via the system tray.</li> + <li>Instructs the Windows Mount Manager to unmount the volume.</li> + <li>Deletes the link between the drive letter and the volume's virtual device.</li> + <li>Deletes the volume's virtual device, which includes erasing the encryption keys from RAM.</li> +</ol> + +<p>In this flow, steps 1 and 2 may fail if there are open files on the volume. Notably, even if all user applications accessing files on the volume are closed, Windows might still keep the files open until the I/O cache is completely flushed.</p> + +<h2>Force Unmount Process</h2> + +<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 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 Unmount</h2> + +<p>There are three approaches to trigger a force unmount in VeraCrypt:</p> + +<ol> + <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 unmounting a VeraCrypt volume. This includes</p> +<ol> + <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 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> + + +</div><div class="ClearBoth"></div></body></html> |