Thanks. Where is that quote from? It does work when FreeCommmander is renamed to explorer.exe, but I'm not sure of the consequences of doing so. Will it mess anything up in the OS? It seems like a bug within Bitdefender. Is there a way to submit bugs to them to get it fixed?
The comments were taken from this thread: https://freecommander.com/forum/viewtopic.php?f=6&t=7083 And, it is not a bug of Bitdefender, it is "by design":