itman

You can running this command from admin level command prompt window: sfc /scannow When that completes if you are running Win 10, then run the following command: DISM /Online /Cleanup-Image /CheckHealth Ref.: https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image Note that both sfc and DISM will take a while to complete.

This would infer you are using NOD32 which does not contain a firewall.

From the bleepingcomputer.com link in regards to Kaspersky like issues I posted previously. Eset along with most VirusTotal AV vendors detect the Trojan. None from what I can tell, detect any of the malicious JavaScript's it uses. Bottom line - unless browser based Chromecast is used, the Chrome Media Router extension should remain in its default disabled state.

Whereas there is a way to export the self-signed cert. from their webmail site here: https://webmail.jpberlin.de/roundcube/ and import it into Eset's list of SSL/TLS known certificates, I don't know if it would work in regards to Eset's client e-mail scanning. Someone from Eset will to comment on this. I am assuming the webmail certificate is the same one their client e-mail servers are using.

What we really haven't talked about is the origin of the problem which is: Here's a detailed analysis of a recent malware that exploited Chrome Media Router: https://securelist.com/razy-in-search-of-cryptocurrency/89485/

I just came across an interesting Google posting related to Chromecast titled; Cannot cast content from a wired PC connected to same router as wifi to which chromecast 3 connected Of note is the last recommendation: https://support.google.com/chromecast/thread/4191235?hl=en As such, I don't expect a speedy resolution to this issue other than the Eset SSL/TLS protocol scanning HTTPS port 8009 exclusion.

Don't believe this is an Eset firewall issue. When I was on the Sage web site, I received multiple alerts from uBlock Origin filter on FireFox about adware/tracking activities on the web site. Post a screen shot on any alerts from Eset it is generating while on the Sage web site.

If the entire quoted reference is read, the only thing that fixed this for the OP was a reformat of the OS partition and a clean install of Win 10.

Although not directly related to this Eset Chromecast issue, it is imperative that one validate that ports 8008, 8009, and 8443 are not open on the WAN side of the router. Before you ignore this, read this Sophos article: https://nakedsecurity.sophos.com/2019/01/04/dont-fall-victim-to-the-chromecast-hackers-heres-what-to-do/

Do you have any games installed from RTS Arena?

You're not following what I posted. There is something wrong with the initialization processing of Win 10 Windows Security Center. Your choices? Do as I suggested or live with the popup notification.

Contact Dell support. They might have a special firmware flash utility or procedure to deactivate. I would imagine this would require you proving to them that you are the real owner of the device. Also if the chip is not soldered to the motherboard, they could sent you a new chip. Chip replacement is dicey.

This is a long known Win 10 issue caused by Windows Security Center not properly initializing and the issue has nothing to do with Eset being installed. It has manifested when Windows Defender was the only AV installed. This old fix shown below appears to be no longer available since Microsoft has locked down these service settings in later Win 10 versions. The same could possibility be done by modifying the associated service start value setting in the Registry. But, that also might be locked down. https://www.tenforums.com/antivirus-firewalls-system-security/10870-notification-turn-virus-protection-evey-time-windows-starts-2.html?s=c70845790774c82707e65190c1c80343 What you might try doing is uninstalling Eset and see if the alert disappears with only Windows Defender running. If so, then reinstall Eset and hopefully the issue is resolved.

Did a bit more checking. It appears once Computrace is activated in the BIOS/UEFI, there is no way to permanently disable it. This actually is by design to prevent whomever stole your laptop, etc. from doing the same. It also appears that setting is controlled by the chip firmware itself. And reflashing the BIOS/UEFI won't deactivate it.

Also there is some confusion about terminology. Computrace was originally named Lojack. There is a Trojanized malware version of Lojack which Eset name "Lojax" that is creating the confusion: https://www.welivesecurity.com/wp-content/uploads/2018/09/ESET-LoJax.pdf Of note is Eset's detection for the malware version is LoJack agent LoJax.

Check this out: https://support.google.com/chromecast/answer/3249268?hl=en . Run the automated troubleshooter first.

I am far from an expert when it comes to IoT connectivity. But based on this article: https://blog.bestbuy.ca/tv-audio/tv-home-theatre-tv-audio/how-to-connect-chromecast-chromecast-audio-to-your-av-receiver , connecting the Chromecast dongle to an AV receiver only allows for output from that dongle to anything directly connected to the AV receiver. That usually is a TV, X-Box, etc.. It appears latter version Onkyo receivers haves Chromecast built-in but that is only for audio streaming. In other words in this configuration, I see no way how your PC not physically connected to the AV receiver could communicate with a Chromecast dongle attached to the AV receiver.

Onkyo equipment is notoriously temperamental. This also might be routing issue. PC that can't connect to Chromecast device can't "see" the dongle since it is connected to the AV receiver.

Since it appears you are using Chromecast on multiple network devices, on which device is the dongle attached to?

Did Chromecast work properly on this device prior to ver. 12.2.23?

On the device where Chromcast connectivity cannot be established, Set HTTPS port to only 443 and see if connectivity is now established.

If this ARP poisoning attack just started on your device with Eset installed and Eset has been installed for some time, it appears your Macbook has been compromised. So that is the device that needs to be examined in detail.

Care to elaborate on how this can be done? Posters in the thread have tried to do just this using Eset's interactive SSL/TLS protocol scanning certificate exclusion methods. They have failed. The problem is that Eset is blocking the connection to the Chromecast dongle device. As such, the certificate on that device cannot be accessed. The only way this can be done would be to export the Chromecast certificate from the dongle device and import it into Eset using SSL/TLS protocol scanning certificate exclusion. The question is how can the certificate export from the Chromecast dongle be performed. -EDIT- It is also doubtful this would work. Unlike in Kaspersky where this issue presented as a certificate issue, Eset is blocking the connection prior to this event.

I don't know if the following still applies. If is does, it doesn't bode well for Eset's SSL/TLS protocol scanning: https://stackoverflow.com/questions/27146081/does-chromecast-come-with-a-certificate-bundle-allowing-simple-webserver-authent

No. It's using a local proxy connection it appears to me. It listens for connections on local device port 8010. It then proxies the inbound traffic to the Chromecast dongle via port 8009. For outbound connections, the reverse occurs. The proxy activity bypasses Esets protocol filtering. Hence, why there is no issue with the VLC app.