Pete12

Marcos , thank you very much , removing the wrong keys is the solution in my Win11 !! 😃 Did not seen any eventlog-errors anymore ( after some reboots also OK ! ) My ESET 17.0.16 works fine , no errors anymore !!! Very good , while you should update your protection always !! Again , thanks a lot , buy you a beer in Holland ...........🙋‍♂️

Should I take ownership before or after the update , and should I remove the keys for/after update ( and reboot ) ??

Ok , 26E0861C ( AV) and 1EDB0739 (Fw) will be present after the update to17 , and the other keys will be removed ( or can I remove myself ?) , after the update .......?? And this will be the fix for id=16 , 18, 19 ?

So, HOW(?) many keys should we have after update to 17 ( 2 in AV , 1 in Fw ?) Which one to remove , after installing 17 ? Is there another way of not showing id=16 in eventviewer ( "Sec.center could not load database, etc " ) ?

Well ,tried several times by following your instructions , though the eventview-errors still coming back , after each reboot . Had to roll-back ,several times, to ESET16-version ( with no errors at all !) My machine is not getting better , thinking of waiting for a real working solution , untill the support of the 16-version will end ........... Anyway , thanks for your help , and if you have other ( better ) solution(s), then ,please, let us know ........

These keys are in the AV and Fw , while only ESET and Windows Firewall is present on my Win11 ( latest version ). Which one to remove/keep ?? Copied them all , so restoring no problem. After updating from 16 to latest 17 , and following your tips , got id=16 and 18 and 19 in the eventlogs still...........

Why (??) so many keys in AV and Fw , only ESET is anti-virus/firewall ...... Which one should I keep........??

followed your solution , still no luck ! Strange in the AV-key , three keys noticed , two from ESET ( did not noticed difference between them ) and the other from Windows Defender. In the Fw-key , two keys noticed , both from ESET ( again , no difference between them ) So, looks like a few keys too much , what to do .........? Removed a Fw-key ( after copy ) ...

After these modifyings , still got errors ; id=16 ( SECURITY_PRODUCT_STATE_ON.) and id=18 ( not possible to load from Firewall-product from datastore )

Still these annoying event-errors , ITS STILL NOT FIXED !! Will stop using ESET if its not fixed this year............!!! Version 17 gives lots of event-log errors , PLEASE , FIX IT ........!!! ( id=18 and id=19 , dont want to see these errors anymore , HOW TO STOP THEM ARRIVE , AFTER EACH REBOOT !!)

Will roll back to 16-version , without all these annoying event-errors !! Costed me a lot of time !! Thanks ( ??) for your ( untested ! ) "advice "

" Not that I am aware of. "..............??? HOW (??) can you advice the ESET-customers to update from version 16 to 17 , while you did not tested it BEFORE (!!) Please , read the REASON (!) of this forum again ! So, still NO SOLUTION ...............!! Test first , before advicing people to update !!!! 🤨

So, this problem ( event viewer running full errors ) is finally fixed ..............??