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

LesFerch said:

unless there is an IP address or host name associated with your drive F, I'm not sure if this is any help.

Click to expand...

Hmm, is there any way I could find out that information? Or any clue as to why or how that could even happen?

FMBz said:

Hmm, is there any way I could find out that information? Or any clue as to why or how that could even happen?

Click to expand...

All I know is that Windows is treating your drive F as a network drive that is not part of your local Intranet.

Since you have a good profile (i.e. the new local account) to compare to your profile, it should be possible to find the important difference(s) (probably in the registry) by using comparison tools and a lot of time to wade through mountains of unrelated differences. It usually takes less time to move to the new account, but I understand that you don't want to do that.

If it were my machine, I would really want to find the root cause, so I'd spend hours exporting registry keys and comparing With Beyond Compare. You might be able to shortcut the process a bit by searching for F: references.

Speaking of wild, I'm just taking a wild guess here but do you suppose it might have anything to do with "advanced sharing" of the hard drive itself?

Try3 said:

look in
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2
for mapped network paths

Click to expand...

FMBz said:

I have indeed found entries for F (as well as my other VeraCrypt drive, G) under
MountPoints2

Click to expand...

The tutorial also says that mapped drive records are made in two other Registry places

Brink said:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\<share name>
HKEY_CURRENT_USER\Network\<Drive letter>

Click to expand...

They would seem worth checking.
Map Network Drive - ElevenForumTutorials


Denis

Try3 said:

The tutorial also says that mapped drive records are made in two other Registry places


Denis

Click to expand...

Neither of them have any entry for F. In fact \Map Network Drive MRU\ does not exist at all on my system.

Scannerman said:

Speaking of wild, I'm just taking a wild guess here but do you suppose it might have anything to do with "advanced sharing" of the hard drive itself?

Click to expand...

Doubt it, but just in case I did the old "turn it on and off again" thing, i.e. shared the F drive and then unshared it again. Don't think it changed anything.


In the meantime I've tested what would happen if I power up the old HDD Ive used before, assign it the letter F, and then (unlike before) reboot the system with that HDD still powered.
The effect is that in the new session, programs on that HDD (F) can be run as normal. However, this is temporary, just like the other workaround Ive described. If I power off that HDD or move it to a different letter, then reboot (or log off the user and log back in), the effect goes away again.

To put it differently, if the system (or specifically, Explorer.exe) starts while there is an "F" of any kind present, everything is fine.
But if there is no "F" present when Explorer starts, then adding an F drive later means that drive is not trusted.

I have also done a few registry snapshot comparisons, as some have suggested, but nothing really stands out to me so far.

Do you have an extraneous keys under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones? By that I mean you should have keys 0 through 4. Anything else is odd.

pseymour said:

Do you have an extraneous keys under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones? By that I mean you should have keys 0 through 4. Anything else is odd.

Click to expand...

Nothing besides 0-4. I also have reset all zones to default at one point recently.