veracrypt
Mounting fails if keyfiles are on a read-only NTFS volume
Expected behavior
On Windows and with portable version (not tested others): Mounting a volume shouldnt need write access to the keyfiles, so the volume read-only status shouldnt matter
Observed behavior
Windows alert modal popup, suggesting uncontrolled error trap. Volume mount fails
Steps to reproduce
Using the portable windows version: Create a volume using key files Put the keyfiles on an NTFS disk in Windows Using Diskpart, set the volume to READ ONLY with the following commands in CMD.exe (console):
DISKPART LIST VOL SELECT VOL (NUMBER) - use the number that represents the volume where the keyfiles were stored ATTRIBUTES VOLUME SET READONLY check the status is read only using DETAIL VOL if wanted, EXIT
Try to mount the volume using the keyfiles on the read-only NTFS volume. Fails badly.
(Afterwards if wanted the command to clear readonly is ATTRIBUTES VOLUME CLEAR READONLY, executed the same way)
Screenshots
Your Environment
VeraCrypt version: portable 1.25.9 - same happens on newer builds. Not tested on other platforms and non portable. Operating system and version: Win 10 22H2 19045.3570 x64
Can't reproduce on either 1.25.9 or master.
My VM is Windows 10 Pro Edu, 22H2 19045.3324, the drive on which the keyfile is located on and which was set to read-only is a .qcow2 SATA disk image.
