Mounir IDRASSI committed [9cf234] on Source Code

Translations: add macOS device validation strings

Mounir IDRASSI committed [1af978] on Source Code

macOS: validate format wizard device targets

Mounir IDRASSI committed [6c7bdb] on Source Code

Windows: avoid duplicate tray notifications

Mounir IDRASSI committed [cce240] on Source Code

Windows: Update LZMA SDK to version 26.01

Mounir IDRASSI committed [616e7e] on Source Code

Update Language.ro_1.26.28.xml (#1721)

Mounir IDRASSI committed [f49225] on Source Code

Update Norwegian Bokmål translation (#1722)

Mounir IDRASSI committed [31d16a] on Source Code

Fix Off-By-One Stack Buffer Overflows in XML Parser (#1717)

Mounir IDRASSI committed [a02182] on Source Code

Update Corsican translation on 2026-05 (2nd) (#1720)

Mounir IDRASSI committed [653a53] on Source Code

Harden TLV parser bounds checks

Mounir IDRASSI committed [3550e3] on Source Code

Update Language.nl.xml (#1718)

Mounir IDRASSI committed [c3d539] on Source Code

Update Norwegian Bokmål translation (#1716)

Mounir IDRASSI committed [146a99] on Source Code

Update Language.de.xml (#1715)

Mounir IDRASSI committed [d9c2fb] on Source Code

Update Polish translation (#1713)

Mounir IDRASSI committed [36bf50] on Source Code

Update Norwegian Bokmål translation (#1712)

Mounir IDRASSI committed [ecedd7] on Source Code

Translate English entries to Chinese in XML (#1711)

Mounir IDRASSI committed [c185c6] on Source Code

Linux/macOS: show volume creation finalization stages

Mounir IDRASSI committed [2ec61e] on Source Code

Update Russian translation for ntfs3 preference (#1704)

Mounir IDRASSI committed [321ab1] on Source Code

New translations to Language.nb.xml (#1710)

Mounir IDRASSI committed [f3bb0f] on Source Code

Update Polish translation (#1709)

Mounir IDRASSI committed [4e577e] on Source Code

Update Corsican translation on 2026-05 (#1708)

Mounir IDRASSI committed [5cf599] on Source Code

Linux: add emergency cleanup for stale unmounts

Mounir IDRASSI committed [3c0ede] on Source Code

Fix whitespace issues in translation files (#1707)

Mounir IDRASSI committed [71e220] on Source Code

Increment version to 1.26.28 in Language.nl.xml (#1705)

Mounir IDRASSI committed [f57a26] on Source Code

Increment version to 1.26.28

Mounir IDRASSI committed [161c0f] on Source Code

New update to Language.nb.xml (#1703)

Mounir IDRASSI committed [a4c2b4] on Source Code

Language files: regroup newly added entries at the bottom for easy tracking

Mounir IDRASSI committed [4d515a] on Source Code

Translations: Fix lang field of untranslated newly added language files entries

Mounir IDRASSI committed [9d0b13] on Source Code

Update Polish translation (#1702)

Mounir IDRASSI committed [ad0263] on Source Code

Update Language.nb.xml (#1701)

Mounir IDRASSI committed [319e6a] on Source Code

Linux: allow mounting NTFS volumes with ntfs3 (#1695)

Mounir IDRASSI committed [2bc7bf] on Source Code

Update Language.zh-cn.xml (#1694)

Mounir IDRASSI committed [cbe9d7] on Source Code

Some minor fixes to Norwegian Bokmål translation (#1699)

Mounir IDRASSI committed [32c620] on Source Code

Update Norwegian Bokmål translation (#1697)

Mounir IDRASSI committed [65ac30] on Source Code

Update Polish translation (#1696)

Mounir IDRASSI committed [b30450] on Source Code

Windows: Harden Windows driver input validation

Mounir IDRASSI committed [edd852] on Source Code

Windows: allow EFI repair to finalize stuck decryption

Mounir IDRASSI committed [a099cc] on Source Code

Windows: detect VeraCrypt loader before Windows loader

Mounir IDRASSI committed [54bdb6] on Source Code

Windows: verify EFI loader restoration

Mounir IDRASSI committed [fec4dc] on Source Code

Docs: add Unix command line usage page

Mounir IDRASSI committed [09e721] on Source Code

docs: document Linux noatime mount option

Tiry posted a comment on discussion Technical Topics

Hi everyone, The latest version (1.26.27 portable) causes a BSOD on Windows 11. The bug systematically appears when mounting a disk This BSOD isn't uncommon: when mounting a drive, it simply crashes about half the time. The problem is that I didn't have any logs to provide: I just got a green screen. The previous version (1.26.24) also had this issue, but a BSOD bug is supposed to be fixed in version 1.26.27. But after persisting, I managed to get a dump file. So I'll try to help you, but I'm not...

Mounir IDRASSI posted a comment on discussion Technical Topics

Yes, the EFI DCS mechanism can technically support this: one DCS prompt can accept either the hidden OS password or the decoy OS password, provided both OS entries have their own encrypted DCS/GPT package in separate security region slots. Your current result is expected. A plain decoy Windows installation can't be accepted by the DCS prompt because there is no system encryption header for DCS to test. Also, gpt_hid being rejected with GPT has to be encrypted means it isn't the encrypted package...

Mounir IDRASSI posted a comment on ticket #622

Indeed, this is a Kali rolling issue as it appears to have moved its normal package index to FUSE 3 (fuse3 / libfuse3-4), while libfuse2 /libfuse2t64 are not currently installable by name, which explains the apt errors. As a temporary workaround, Kali users can install the matching FUSE 2 runtime package from the official Kali package pool: arch=$(dpkg --print-architecture) wget https://http.kali.org/kali/pool/main/f/fuse/libfuse2t64_2.9.9-9+b1_${arch}.deb sudo apt install ./libfuse2t64_2.9.9-9+b1_${arch}.deb...

Sara posted a comment on discussion Technical Topics

Hello, I have a Windows 11 Home x64 machine using UEFI/GPT and VeraCrypt 1.26 manual DCS hidden OS flow. Current state: Internal NVMe is GPT/UEFI. Normal/decoy Windows currently boots through the normal internal Windows Boot Manager. Normal/decoy Windows is NOT VeraCrypt system-encrypted. Hidden OS is installed on a separate partition and VeraCrypt system encryption completed successfully. I created the DCS/auth USB flow manually. Both authorization USBs now work. With the authorization USB, DcsBoot.efi...

Sara posted a comment on discussion Technical Topics

It's working now, thank you so much!

Kostja modified a comment on discussion General Discussion

Hello, Mounir. I want to mention some amendments: 1). In VeraCrypt, a container is opened and a file is created in it with lowercase letters: “document”, and then if the first letter is capitalized, i.e. not “document”, but “Document”, then the first letter: ”D” will still be small (lowercase), as well as if the name is written in capital letters: “DOCUMENT“, then you cannot rename the file name in lowercase letters, i.e. rename ”DOCUMENT“ to ”document", changing the case of these letters will not...

Poseidon posted a comment on ticket #622

@presenttruth Kali stopped supporting fuse2 and moved to fuse 3 that is why Veracrypt no longer works. The rest of your post has to do with Kali and not Veracrypt, if you can't install libfuse2 in Kali ask in a Kali forum.

Kostja modified a comment on discussion General Discussion

Hello, Mounir. I want to mention some amendments: 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition...

Kostja modified a comment on discussion General Discussion

Hello, Mounir. 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows...

Kostja modified a comment on discussion General Discussion

Hello, Mounir. 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows...

Kostja modified a comment on discussion General Discussion

Hello, Mounir. 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows...

Kostja modified a comment on discussion General Discussion

Hello, Mounir. 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows...

Kostja modified a comment on discussion General Discussion

Hello, Mounir. 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows...

Kostja modified a comment on discussion General Discussion

Hello, Mounir. 1). Windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows...

Kostja modified a comment on discussion General Discussion

Hello, windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt, so that windows does not...

Kostja modified a comment on discussion General Discussion

Hello, windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available VeraCrypt disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt and windows accidentally did...

Kostja modified a comment on discussion General Discussion

Hello, windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt and windows accidentally did not format...

Kostja posted a comment on discussion General Discussion

Hello, windows has a logical partition, let's say a disk with the letter: “E”, when VeraCrypt formats, encrypting, then this letter: “E” cannot be used not by windows, not by VeraCrypt. There is a suggestion that VeraCrypt, when encrypting this partition, add this letter: “E” to its list of available disks, rather than ignore it and at the same time remove the letter: “E” from the windows system because windows cannot work with this partition without VeraCrypt and windows accidentally did not format...

Present Truth posted a comment on ticket #622

Hello. Veracrypt suddent stopped working today. I cannot access my files in Kali Linux. I tried uninstalling and reinstalling but I get the follow error when I try to reinstall the applmage: Error: Package 'libfuse2' has no installation candidate /tmp/.mount_VeraCrafodpE/usr/bin/veracrypt: error while loading shared libraries: libfuse.so.2: cannot open shared object file: No such file or directory I tried to install libfuse2 but also get this error: └─$ sudo apt update sudo apt install libfuse2 Hit:1...

Mounir IDRASSI posted a comment on ticket #622

@malcarada Thanks for the report. This is caused by the missing Fedora package fuse-libs which provides libfuse.so.2. The current Fedora RPM is linked against FUSE 2. On Fedora, the fuse package contains the FUSE 2 tools, while the runtime shared library libfuse.so.2 is in fuse-libs. Please install it with: sudo dnf install fuse-libs Then launch VeraCrypt again. Reinstalling VeraCrypt itself is not required. For future packages, I will provide Fedora builds linked against FUSE3 since FUSE3 support...

Poseidon created ticket #622

Veracrypt .rpm package stopped working in the latest Fedora 44

George posted a comment on discussion Technical Topics

Hoorah! Windows booted normally without VeraCrypt prompt for password. Thank you very much, good Sir.

Mounir IDRASSI posted a comment on discussion Technical Topics

@dc01 Thank you for the outputs. They show that Windows is decrypted and that the remaining prompt is only an EFI boot-loader cleanup issue. Your firmware boots Windows Boot Manager at: \EFI\Microsoft\Boot\bootmgfw.efi but that file is 25,160 bytes, the same size as VeraCrypt DcsBoot.efi. So the Windows Boot Manager path still contains the VeraCrypt loader. The original Microsoft loader is still present as: \EFI\Microsoft\Boot\bootmgfw_ms.vc Please boot Windows by pressing ESC, open Command Prompt...

Martin posted a comment on discussion Technical Topics

I want to connect and use an internal SATA HDD, encrypted as a VeraCrypt volume (non-system), in an external USB enclosure. Are there any potential encryption problems if the SATA HDD was originally connected internally when the VeraCrypt volume was created?

George posted a comment on discussion Technical Topics

Directory of S:\EFI\VeraCrypt 24.04.2026 22:44 . 24.04.2026 22:44 .. 24.04.2026 22:44 25 160 DcsBoot.efi 24.04.2026 22:44 934 744 DcsInt.dcs 24.04.2026 22:44 976 168 DcsCfg.dcs 24.04.2026 22:44 10 888 LegacySpeaker.dcs 24.04.2026 22:44 38 216 DcsInfo.dcs 24.04.2026 22:44 779 DcsProp 24.04.2026 22:50 2 255 PlatformInfo 7 File(s) 1 988 210 bytes 2 Dir(s) 70 473 728 bytes free

George posted a comment on discussion Technical Topics

Directory of S:\EFI\Boot 07.07.2021 17:54 . 07.07.2021 17:54 .. 09.04.2021 05:49 1 558 864 original_bootx64.vc_backup 24.04.2026 22:44 25 160 bootx64.efi 2 File(s) 1 584 024 bytes 2 Dir(s) 70 473 728 bytes free

George modified a comment on discussion Technical Topics

C:\Windows\system32>dir S:\EFI\Microsoft\Boot\bootmgfw* Volume in drive S has no label. Volume Serial Number is Directory of S:\EFI\Microsoft\Boot 24.04.2026 22:44 25 160 bootmgfw.efi 15.10.2025 11:53 1 604 016 bootmgfw_ms.vc 2 File(s) 1 629 176 bytes 0 Dir(s) 70 473 728 bytes free

George posted a comment on discussion Technical Topics

C:\Windows\system32>dir S:\EFI\Microsoft\Boot\bootmgfw* Volume in drive S has no label. Volume Serial Number is Directory of S:\EFI\Microsoft\Boot 24.04.2026 22:44 25 160 bootmgfw.efi 15.10.2025 11:53 1 604 016 bootmgfw_ms.vc 2 File(s) 1 629 176 bytes 0 Dir(s) 70 473 728 bytes free Directory of S:\EFI\Boot 07.07.2021 17:54 . 07.07.2021 17:54 .. 09.04.2021 05:49 1 558 864 original_bootx64.vc_backup 24.04.2026 22:44 25 160 bootx64.efi 2 File(s) 1 584 024 bytes 2 Dir(s) 70 473 728 bytes free Directory...

George posted a comment on discussion Technical Topics

C:\Windows\system32>bcdedit /enum firmware Firmware Boot Manager identifier {fwbootmgr} displayorder {bootmgr} timeout 1 Windows Boot Manager identifier {bootmgr} device partition=\Device\HarddiskVolume3 path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {e3c97977-df8e-11eb-b098-94c7dd1d002d} displayorder {current} toolsdisplayorder {memdiag} timeout 30

George modified a comment on discussion Technical Topics

Thank you for explanation. I've uninstalled VeraCrypt to 1.26.24. Installed VeraCrypt 1.24-Update7 (I had it in my backups). System > Permanently Decrypt System Partition/Drive is still available in the menu. When I select it VeraCrypt says "System partition/drive does not appear to be encrypted". I no longer have VeraCrypt recovery U-disk. I'll try Startup Repair from Windows Recovery Environment. Windows Startup Repair "couldn't fix my PC".

George posted a comment on discussion Technical Topics

Thank you for explanation. I've uninstalled VeraCrypt to 1.26.24. Installed VeraCrypt 1.24-Update7 (I had it in my backups). System > Permanently Decrypt System Partition/Drive is still available in the menu. When I select it VeraCrypt says "System partition/drive does not appear to be encrypted". I no longer have VeraCrypt recovery U-disk. I'll try Startup Repair from Windows Recovery Environment.

Jack Omen posted a comment on discussion General Discussion

That's great! Thank you so much!

VeraCrypt updated /VeraCrypt 1.26.24/veracrypt-1.26.24-sha256sum.txt

VeraCrypt updated /VeraCrypt 1.26.24/veracrypt-1.26.24-sha512sum.txt.sig

VeraCrypt updated /VeraCrypt 1.26.24/veracrypt-1.26.24-sha512sum.txt

VeraCrypt updated /VeraCrypt 1.26.24/veracrypt-1.26.24-sha256sum.txt.sig

Mounir IDRASSI posted a comment on discussion General Discussion

Thank you for the report. I have just built Ubuntu 26.04 packages for version 1.26.24 and they are now available on the download page and also here on Sourceforge

VeraCrypt released /VeraCrypt 1.26.24/Linux/veracrypt-1.26.24-Ubuntu-26.04-amd64.deb

VeraCrypt released /VeraCrypt 1.26.24/Linux/veracrypt-console-1.26.24-Ubuntu-26.04-amd64.deb

VeraCrypt released /VeraCrypt 1.26.24/Linux/veracrypt-console-1.26.24-Ubuntu-26.04-amd64.deb.sig

VeraCrypt released /VeraCrypt 1.26.24/Linux/veracrypt-1.26.24-Ubuntu-26.04-amd64.deb.sig

Jack Omen posted a comment on discussion General Discussion

Hi, I noticed last Ubuntu package is 25.04, though Ubuntu 26.04 is out now. Could you please make the package for the latest release available in the download section? Many thanks

Mounir IDRASSI posted a comment on discussion Technical Topics

Since pressing ESC at the VeraCrypt password prompt starts Windows, your system partition is not encrypted anymore. The remaining issue is that your firmware is still starting a VeraCrypt EFI loader. Deleting a boot option in UEFI setup only removes a firmware/NVRAM entry. It does not necessarily restore the EFI boot files on the EFI System Partition. During UEFI system encryption, VeraCrypt also works with the Windows Boot Manager path and keeps a backup of the original Windows loader. Please do...

Mounir IDRASSI posted a comment on discussion Technical Topics

The best tools for identifying the process that has open handle on mounted volume are Microsoft Sysinternals Process Explorer or Handle. Run them as Administrator. In Process Explorer, use Find > Find Handle or DLL and search for the mounted drive letter, for example X:. If nothing appears, also search for the VeraCrypt virtual device name \Device\VeraCryptVolumeX where X is the drive letter. From an elevated command prompt you can also use: handle64.exe -u X:\ handle64.exe -a -u \Device\VeraCryptVolumeX...

Mounir IDRASSI posted a comment on discussion General Discussion

There was no behavior change in VeraCrypt 1.26.24 related to this. The option "VeraCrypt Background Task -> Exit when there are no mounted volumes" applies only to the background task, i.e. after the main VeraCrypt window has been closed/hidden to the tray. If the main VeraCrypt window is left open, auto-unmount will unmount the volume, but it will not automatically close the visible GUI. What you are describing is a new feature: making the whole VeraCrypt process exit after auto-unmount if no volumes...

Mounir IDRASSI committed [f0f238] on Source Code

Update Language.de.xml (#1692)

Mounir IDRASSI committed [1b9058] on Source Code

Update Dutch translations (#1691)

Mounir IDRASSI committed [f30efa] on Source Code

Update Swedish translation (#1688)

Mounir IDRASSI committed [9e387f] on Source Code

Fix undefined behavior in StartElevated stderr read loop (#1550) (#1687)

Mounir IDRASSI committed [6b802a] on Source Code

macOS: harden FUSE-T SMB metadata handling

Mounir IDRASSI committed [0b554f] on Source Code

macOS: stabilize FUSE-T SMB mount metadata

Mounir IDRASSI committed [380f49] on Source Code

macOS: stabilize FUSE-T SMB auxiliary mounts

Mounir IDRASSI committed [114788] on Source Code

Windows: honor EFI boot menu options in PostOOBE repair

Mounir IDRASSI committed [b58cee] on Source Code

Update Polish translation (#1685)

Mounir IDRASSI posted a comment on discussion Technical Topics

This did not reach the GPT generation stage. The key line is: Encrypted already The preceding "Success" only means the H_OS password/header was accepted. It doesn't mean that -oshideprepcompleted. In this state the system header already has a non-zero EncryptedAreaLength, so DCS stops before asking for gpt_enc / gpt_hidden. For EFI hidden OS, -oshideprep must be run after the system-encryption header/test stage exists, but before H_OS in-place encryption has actually completed. Running it after H_OS...