VeraCrypt - Free Open source disk encryption with strong security for the Paranoid
Description: 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.
Keywords: encryption, security

Documentation Troubleshooting

# Troubleshooting

This section presents possible solutions to common problems that you may run into when using VeraCrypt.
Note: If your problem is not listed here, it might be listed in one of the following sections:

- Incompatibilities
- Known Issues & Limitations
- Frequently Asked Questions

Make sure you use the latest stable version of VeraCrypt. If the problem is caused by a bug in an old version of VeraCrypt, it may have already been fixed. Note: Select Help > About to find out which version you use.

Problem:
Writing/reading to/from volume is very slow even though, according to the benchmark, the speed of the cipher that I'm using is higher than the speed of the hard drive.
Probable Cause:
This is probably caused by an interfering application.
Possible Solution:
First, make sure that your VeraCrypt container does not have a file extension that is reserved for executable files (for example, .exe, .sys, or .dll). If it does, Windows and antivirus software may interfere with the container and adversely affect the performance of the volume.
Second, disable or uninstall any application that might be interfering, which usually is antivirus software or automatic disk defragmentation tool, etc. In case of antivirus software, it often helps to turn off real-time (on-access) scanning in the preferences of the antivirus software. If it does not help, try temporarily disabling the virus protection software. If this does not help either, try uninstalling it completely and restarting your computer subsequently.

Problem:
VeraCrypt volume cannot be mounted; VeraCrypt reports "Incorrect password or not a VeraCrypt volume".
Possible Cause:
The volume header may have been damaged by a third-party application or malfunctioning hardware component.
Possible Solutions:

- You can try to restore the volume header from the backup embedded in the volume by following these steps:
  1. Run VeraCrypt.
  2. Click Select Device or Select File to select your volume.
  3. Select Tools > Restore Volume Header.

Problem:
After successfully mounting a volume, Windows reports "This device does not contain a valid file system" or a similar error.
Probable Cause:
The file system on the VeraCrypt volume may be corrupted (or the volume is unformatted).
Possible Solution:
You can use filesystem repair tools supplied with your operating system to attempt to repair the filesystem on the VeraCrypt volume. In Windows, it is the 'chkdsk' tool. VeraCrypt provides an easy way to use this tool on a VeraCrypt volume: First, make a backup copy of the VeraCrypt volume (because the 'chkdsk' tool might damage the filesystem even more) and then mount it. Right-click the mounted volume in the main VeraCrypt window (in the drive list) and from the context menu select 'Repair Filesystem'.

Problem:
When trying to create a hidden volume, its maximum possible size is unexpectedly small (there is much more free space than this on the outer volume).
Probable Causes:

1. The outer volume has been formatted as NTFS
2. Fragmentation
3. Too small cluster size + too many files/folders in the root directory of the outer volume.

Possible Solutions:
Solution Related to Cause 1:

> Unlike the FAT filesystem, the NTFS filesystem always stores internal data exactly in the middle of the volume. Therefore, the hidden volume can reside only in the second half of the outer volume. If this constraint is unacceptable, do one of the following:
> - Reformat the outer volume as FAT and then create a hidden volume within it.
> - If the outer volume is too large to be formatted as FAT, split the volume to several 2-terabyte volumes (or 16-terabyte volumes if the device uses 4-kilobyte sectors) and format each of them as FAT.

Solution Related to Cause 2:

> Create a new outer volume (defragmentation is not a solution, because it would adversely affect plausible deniability – see section Defragmenting).

Solution Related to Cause 3:

> Note: The following solution applies only to hidden volumes created within FAT volumes.
> Defragment the outer volume (mount it, right-click its drive letter in the 'Computer' or 'My Computer' window, click Properties, select the Tools tab, and click 'Defragment Now'). After the volume is defragmented, exit Disk Defragmenter and try to create the hidden volume again.
> If this does not help, delete all files and folders on the outer volume by pressing Shift+Delete, not by formatting, (do not forget to disable the Recycle Bin and System Restore for this drive beforehand) and try creating the hidden volume on this completely empty outer volume again (for testing purposes only). If the maximum possible size of the hidden volume does not change even now, the cause of the problem is very likely an extended root directory. If you did not use the 'Default' cluster size (the last step in the Wizard), reformat the outer volume and this time leave the cluster size at 'Default'.
> If it does not help, reformat the outer volume again and copy less files/folders to its root folder than you did last time. If it does not help, keep reformatting and decreasing the number of files/folders in the root folder. If this is unacceptable or if it does not help, reformat the outer volume and select a larger cluster size. If it does not help, keep reformatting and increasing the cluster size, until the problem is solved. Alternatively, try creating a hidden volume within an NTFS volume.

