.exe target on VS2022 builds tend to lock and not release?

[TBOpen]

I'm not sure if this is related to VeraCrypt, but it never happened when I used DriveCrypt and only started when I switch to use VeraCrypt. I'm using an encrypted file to build applications using VS2022. I can typically build the .exe once or twice and it works, but at some point the link fails because "fatal error LNK1168: cannot open 'xyz' for writing'. typically after debugging the application as well (running the .exe).

To work around the issue, I've been closing the solution/project, running "chkdsk /x d:" to force handles close, then open the solution and build and works fine again for a while.

If there is something someone can think of that would cause this and check it out, that would be a great fix.

I did also move from using NTFS to exFAT so that may be related as well.