A question about the right-click menu

[zhangyang9527 0]

Windows 7 Sp1

ESET NOD32 Antivirus  14.1

 

Right-click on the folder,I can find the scanning options.

But right-clicking on a single file,there is no scanning options😭

Is this normal?

[Marcos 5,074]

From the screen shot it is not clear what is the extension of the file you clicked.

Make sure that HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\ESET Security Shell exists and its default value is {B089FE88-FB52-11D3-BDF1-0050DA34150D}.

[zhangyang9527 0]

3 hours ago, Marcos said:

From the screen shot it is not clear what is the extension of the file you clicked.

Make sure that HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\ESET Security Shell exists and its default value is {B089FE88-FB52-11D3-BDF1-0050DA34150D}.

HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\ESET Security Shell do exists

but its default value is {B089FE88-FB52-11D3-BDF1-0050DA34150D},and I can't edit it

I have reinstalled ESET,the problem still exists

[Marcos 5,074]

What if you right-click a file with the exe extension? Does the option to scan the file with ESET appear in the menu? If not, please open a support ticket with your local ESET distributor.

[zhangyang9527 0]

14 minutes ago, Marcos said:

What if you right-click a file with the exe extension? Does the option to scan the file with ESET appear in the menu? If not, please open a support ticket with your local ESET distributor.

exe、doc、xls、jpg、mp4、dll、rar、zip....anything you can think of，all the same...

Only right-click on the folder the scan option will appear

I used to use Kaspersky（already uninstalled），Maybe it caused a problem with my operating system

so,let it be,I can bear it

and Thank you very much! Your help makes me feel good about ESET

[itman 1,659]

This is a weird one. I haven't been able to find a file extension that cannot be scanned via Eset context scan option.

[zhangyang9527 0]

12 hours ago, itman said:

This is a weird one. I haven't been able to find a file extension that cannot be scanned via Eset context scan option.

I can still drag the file into ESET to scan,It's just not very convenient😞

[itman 1,659]

23 hours ago, zhangyang9527 said:

HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\ESET Security Shell do exists

but its default value is {B089FE88-FB52-11D3-BDF1-0050DA34150D},and I can't edit it

Another possibilty is Eset cannot inject its .dll into Windows Explorer for some reason.

Using Process Explorer, verify that Eset's .dll exists in Windows Explorer per beow screen shot:

[zhangyang9527 0]

12 hours ago, itman said:

Another possibilty is Eset cannot inject its .dll into Windows Explorer for some reason.

Using Process Explorer, verify that Eset's .dll exists in Windows Explorer per beow screen shot:

You are right👍 that Eset's .dll does not exist in the process

But i don't know why😢

[itman 1,659]

11 hours ago, zhangyang9527 said:

But i don't know why

You previously posted that you used Kaspersky previously. Check if there is a cleaner utility that exists that is designed to remove all traces of it.

Do you have any other security or security-like software installed? Do you have Adguard installed?

[Mr_Frog 14]

9 minutes ago, itman said:

Do you have any other security or security-like software installed?

I saw he also installed Qihoo 360:

https://www.360totalsecurity.com/en/

 

 

[zhangyang9527 0]

21 minutes ago, Mr_Frog said:

I saw he also installed Qihoo 360:

https://www.360totalsecurity.com/en/

 

 

Qihoo 360 has no anti-virus capabilities at all, I only use it to clean up files such as operating system caches.

After uninstalling Kaspersky, I used Qihoo 360 to clean up the windows registry.

But usually I don’t allow Qihoo 360’s process to start with windows.

Maybe Kaspersky or Qihoo360 damaged the registry and caused ESET's problem

[itman 1,659]

Per SysInternals Autoruns, there should be two Eset registry entries for explorer.exe per below screen shot. I believe that one of those entries is not being initialized on your device leading to Eset context scan option missing at the file level. Uninstall Qihoo 360 and see if that resolves this issue.

 

[zhangyang9527 0]

10 hours ago, itman said:

Per SysInternals Autoruns, there should be two Eset registry entries for explorer.exe per below screen shot. I believe that one of those entries is not being initialized on your device leading to Eset context scan option missing at the file level. Uninstall Qihoo 360 and see if that resolves this issue.

 

When I installed ESET, Qihoo 360 was turned off, it will not interfere with the installation of ESET.
If Qihoo 360 causes system damage, then the damage was caused before ESET was installed, so uninstalling Qihoo 360 will not work.
Today I tried it on my laptop (I also uninstalled Kaspersky and installed Qihoo 360), and everything worked fine.
This is so weird