Problem:
One of the following problems occurs:

- A VeraCrypt volume cannot be mounted.
- NTFS VeraCrypt volumes cannot be created.

In addition, the following error may be reported: "The process cannot access the file because it is being used by another process."
Probable Cause:
This is probably caused by an interfering application. Note that this is not a bug in VeraCrypt. The operating system reports to VeraCrypt that the device is locked for an exclusive access by an application (so VeraCrypt is not allowed to access it).
Possible Solution:
It usually helps to disable or uninstall the interfering application, which is usually an anti-virus utility, a disk management application, etc.

Problem:
In the VeraCrypt Boot Loader screen, I'm trying to type my password and/or pressing other keys but the VeraCrypt boot loader is not responding.
Probable Cause:
You have a USB keyboard (not a PS/2 keyboard) and pre-boot support for USB keyboards is disabled in your BIOS settings.
Possible Solution:
You need to enable pre-boot support for USB keyboards in your BIOS settings. To do so, follow the below steps:
Restart your computer, press F2 or Delete (as soon as you see a BIOS start-up screen), and wait until a BIOS configuration screen appears. If no BIOS configuration screen appears, restart (reset) the computer again and start pressing F2 or Delete repeatedly as soon as you restart (reset) the computer. When a BIOS configuration screen appears, enable pre-boot support for USB keyboards. This can typically be done by selecting: Advanced > 'USB Configuration' > 'Legacy USB Support' (or 'USB Legacy') > Enabled. (Note that the word 'legacy' is in fact misleading, because pre-boot components of modern versions of MS Windows require this option to be enabled to allow user interaction/control.) Then save the BIOS settings (typically by pressing F10) and restart your computer. For more information, please refer to the documentation for your BIOS/motherboard or contact your computer vendor's technical support team for assistance.

Problem:
After the system partition/drive is encrypted, the computer cannot boot after it is restarted (it is also impossible to enter the BIOS configuration screen).
Probable Cause:
A bug in the BIOS of your computer.
Possible Solutions:

Follow these steps:

1. Disconnect the encrypted drive.
2. Connect an unencrypted drive with an installed operating system (or install it on the drive).
3. Upgrade the BIOS.
4. If it does not help, please report this bug to the manufacturer or vendor of the computer.

OR

- If the BIOS/motherboard/computer manufacturer/vendor does not provide any updates that resolve the issue and you use Windows 7 or later and there is an extra boot partition (whose size is less than 1 GB) on the drive, you can try reinstalling Windows without this extra boot partition (to work around a bug in the BIOS).

Problem:
One of the following problems occurs:

- After the pre-boot authentication password is entered during the system encryption pretest, the computer hangs (after the message 'Booting...' is displayed).
- When the system partition/drive is encrypted (partially or fully) and the system is restarted for the first time since the process of encryption of the system partition/drive started, the computer hangs after you enter the pre-boot authentication password (after the message 'Booting...' is displayed).
- After the hidden operating system is cloned and the password for it entered, the computer hangs (after the message 'Booting...' is displayed).

Probable Cause:
A bug in the BIOS of your computer or an issue with Windows bootloader.
Possible Solution:

