FreeCommander right-click context menu not identical to Windows File Explorer

Bugs and issues - current donor version.
Post Reply
Message
Author
Muse2Us
Posts: 2
Joined: 06.10.2019, 20:00

FreeCommander right-click context menu not identical to Windows File Explorer

#1 Post by Muse2Us » 06.10.2019, 20:32

I am running FreeCommander 790a 64-bit on a Windows 10 Pro 1809 64-bit computer. When I right-click on a folder or file, the FreeCommander context-menu is missing a few menu entries when compared to the context-menu displayed by the Windows File Explorer. Two of the FreeCommander missing entries are part of the Symantic/Norton Security Package and the third is the Windows 'Pin to Taskbar' entry. I could live without the 'Pin to Taskbar' entry but I do use the NS scan folder/file for virus function regularly and I find it annoying having to switch to File Explorer and find the folder/file again, to perform that function. I should point out that I have made the same observation on a Windows 10 Pro 32-bit computer running FreeCommander 790a 32-bit.

I am assuming that both FreeCommander and File Explorer, go to the Windows registry entries to find the list of context-menu managers and the pointers to the function program executables. What could be different in the entries for Norton Security that would result in FreeCommander not 'seeing' the NS entries? I have checked the NS history log and I do not see any attempt by NS to block Freecommander access.

Timon
Posts: 688
Joined: 13.09.2012, 06:51

Re: FreeCommander right-click context menu not identical to Windows File Explorer

#2 Post by Timon » 07.10.2019, 09:48

Have a look at a similar problem with BitDefender - viewtopic.php?p=22743#p27596 and how it was solved

Muse2Us
Posts: 2
Joined: 06.10.2019, 20:00

Re: FreeCommander right-click context menu not identical to Windows File Explorer

#3 Post by Muse2Us » 07.10.2019, 21:12

Timon,
Thank you. The post you referenced identifies the same issue as it relates to BitDefender. The post points out that if you rename the executable of BitDefender to explorer.exe, the Norton Security context-menu entries return. Renaming the FreeCommander.exe to explorer.exe, has the same result. Running FreeCommander.exe as explorer.exe returns the context-menu entries. That begs the question, is this a Windows or Norton Security bug, or a Norton Security feature by design.

As far as I can tell, this Norton Security issue has been reported as early as 2013. Some reports reference a loss of Norton Security context-menus entries in Windows Explorer also. These tend to resolve themselves shortly after a Norton Security update and are different from what we are reporting here. Some posts on the Internet get responses from Norton indicating that the behavior is by design (non-Windows Explorer file manager no longer get context-menu support, without explanation as to why) and other responses that Norton is looking at the issue, followed by silence.

If it is by design, It may be that Norton thinks that providing direct access to file managers through the context-menu is a security risk for them, one that they are willing to accept with a known, Windows File Explorer. This approach makes no sense, since a simple rename of the executable to explorer.exe circumvents that protection.

The above post ends with an unanswered question, what is the long term effect of renaming the executable to explorer.exe? If the file manager was installed using the Windows setup or msi process, the executable is located in Program Files or Program Files (86) folder, so you will need Administrative access to the folder. When you need Administrative to perform a Windows function, it suggests that you are trying to fool mother nature. Changing the name at least results in a mismatch between the folder content and the Windows Registry. That at minimum could impact future uninstall of the program. If FreeCommander is installed as a portable app, that can be avoided.

You have identified a workaround that probably is a reasonable solution for most FreeCommander users, especially those with portable installs. I pay good money for yearly subscriptions so I may shake Norton's tree and if anything falls, I'll report back here.

Post Reply

Who is online

Users browsing this forum: No registered users and 117 guests