itman

There's a bug in the ver.17.0.15 in-product upgrade installer. It is installing Browser Privacy & Security with "Display Browser Privacy & Security notifications" disabled.

After Win 10 22H2 Nov. cumulative update, my build no. is 19045.3693 and this is the one Eset ver.17.0.15 is causing WSC event log errors. Also within this Win Update was a .Net update but don't believe that is the source of the problem

As far as a strong possible suspect in regards to the Win Nov. cumulative update, Microsoft patched a zero day vulnerability in SmartScreen. Since SmartScreen directly interfaces with WSC, "my money is on" this being the the source of conflict with Eset and WCS processing at system start up time.

What Win updates did you perform? I installed the Win Nov. updates after I had reverted back to ver. 16.2.15. So you might have at least nailed down the source of the WCS errors.

Now that ver. 17 is available via in-product update option, I decided to do so and I am now also receiving the Win 10 WSC errors at system startup time. The following is important and might aid in the resolution of this issue. Early in this thread I posted I was not encountering this WSC issue when I had previously tested ver. 17. Here's the details of that previous testing. I had downloaded the early release of ver. 17.0.13 via forum provided link. I installed ver. 17.0.3 on top of my existing ver. 16.2.15 installation. No WSC Win event log errors immediately after ver. 17 installation or thereafter. This leads to the following conclusions; 1. Something changed between ver. 17.0.13 and 17.0.15 release. 2. There is a problem with the in-product upgrade processing in regards to ver. 17.0.15.

Did you check tor.exe at VirusTotal?

Based on the fact that Security Center is accessible via its desktop toolbar icon and Eset is being properly registered as the Win AV real-time solution: https://forum.eset.com/topic/38760-windows-security-center-service-unable-to-load-instances-of-antivirusproduct-from-datastore/?do=findComment&comment=176096 , I would say that these Win Security Center error Event log entries can be ignored.

One thing that needs to checked by those seeing these Eset ver. 17 Security Center error Win event log entries is to verify if Microsoft Defender is running concurrent with Eset. Using Process Explorer or Win Task Manger, check if mpengine.exe is running.

I guess you ignored @Marcos prior posted comment. Refer to the Date last analyzed in the VT results. It's 4 months old. Now mouse click on "Reanalyze" on the VT results web page. You will observe that Eset no longer detects your web site.

The graphic display to be appears to be a HDD with the case removed showing all the drive platters on top.

Are you attempting to install an Eset ver. 17 Home/Consumer product?

Actually, Bitlocker can be enabled on Win 11 Home versions: https://support.microsoft.com/en-us/windows/turn-on-device-encryption-0c453637-bc88-5f74-5105-741561aae838#ID0EBD=Windows_11 . Such is not the case for Win 10 Home versions.

He noted that it was fixed in ver. 17;

I will also add there are multiple known vulnerabilities for Synology DSM; https://www.cvedetails.com/vulnerability-list/vendor_id-11138/Synology.html Ensure all the latest software patches available by the manufacturer have been applied.

I am not an Eset employee. You need to direct these questions to your authorized Eset distributor in India.

Here's the Microsoft article on the malware: https://www.microsoft.com/en-us/security/blog/2023/11/20/social-engineering-attacks-lure-indian-users-to-install-android-banking-trojans/ . It appears Microsoft has not publicly shared the malware sample. As such, it can't be determine what other AV vendors detect it.

Blackberry has an article on Warzone RAT here: https://blogs.blackberry.com/en/2021/12/threat-thursday-warzone-rat-breeds-a-litter-of-scriptkiddies . The article is a bit dated and most AVs detect the the variants listed in the article. This might be a new variant that is currently "flying under the AV radar." Also, Warzone per se is a legit game: https://www.callofduty.com/playnow/warzone .

Here's a second opinion via PCRisk that deploys Quttera's web site malware scanner. Unlike Sucuri, Quttera will scan your entire web site. With the amount of malware noted, I would say you need professional help cleaning your web site; https://scanner.pcrisk.com/detailed_report/www.ayr.es#details

Engage Sucuri, Quttera, or another web site cleanup provider to clean your web site of malware.

Wrong. The web site is infected; I had to add the "/* to the domain to prevent Eset from triggering a malware detection on www.ayr.es prior to access to Sucuri web site,

I assume you are referring to this; Please clarify your question. This current Security Center Event log error entry only exists for Eset ver. 17.

The Sucuri link @Marcos posted above: https://sitecheck.sucuri.net/results/https/ayr.es/blog/category/especial-alquileres/ now scans clean at Sucuri. However, this is for a sub-domain on your web site. Sucuri still finds malware on your home web page domain: https://sitecheck.sucuri.net/results/https/ayr.es .

Did you purchase your Eset license also from Micro Center?

The main point is that Eset ver. 17 is properly installed in Win 11 which it appear it is. As far as the Event log error, I suspect it is related to the Microsoft Azure code signing cert. Eset is using to sign all its software now. It appears "not to play nicely" with Win 11 Security Center validations. On that regard, nothing new since Eset never has properly signed its eamsi.dll;

For those having issues with Win 11 Security Center with ver. 17 installed, it is critical you post back your finding to what @Marcos requested here: https://forum.eset.com/topic/38760-windows-security-center-service-unable-to-load-instances-of-antivirusproduct-from-datastore/?do=findComment&comment=175846 . When the Security Center displays Eset data as shown in the above linked screen shot, it indicates Eset has been successfully registered in Security Center as the active real-time AV solution.