Pete12

" My PC updated to 17.1.11.0 two days ago and have not logged this error since it updated. "...........yes ! same on my tree PCs ! Finally fixed ...........!!

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 ..............??

" it requires cooperation with Microsoft to figure out the root cause. "...........latest februari-Microsoft updates just arrived/installed . WHY (??) does it takes so long , before MS starts to cooperate for fixing this ( endless time taking !!) problem ?? You know this event-viewer problem will costs ESET lots of customers ( including myself !) if its not been fixed ! Not very nice seeing an eventviewer , every day, full with errors ...........!!! WAKE UP, PLEASE !!!

Ok , thank you . So, still not any solution available ........... Will wait , untill my version ( V16 ) is not supported anymore . If no solution , have to search for other security software , without errors in my eventlogs !

Cant find the v16 on your link ................!! When selecting older version , nothing happens ! btw ; Im now on 16.2.15 version still , no problems with this version , untill I update to later version(s) ......... So, what version is the v16 ?

" you can temporarily use the older version signed with the SHA2 certificate while the issue is being investigated. "...............how ( ?) to get this version , will try , untill finally fixed for latest also . Im getting 17.0.16.0 , when looking for latest ..........

" Still waiting for a response from Microsoft. We'll ping them again. "..........still no fix for this annoying problem ?? ( 17 Januari .....!) Why ( ??) do we have to wait soo long for a response from Microsoft ? Eventviewer still full with errors , since latest ESET-update..........!! Not in the mood for updating my 16.2.15...............😟

Still no improvements , eventlogs full of errors ! Will stay at 16.2.15 untill its running out of support , then will look for other security-software , if ............still no solution ! 🤨

btw ; wy not "roll-back " to a good , solid working version........??!

We are having many problems ( not just me ) with this latest update , made by ESET , so we may expect ESET will solve /undo this "disaster"-update also ! Please, understand ESET will lose lots of customers ( including me too ) if the solution will take too much time .........

I ( and we ! ) just cant understand WHY (!!!) its taking so much time ,before all these problems with latest update (??!) will be fixed .............. Im a ESET-customer for a very long time , never had all these update-problems before ! WHATS THE MATTER ?? ESET is losing very much customers with these "updates " ! Im also thinking of stepping out and looking for more reliable anti-virus/firewall software , without all these headaches .......... PLEASE , SOLVE IT ..........🙏