Changes between 1.26.30 and 1.26.31 (2 November 2026):
-
All OSes:
- Update translations and documentation.
-
Windows:
- Fix upgrades from VeraCrypt 1.26.30 that could fail while replacing the system service executable. Wait for the service process to exit, retry locked files and defer replacement until Windows restarts when necessary.
- Fix MSI upgrades on systems with an encrypted system drive, including migration of original bootloader backups, bootloader updates and Secure Boot compatibility checks.
- Report Windows feature-update configuration, recovery-backup migration and system-service update failures as warnings identifying the affected file or registry value, allowing installation, uninstallation and system-encryption operations to finish. Retry feature-update configuration when the system service starts.
- Warn when a new Rescue Disk would reuse a Windows Boot Manager backup signed by Microsoft Windows Production PCA 2011 during migration to Windows UEFI CA 2023. Recreating the Rescue Disk does not update this stored backup.
- Improve protection and cleanup of the legacy system encryption support directory under ProgramData, including read-only files and redirected paths. Preserve recovery backups and retain old driver files until Windows Setup registration changes are verified.
- Avoid repeated warnings caused by unrelated incompatible language packs. When no compatible pack is available for the selected language, display a single warning and fall back to English while preserving the language preference.
-
Linux, macOS and BSD:
-
Security: Prevent programs launched by VeraCrypt from inheriting the pipes between its interface and service, which could let them use an active administrator session. This extends the protection added in version 1.26.30.
- Reported by aorakko.
-
Security: Prevent programs launched by VeraCrypt from inheriting its open files, devices and internal pipes.
-
Fix cases where VeraCrypt could hang while waiting for system tools used to mount volumes or open them in a file manager. Improve timeout handling for these tools.
-
Document that permission to run VeraCrypt or its core service as root through
sudoordoasgrants full root authority. See the security model. -
Fix mount-point validation for directories that do not yet exist, including paths containing
..or symbolic links. (GH #1973)- Reported by aorakko.
-
Restore compatibility with GCC 4.4 for Unix GUI and console builds.
-
Improve password dialog titles for long volume paths, preserving the volume file name where possible and adapting to window resizing.
-
-
Linux and BSD:
- Only default mount-point names, consisting of the configured prefix followed by a slot number from 1 to 64, receive automatic directory creation, ownership changes and removal. Custom mount points such as
/media/veracrypt-backupor/media/veracrypt1/photosmust already exist with suitable permissions; sharing the default prefix no longer makes them automatically managed.
- Only default mount-point names, consisting of the configured prefix followed by a slot number from 1 to 64, receive automatic directory creation, ownership changes and removal. Custom mount points such as
-
Linux:
- Add optional Ayatana AppIndicator support to RPM and Arch Linux package builds for system tray integration, including on KDE Wayland. (GH #1339)
Merged Pull Requests
- Common: make derived key buffer alignment explicit in CreateVolumeHeaderInMemory by @bernardladenthin in #1843
- Complete and refine the Swedish translation by @NickWick13 in #1951
- Update Norwegian Bokmål translation by @sandakersmann in #1975
- Update Polish translation by @Matthaiks in #1976
Full Changelog: VeraCrypt_1.26.30...VeraCrypt_1.26.31