Hi, Your report is not ignored. In fact, another user has reported the same issue on Github which I replied to yesterday: https://github.com/veracrypt/VeraCrypt/issues/1779 I have been working on this. Short answer: there is an issue in FUSE-T backend related to unmounting which leaves FUSE-T process running. I'm trying to find the best approach to handle FUSE-T unmount, especially when done through Finder which is outside the control of VeraCrypt. There are other issues reported in relation to FUSE-T....
Unix: add doas elevation support
Linux: retry auto FAT mounts with blkid
Unix: make Pipe::Close idempotent
Unix: honor configured pthread stack size
Move new macOS filesystem strings to end of language files
macOS: honor the CheckFilesystem repair flag (#1791)
Typo fix in Spanish translation (#1794)