Force NOD32 entry in Opus context menu

For those using NOD32, what's the correct command (and CLSID) to show the entry in the right-click context menu in Opus?

I tried adding in Filetypes > All Files and Folders > Context Menu:

FileType CONTEXTFORCE CONTEXTMENU={B089FE88-FB52-11D3-BDF1-0050DA34150D}

but nothing appears.

Seems like one of these should work, but none do. Maybe because it's done via PackagedCOM now:

FileType CONTEXTFORCE CONTEXTMENU=EsetContextMenu_18.2.17.0_neutral__f55j32bkf4yvt
FileType CONTEXTFORCE CONTEXTMENU={B089FE88-FB52-11D3-BDF1-0050DA34150D}
FileType CONTEXTFORCE CONTEXTMENU={938301B7-1649-4A50-81E2-77D74D79D6C5}

Although having a version number in the Packaged COM ID means that even if that did work, it wouldn't work for long. Nothing about Packaged COM makes sense or is an improvement on what we already had, but that sums up Microsoft and Windows in general these days.

Maybe we can find a way to make it work.

We’ll add a way to make this work in the next beta.

2 Likes

In Opus v.13.1.8.3 I tried all of this, but none of it works:

FileType CONTEXTFORCE CONTEXTMENU=package:EsetContextMenu*/{938301B7-1649-4A50-81E2-77D74D79D6C5}
FileType CONTEXTFORCE CONTEXTMENU=package:EsetContextMenu*/{B089FE88-FB52-11D3-BDF1-0050DA34150D}
FileType CONTEXTFORCE CONTEXTMENU=package:*/{938301B7-1649-4A50-81E2-77D74D79D6C5}
FileType CONTEXTFORCE CONTEXTMENU={938301B7-1649-4A50-81E2-77D74D79D6C5}

I can see that the registry entry for ...EsetContextMenu_18.2.18.0_neutral__f55j32bkf4yvt\Class\{938301B7-1649-4A50-81E2-77D74D79D6C5} exists, so I don't know what I'm doing wrong.

It works OK here, fwiw.


Good(?) news: It's also not working for me on at least one of my machines. I'll try and work out what's going wrong.

1 Like

I have been using Eset Internet Security largely because I can purchase a 3 license version very cheaply here in late November.

I found the same CLSID listed in this thread's initial post and also could not get it to work in a menu.

I fixed it !
There was something wrong with my copy and paste from the forum.
I tried to move CONTEXTFORCE to the end of the command and my menu started working.

I then moved CONTEXTFORCE back to immediately after Filetype to check if it still did not work, but it now does.

FileType CONTEXTFORCE CONTEXTMENU={B089FE88-FB52-11D3-BDF1-0050DA34150D}

Edit Note : Yes, I had a file selected when it did not work.
I really don't know what the cause was.

I tried moving CONTEXTFORCE around as you did, but that did nothing for me.
The ESET context menu content still doesn't show.

Looks like you're using Windows 10, from the RegEdit screenshot's scrollbar style.

NOD32 only uses the new UWP menu type in Windows 11.

The next beta has a fix for this.

Correct command is still the first one (same as in the release notes):

FileType CONTEXTFORCE CONTEXTMENU=package:EsetContextMenu*/{938301B7-1649-4A50-81E2-77D74D79D6C5}
1 Like

Confirmed. Thanks.

1 Like