ESET Cyber Security version 8 has the finder extension bug

[Chas4 11]

Seen it with 2 other Finder extensions, no clue what triggers this bug

 

[Robertos 68]

Thank you, it seem as bug. We will look on it.

[Robertos 68]

Chas4, what version of macOS is on affected device?
Could you see ESET firewall items in Finder context menu? Muse be tested under admin account and in folder where applications are stored . e.g. /Applications/

Edited November 13 by Robertos

[Chas4 11]

1 hour ago, Robertos said:

Chas4, what version of macOS is on affected device?
Could you see ESET firewall items in Finder context menu? Muse be tested under admin account and in folder where applications are stored . e.g. /Applications/

8.2.800.0

No firewall menu items nor any ESET Finder context menu items

It is not instant but over a few days they grow (that is after 9 days of uptime)

Edited November 13 by Chas4

[Chas4 11]

Is there context menu items yet in version 8 of the stable builds?

[Robertos 68]

Yes, the context menu is available, but it will only appear when you’re in a folder containing an application, such as the /Applications folder.

Also, I was asking for your macOS version, not the product version. Could you please let me know which version of macOS you're using?

[Chas4 11]

7 minutes ago, Robertos said:

Yes, the context menu is available, but it will only appear when you’re in a folder containing an application, such as the /Applications folder.

Also, I was asking for your macOS version, not the product version. Could you please let me know which version of macOS you're using?

macOS 11 (current version of Big Sur)

Never seen any context menu item

 

Also some reason your text is black even in dark mode.

Edited November 14 by Chas4

[Robertos 68]

Hello,

After investigating the issue, we've determined that this behavior is not a problem, but rather how macOS manages Finder extensions.

A single Finder extension can have multiple instances, and macOS controls the initiation and termination of these instances. As a result, we are unable to exit an instance until macOS calls for it to close. 

For example, the Finder extension process can be initiated by an open-file or save-as dialog. If the user closes the application that used the dialog to create an instance of our Finder extension, you'll notice that the extension process will exit as well once the application is closed. 

[Chas4 11]

1 hour ago, Robertos said:

Hello,

After investigating the issue, we've determined that this behavior is not a problem, but rather how macOS manages Finder extensions.

A single Finder extension can have multiple instances, and macOS controls the initiation and termination of these instances. As a result, we are unable to exit an instance until macOS calls for it to close. 

For example, the Finder extension process can be initiated by an open-file or save-as dialog. If the user closes the application that used the dialog to create an instance of our Finder extension, you'll notice that the extension process will exit as well once the application is closed. 

Sadly it does not close on its own, or even if the app is not open the macOS bug is triggered, seems it is one Apple never fixed