itman

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.

I found another Microsoft posting related to this issue: https://answers.microsoft.com/en-us/windows/forum/all/the-windows-security-center-service-was-unable-to/a5d72875-bd78-4a9c-be76-e1785919fd67 . This posting also explains an earlier reply in this thread when the poster couldn't find WSC desktop toolbar icon in Win 11; the WCS service wasn't running. As the poster in the above link stated, he also could not start the service. This is a serious issue since other postings indicate if a WSC app reset doesn't fix the issue, the only other alternative is the Win reset option. Or, uninstall the third party AV solution and pray that fixes the issue.

Does your PC motherboard have a TPM module installed?

I had ver. 17 installed on my Win 10 22H2 installation earlier in the week prior to the official release to test it out. There were no Event 19 errors in my Win Event log related to WSC. As such, I conclude this appears to be Win 11 issue.

Should not be a problem as far as I am aware of. At least one poster has done so: https://forum.eset.com/topic/38725-eset-internet-security-not-working-after-17015/?do=findComment&comment=175524 .

No clue.

You can't "rollback" to ver. 16.2.25. 1. Export existing Eset 17.0.15 settings if customization made from Eset default settings. 2. Download ver. 16.2.15 from here: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products . Scroll down to this web page section, Earlier versions of ESET Windows home products, and select ver. 16.x for the Eset product you have installed. 3. Uninstall Eset ver. 17.0.15. Reboot necessary after uninstall. 4. Install Eset ver. 16 previously downloaded. 5. Import Eset settings if previously exported.

We need @Marcos to verify if the detection is a false positive.

That's what I did. Stayed with 16.2.15.

How did you upgrade to Win 11? TPM is a base requirement for Win 11. Overriding base Win 11 requirements to force its install not a good idea. It could come back to bite you in the butt.

This URL has 0 detection's at VirusTotal.

https://www.elevenforum.com/t/open-windows-security-in-windows-11.1050/

This does clarify the problem might only be related to Win 11. Another posting of note: https://answers.microsoft.com/en-us/windows/forum/all/receiving-event-id-18-19-and-error-with-thumbprint/c34478a9-c7e5-4631-b9a5-37eacb8b0d36?page=1 The only way this poster was able to resolve the issue was to revert back to Win 10.

I will also advise opening Windows Security Center -> Device Security -> Core isolation -> Core isolation details and verify that Memory Integrity is set to On status.

Eset detects on my installed Firefox browser;

https://forum.eset.com/topic/38521-secured-browser-keyboard-protection-firefox-mistyped-characters/?do=findComment&comment=175664

This has already been acknowledged here: https://forum.eset.com/topic/38725-eset-internet-security-not-working-after-17015/?do=findComment&comment=175486

Assume Eset has temporarily suspended ver. 17.0.15 upgrades by all in-product methods until recently posted issues have been resolved. Appears however you can still download here: https://support.eset.com/en/kb2885-download-and-install-eset-offline-or-install-older-versions-of-eset-products?ref=esf . Do so at your own risk. -EDIT- Looks like off-load download link is also down.

Plan on not getting much sleep for awhile.

👍 What about forced in-product upgrade option?