- Upgrade your BIOS (for information on how to do so, please refer to the documentation for your BIOS/motherboard or contact your computer vendor's technical support team for assistance).
- Use a different motherboard model/brand.
- If the BIOS/motherboard/computer manufacturer/vendor does not provide any updates that resolve the issue and you use Windows 7 or later and there is an extra boot partition (whose size is less than 1 GB) on the drive, you can try reinstalling Windows without this extra boot partition (to work around a bug in the BIOS).
- There two other known workarounds for this issue that require having a Windows Installation disk:
  - Boot your machine using a Windows Installation disk and select to repair your computer. Choose "Command Prompt" option and when it opens, type the commands below and then restart your system:
    - BootRec /fixmbr
    - BootRec /FixBoot
  - Delete the 100 MB System Reserved partition located at the beginning of your drive, set the system partition next to it as the active partition (both can be done using diskpart utility available in Windows Installation disk repair option). After that, run Startup Repair after rebooting on Windows Installation disk. The following link contains detailed instructions: https://www.sevenforums.com/tutorials/71363-system-reserved-partition-delete.html

Problem:
When trying to encrypt the system partition/drive, during the pretest, the VeraCrypt Boot Loader always reports that the pre-boot authentication password I entered is incorrect (even though I'm sure it is correct).
Possible Causes:

- Different state of the Num Lock and/or Caps Lock key
- Data corruption

Possible Solution:

1. When you set a pre-boot authentication password, remember whether the Num Lock and Caps Lock keys are on or off (depending on the manufacturer, the keys may have different labels, such as Num LK). Note: You can change the state of each of the keys as desired before you set the password, but you need to remember the states.
2. When you enter the password in the VeraCrypt Boot Loader screen, make sure the state of each of the keys is the same as when you set the password.

Note: For other possible solutions to this problem, see the other sections of this chapter.

Problem:
When the system partition/drive is encrypted, the operating system 'freezes' for approx. 10-60 seconds every 5-60 minutes (100% CPU usage may co-occur).
Probable Cause:
A CPU and/or motherboard issue.
Possible Solutions:

- Try disabling all power-saving-related features (including any special CPU enhanced halt functions) in the BIOS settings and in the 'Power Options' Windows control panel.
- Replace the processor with a different one (different type and/or brand).
- Replace the motherboard with a different one (different type and/or brand).

Problem:
When mounting or dismounting a VeraCrypt volume, the system crashes (a 'blue screen' error screen appears or the computer abruptly restarts).
OR
Since I installed VeraCrypt, the operating system has been crashing frequently.
Possible Causes:

- A bug in a third-party application (e.g. antivirus, system "tweaker", driver, etc.)
- A bug in VeraCrypt
- A bug in Windows or a malfunctioning hardware component

Possible Solutions:

- Try disabling any antivirus tools, system "tweakers", and any other similar applications. If it does not help, try uninstalling them and restarting Windows.
  If the problem persists, run VeraCrypt and select Help > 'Analyze a System Crash' shortly after the system crashes or restarts. VeraCrypt will then analyze crash dump files that Windows automatically created when it crashed (if any). If VeraCrypt determines that a bug in a third party driver is likely to have caused the crash, it will show the name and provider of the driver (note that updating or uninstalling the driver might resolve the issue). Whatever the results, you will be able to choose to send us essential information about the system crash to help us determine whether it was caused by a bug in VeraCrypt.

Problem:
On Windows 7/Vista (and possibly later versions), the Microsoft Windows Backup tool cannot be used to backup data to a non-system VeraCrypt Volume.
Cause:
A bug in the Windows Backup tool.
Possible Solution:

1. Mount the VeraCrypt volume to which you want to back up data.
2. Right-click a folder located on the volume (or right-click its drive letter in the 'Computer' list) and select an item from the 'Share with' submenu (on Windows Vista, select 'Share').
3. Follow the instructions to share the folder with your user account.
4. In the Windows Backup tool, select the shared folder (the network location/path) as the destination.
5. Start the backup process.

Note: The above solution does not apply to the Starter and Home editions of Windows 7 (and possibly later versions).

Problem:
The label of a filesystem in a VeraCrypt volume cannot be changed from within the 'Computer' window under Windows Vista or a later version of Windows.
Cause:
A Windows issue causes the label to be written only to the Windows registry file, instead of being written to the filesystem.
Possible Solutions:

- Right-click the mounted volume in the 'Computer' window, select Properties, and enter a new label for the volume.

Problem:
I cannot encrypt a partition/device because VeraCrypt Volume Creation Wizard says it is in use.
Possible Solution:
Close, disable, or uninstall all programs that might be using the partition/device in any way (for example an anti-virus utility). If it does not help, right-click the 'Computer' (or 'My Computer') icon on your desktop and select Manage -> Storage -> Disk Management. Then right-click the partition that you want to encrypt, and click Change Drive Letter and Paths. Then click Remove and OK. Restart the operating system.

Problem:
When creating a hidden volume, the Wizard reports that the outer volume cannot be locked.
Probable Cause:
The outer volume contains files being used by one or more applications.
Possible Solution:
Close all applications that are using files on the outer volume. If it does not help, try disabling or uninstalling any anti-virus utility you use and restarting the system subsequently.

Problem:
When accessing a file-hosted container shared over a network, you receive one or both of the following error messages:
"Not enough server storage is available to process this command." and/or,
"Not enough memory to complete transaction."
Probable Cause:
IRPStackSize in the Windows registry may have been set to a too small value.
Possible Solution:
Locate the IRPStackSize key in the Windows registry and set it to a higher value. Then restart the system. If the key does not exist in the Windows registry, create it at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters and set its value to 16 or higher. Then restart the system. For more information, see: https://support.microsoft.com/kb/285089/ and https://support.microsoft.com/kb/177078/

See also: Known Issues & Limitations, Incompatibilities