VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/doc/html/Using VeraCrypt Without Administrator Privileges.html
diff options
context:
space:
mode:
authorHelmut K. C. Tessarek <tessarek@evermeet.cx>2025-01-31 23:18:26 +0100
committerGitHub <noreply@github.com>2025-01-31 23:18:26 +0100
commit498dff9013d18e5978ab77c14ea2b2d0229603a4 (patch)
tree7f172f9c2945691ac9b1fb08f963a2263fd6942f /doc/html/Using VeraCrypt Without Administrator Privileges.html
parentc71fa14dc09fd7f31282f6ce4fdf3db547b9b827 (diff)
downloadVeraCrypt-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/html/Using VeraCrypt Without Administrator Privileges.html')
-rw-r--r--doc/html/Using VeraCrypt Without Administrator Privileges.html2
1 files changed, 1 insertions, 1 deletions
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
@@ -40,7 +40,7 @@
<p>In Windows, a user who does not have administrator privileges <em>can</em> use VeraCrypt, but only after a system administrator installs VeraCrypt on the system. The reason for that is that VeraCrypt needs a device driver to provide transparent on-the-fly
encryption/decryption, and users without administrator privileges cannot install/start device drivers in Windows.<br>
<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
partitions/devices, and they cannot run VeraCrypt in &lsquo;portable&rsquo; mode.</p>
<div>