I have a 4TB M.2 NVMe drive that I mount as a device volume in VeraCrypt. I am currently running 1.26.24, but the volume was created using an earlier version of VeraCrypt. The problems are recent and started happening months after upgrading VeraCrypt.
When initially-mounted, the drive functions normally, but after a period of time (hours, days, maybe after a few hibernations/sleeps) accessing the drive begins to throw errors. This only started happening a few days ago, and may be associated with a Windows update (Win11 x64 Enterprise).
When trying to create a folder: "An unexpected error is keeping you from creating the folder. It you continue to receive this error, you can use the error code to search for help with this problem. Error 0x8007701B1: A device which does not exist was specified" Note that I can continue to read from files, when this happens, just not write.
Trying to save a file on the volume fails. No specific error. For example, Excel will say "Error were detected while saving XXXX."
Sometimes trying to open a folder results in an error (my apologies for not noting the specifics).
The problem is resolved by unmounting the drive, rebooting the computer, and re-mounting the volume. I'm unsure if the reboot step is necessary.
I have a 4TB M.2 NVMe drive that I mount as a device volume in VeraCrypt. I am currently running 1.26.24, but the volume was created using an earlier version of VeraCrypt. The problems are recent and started happening months after upgrading VeraCrypt.
When initially-mounted, the drive functions normally, but after a period of time (hours, days, maybe after a few hibernations/sleeps) accessing the drive begins to throw errors. This only started happening a few days ago, and may be associated with a Windows update (Win11 x64 Enterprise).
The problem is resolved by unmounting the drive, rebooting the computer, and re-mounting the volume. I'm unsure if the reboot step is necessary.