Marcos

It should work if you select the desired computers and then select Manage -> Remove. Please make sure to follow all 3 steps especially if settings are protected with a password:

It is ok that bcd.log cannot be opened for scan, just ignore it. It can't be accessed even with elevated admin rights:

ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 17.1.11 have been released and are available for download. Changelog: Version 17.1.11 FIXED: transparency lag while moving the application window FIXED: BSOD on Win10 RTM build Known issues: N/A Upgrade to Latest Version Upgrade my ESET Windows home product to the latest version If your ESET security product has not updated automatically yet, you can enforce product update by manually checking for update in the Update panel or wait until it updates automatically. Support Resources ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support. Online Help (user guides) Visit www.eset.com/contact to email ESET technical support

ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 17.1.11 have been released and are available for download. Changelog: Version 17.1.11 FIXED: transparency lag while moving the application window FIXED: BSOD on Win10 RTM build Known issues: N/A Upgrade to Latest Version Upgrade my ESET Windows home product to the latest version If your ESET security product has not updated automatically yet, you can enforce product update by manually checking for update in the Update panel or wait until it updates automatically. Support Resources ESET provides support in the form of Online Help (user guides), fully localized application and Online Help, online Knowledgebase, and applicable to your region, chat, email or phone support. Online Help (user guides) Visit www.eset.com/contact to email ESET technical support

Currently there are no such plans as this was probably the first such request.

The string is not added by ESET to the subject of email. The best I could find is the following explanation although without a reference to particular software that adds it: The {disarmed} flag in the subject line of a filtered email indicates the system has located a "Web Bug" or tracking code and has disabled it. A "Web Bug" is a piece of code attached to an email that is invisible to the reader, but sends tracking information to a remote server that would then keep track of information such as when you opened the email, what kind of computer you are using, what your IP address is and so forth which the sender (or sending server) could use to identify you. This type of tracking code is most often found in HTML "newsletters" and spam messages to track when users open and read their e-mails. The filters prevent that information from getting back to the sender to protect privacy. This helps prevent the further propagation of spam, because once an email address is verified as real, and that a human viewed it, the now-confirmed email address will tend to make its way to other senders. https://www.virtbiz.com/client/index.php?rp=/knowledgebase/14/Email-arrives-that-says-it-has-been-disarmed.html

Unfortunately not, it used to work for some users who reported similar issues in the past.

V11.0.2044 is the latest version of ESET Endpoint products for Windows. Not really, it was a redundant setting controlling an obsolete way of hooking that was not supported on modern Windows systems anyways.

Thank you, I've forwarded the dumps to developers for perusal. Will keep you posted. P_ESSW-18149

We spoke to Michel Mayor about the importance of public engagement with science and fostering responsibility among the youth for the preservation of our changing planetView the full article

If disabling SSL/TLS filtering doesn't make any difference, then it should be unrelated to ESET.

The detection is correct. The malicious JS loads @Trojan.JS/Spy.Banker.MP:

For me it works. I could create a rule in override mode, put it above the blocking rule applied by a policy and enable or disable it. Please raise a support ticket to find out why it doesn't work for you.

Dr. Israelian talks about Starmus's vision and mission, the importance of inspiring and engaging audiences, and the strong sense of community within the Starmus universeView the full article

That should work too.

You can raise a support ticket by going through the troubleshooting wizard at https://go.eset.com/contact-support/. In order to create a pcap log, apply an agent policy that will set 1-minute interval for replication and let Wireshark log the communication for 2-3 minutes to ensure that a connection attempt will be logged.

It will be necessary to check a pcap log with the network communication captured during an attempt to contact the ESET PROTECT server by the agent, hence I'd recommend raising a support ticket for help with further troubleshooting: ERROR: InitializeConnection: Initiating replication connection to 'host: "eset.ipXXXXXXio.local" port: 2222' failed with: Response for request of type DeviceSessionTokenRequest (request id: 40120) was not received in time

Please provide a kernel or better complete memory dump from a crash to determine the cause of the issue. The dumps provided by Cubex Group did not show ESET being the culprit but we're still analyzing them.

Please provide a dump of egui_proxy.exe and ekrn.exe when the icon is constantly spinning. If you hover the mouse cursor over the icon, does it say that update or scan is in progress? Does the icon keep spinning for hours?

It should be possible to create IDS rules that will enable pop-up notifications for network attacks. However, keep in mind that computers accessible from the Internet are usually constantly attacked which would result in numerous pop-up notifications the user would be getting.

The only way how not to display this notification is by activating gamer mode or disabling desktop notifications completely:

Please check if DNS resolves eset.ipXXXXXXio.local on the machine (some letters in the actual hostname were obfuscated with X).

Status.html should clearly state what the problem is. You can upload the logs here for perusal. Attachments are accessible only by ESET staff.

Please delete the folder C:\Users\%UserName%\AppData\Local\ESET\ESETOnlineScanner and install ESET Online Scanner again.

This is caused by a change in the latest kernel. We are working on an update which will take some time. As a workaround, you can rollback to kernel 6.1.0-18-amd64. P_EFSU-4276