Blacklisted drive letter? Executing files gives Security Warning, Do you want to run this file?

[Mike Lynch 0]

Win version 24H2 26100.6901

I switched from Windows 10 to Windows 11 a few months ago and ever since I have been experiencing trouble with one of my internal drives (that has been in use for years on W10 without issue).
It's an encrypted (VeraCrypt) volume from which I am unable to execute files (exe, bat, lnk) without a Security Warning (see attached screenshot for an example).
I have several other VeraCrypt volumes that do not experience this problem, and there is nothing meaningfully different about how they are mounted or set up that I can see.

The most curious thing is, if I mount the drive under a different drive letter, the issue does not appear. Moreover, if I mount a different drive under the "problematic" drive letter (F), I start getting warnings when executing things on that drive. So, it can't have anything to do with the specific executables themselves, it seems. It's only the fact that they are located, sometimes, on a path that starts with F:\... that gives Windows reason to mistrust them.
In short, Windows seems to have "blacklisted" drive letter F on my system.

I also stumbled across another workaround that I don't understand why works, which is to run the following batch file after the drive has been mounted:

Batch:

taskkill /F /IM explorer.exe
start explorer

So, not only is it blacklisting drive F, it seems to do so (or remember to do so) at the time the drive is mounted, not before.

Any clues as to what part of Windows might do something like that and where one might go to fix this?

I would rather not change drive letter permanently as I've gotten extremely used to it being "the F drive".
I am also aware that I could disable that part of Windows Security entirely, so that no warnings are given for any files at all. But I'd rather not do that, either.

Thanks in advance for any insight...

 

[Trevor Neale 0]

Right click on an exe file and select properties. If you find a message that says "This file came from another computer and might be blocked..."
Uncheck the box and click apply. Then you should be able to run it. You can do that for all of your files one by one, or just run this command in Powershell to unblock all the files in the folder.

Get-ChildItem -Path "F:/(folder name)" -Recurse | Unblock-File