(Bug) Veracrypt container always has to be dismounted forcefully because of a system process.

[interested-user-1]

This process is usually using the drive, so I have to force dismount. Now, I've heard this is common for the drive Windows is running on, but this is the A: Drive, so there shouldn't be any reason for it to exist. I have to check procexp every time I dismount the container forcefully just in case something actually important is in use (to prevent corruption).

Does anyone know how to fix this? I've been thinking of making an ext4 container instead, but since my drive is in NTFS...

[ColorfulResponse]

This definitely isn't a bug, it's something on your end. There's a process running that is using something that's on the drive. You need to end that process before you unmount and then you won't have this issue.

[interested-user-1]

So I've been browsing some forums and it seems that this is Windows' method to journal for NTFS (not sure if it's true). Anyway, since it's a system process, I don't think I could kill it. That's why I was considering switching to ext4, do you think it's fine to run an ext4 container on an NTFS drive?

There's a solution listed here but since Veracrypt doesn't create a 'real' drive, it doesn't show up on the Drive Management utility (At least that's why I think it doesn't). I guess I could mount it on another letter in the future, though it would break many of my shortcuts...

Then I have went to ComputerManagement->DriveManagement utility and I have removed any drive-letter assignements for that drive. Instantly afterwards, I was able to eject the drive. Then I tried connecting it again, reassigning the drive letter, switching it to quick-removal and it seems to work properly and still be ejectable.

There's also this method

I think that the "turn the drive offline" via "computer management -> drive management" might actually be the quickest solution, however I have not tried it since my random attempts helped before I've read about that.

But my Veracrypt drive doesn't show up on that utilty even though it does on File Explorer