Marcos

Since this is an English forum, we kindly ask you to post in English.
Do you have the latest version 17.0.15 installed? Please follow the instructions on the download page, create an ESET HOME account first and add the license there. You can then activate the product from ESET HOME or from the product via your ESET HOME account.
 

Honestly it is not fair to blame ESET if you purchase a license from an unauthorized seller who sells licenses to several users for instance and the licenses are then canceled. The solution is to ask for a refund and purchase one from an authorized distributor or reseller.

Honestly it is not fair to blame ESET if you purchase a license from an unauthorized seller who sells licenses to several users for instance and the licenses are then canceled. The solution is to ask for a refund and purchase one from an authorized distributor or reseller.

This is an old detection from 2012 and the file with the said hash is not detected. If you reboot the machine and restore the file from quarantine is it still detected? If so, please provide logs collected with ESET Log Collector from the machine.

If possible, please switch to the pre-release update channel some non-critical Windows Server 2012 R2 systems and check if the modules load alright. Then you can switch back to the regular update channel.
We have adjusted the signing process to make work also on Windows 8.1 systems and have tested module updates on our Windows Server 2012 R2 without issues. We're going to use it for signing modules on the regular update channel as of the next week so we would appreciate feedback from you.

This should not be necessary, as MarcFL wrote, clicking Dismiss in the warning should suffice and the protection status will be green. The eicar test file is detected then so protection seems to work fine. We'll make some further tests to make sure. So far it appears to be a glitch with the notification during modules reload after update.

Cleaner 1245 is currently on the pre-release update channel. We'll continue with the release once the Antivirus and antispyware module 1605.2 with a workaround for the issue has been received by all users.

Thank you for the heads-up. The issue has been reported to developers and is tracked.
P_ESSW-17553

We'll need to release the Antivirus and antispyware module 1605.2 to all users first (most likely within a week) and then we'll continue with the release of the Cleaner module 1245.

Anyways, we will internally discuss a better and more prominent placement for changelogs as they are now quite buried on the website.

If you choose to uninstall v17, it's possible to export the configuration also on non-ACS systems:

EIS v16 can be downloaded from https://download.eset.com/com/eset/apps/home/eis/windows/v16/latest/eis_nt64.exe.

Please provide logs collected with ESET Log Collector.

The extension is installed only into supported browsers. If a particular browser parasitizes another supported browser's extensions, we can't do anything about it.

According to https://help.eset.com/essp/17/en-US/idh_config_bps.html, supported browsers are; Google Chrome, Mozilla Firefox and Microsoft Edge.

I'm afraid we can't prevent Brave from reading the extension from Chrome or to prevent getting it from Chrome webstore via Brave. The point is not to install it since Brave is not a supported browser. We'll add a notice in the documentation and possibly KB as well.

The
The Configuration module 2099.5 which addresses the issue is currently available on the pre-release update channel with staggered updates on the regular update channel to follow soon. It should be fully released towards the end of November.

V17 has been released worldwide, however, automatic update is currently available only for those who update from the pre-release update channel, however, you can also upgrade to it using the installer from the website.
The issue you are referring to was caused by the fact that upgrade was initially allowed only on systems without Azure Code Signing support. This was fixed and if you attempted to update from the pre-release update channel now, older versions on non-ACS enabled systems would not upgrade to v17.
While we're still working on resolving an issue with a subscription validation notification in gui that affects some users who have upgraded, it can be fixed by deactivating the product from ESET HOME and re-activating it. Once this has been fixed on the backend, we'll enable staggered product updates to v17 again.

Yes, the Banking Payment and Protection module 1331 that addresses the issue is going to be fully released on the regular update channel within an hour.

I have no clue how your TV is connected to your LAN.
Anyways, if you can reproduce the detection easily, please carry on as follows:
Enable advanced logging under Help and support -> Technical support Reboot the machine Wait until ARP cache poisoning is detected (should it take too long, don't create advanced logs) Stop logging Collect logs with ESET Log Collector and upload the generated archive here.

Couldn't it be that the TV is connected to LAN both via a network cable and wi-fi? If so, you might want to create an IDS exception.

ESET NOD32 Antivirus, ESET Internet Security and ESET Smart Security Premium version 17.0.15 have been released and are available for download.
Changelog:
Version 17.0.15
ADDED: New ESET Security Ultimate (ESU) product and new subscription offering: ESET HOME Security Essential, Premium and Ultimate
ADDED : VPN (ESU)
ADDED: Identity Protection - USA (ESU)
ADDED: Browser Privacy & Security:
Metadata cleaner
Browsing cleaner
Secure Search
Website settings review (ESU)
CHANGED: Banking & Payment Protection renamed to "Safe Banking & Browsing"
CHANGED: Safe Banking and Browsing: Clipboard protection setting added to advanced setup
REMOVED: Banking & Payment Protection redirector
ADDED: Firewall rule editor: drag and drop supported for headers
ADDED: Additional configuration options in the interactive firewall dialog
ADDED: Azure Certification Signature (ACS) - Operating system update with Azure certificate necessary to install or upgrade ESET products
CHANGED: Subscription support
Other improvements and bugfixes
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

Did you try to switch to the pre-release update channel in the advanced update setup?

Dear users,
Another year has passed and we would like to thank you all for being our users and fans, especially to those who have been active and helpful in our forum and contributed to our mutual endeavor to defend our digital worlds. My special thanks to Itman for his tireless presence here and willingness to help the others
We would like to ask you to spend a few minutes and give us feedback on how we were doing, what you like about ESET and what is not that good and where we could improve. We endeavor to listen to your feedback, tailor the products to your needs and liking while maintaining the products effective, easy to control with small footprint on your systems. If you were not content with how your support tickets, queries or issue reports were handled, we would appreciate if you could provide a ticket number, links to this forum, etc. in a comment so that we could review them and try to improve things in the future.
With ESET home products v17 and Endpoint v11 just around the corner (program update to v17 is already available on the pre-release update channel), you can look forward to features like Browser Privacy & Security with Secure Search or Browser Cleanup as well as a new tier product ESET Security Ultimate which will bring VPN as an addition to existing features for a start. Last but not least, we are excited to tell you that next year we're going to substantially improve the HIPS-based Deep Behavior Inspection, Ransomware shield, scanning on multicore processsor systems, etc.

Regards,
Marcos

Please switch to the pre-release update channel in the advanced setup and see if the issue goes away after the Banking and payment protection module updates to v1331 (not yet available). It should address some of the reported scrambler issues. In the mean time, you can disable Keyboard protection as a temporary workaround.

Honestly had you fast startup enabled and chose to shut down the system, I would understand why a restart was needed after turning on the machine. However, if you really chose to restart the system from the power menu, I have no clue why a true restart was not performed. Fast startup should affect only shutdown, not restart.