Mounir IDRASSI

@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...

@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...

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

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...

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...

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...

Update Language.de.xml (#1692)

Update Dutch translations (#1691)