Invisible Context Menu Entries

Hi everyone.

I found a persistent and undesirable addition to my context menu that I was unable to disable with CCleaner as is my usual practice because CCleaner apparently could not see it. The entry showed up in the context menu for compressed files as "Extract with express zip." This probably entered the registry with a NCH software install. I did do a search for this subject but NCH is only three letters and this forum does not accept search terms less than four letters in length.

I was able to edit the registry and remove these entries, but I am wondering how they were able to evade CCleaner's eagle eye and therefore I am attaching a sample of one of the registry entries to help you with your development. This was for .rar files but I had to delete the entry from every conceivable compressed format possible. I used 'find' of course...:)

Edit:Could not upload .reg so I zipped it.

rarfie.zip

There are many posts online about NCH Software and the context menu items which seem to offer 'install on demand' options.

http://resource.dopus.com/viewtopic.php?f=3&t=16656

http://www.foxite.com/archives/irritating-program-express-zip-0000351578.htm

Not something I would want to install I think.

Welcome to the forum by the way :)

Yes, they do have a lot of buttons in their applications that you might accidentally press and launch an on-demand installer... only fair if it's freeware. But the clogging up of the context menu is the outside of enough, I feel.

Oh well, better the enemy that you know, what? They do have a nice chromatic tuner application and now that I've gone to so much hassle over it I guess I might as well keep it.

So do you think that the development team can include these context menu entries for disabling in a future ccleaner or has NCH found the perfect loophole?

Please note that you can simply change the extension from REG to TXT and then the file can be attached - no need to zip.

I am confused about your hopes and expectations of CCleaner.

The Registry Cleaner aims at redundant keys that designate something which is no longer present.

If the context menu can still launch an on-demand installer then what the key designates is very probably still present,

and so is outside the "rules of enemy engagement".

You might however have a valid BUG to report if your unwanted NCH context menu action is active BUT CCleaner fails to show it under

Tools / Startup / "Context Menu".

Was that the case ?

You might however have a valid BUG to report if your unwanted NCH context menu action is active BUT CCleaner fails to show it under

Tools / Startup / "Context Menu".

Was that the case ?

exactly. That's why I attached the key. I don't expect CC to deal with the software, just the registry key that adds a line to the context menu, resulting in menu bloat.

Please clarify :-

If you click on that unwanted context menu item, does it initiate an on-demand installation ?