-
Posts
113 -
Joined
-
Last visited
Everything posted by Pete12
-
Ok , updated from 16 version to this latest 17.0.16 , rebooted ! Conclusion ; still no solution !!! id=18 and id=19 keeps showing up in our eventlogs !! Went back to 16.2.15 ( again) no eventlog-errors with this version. We are very dissapointed , still(!!) no solution for this forum-item !! So we have to cancell ( again !) to update from the 16.2.15 ............ Wonder WHEN (!!) this problem ( eventlog-errors ; id=18 and 19 ) will be resolved..........!! ๐คจ
-
1. updated ( again) from 16-version to latest 17.0.15 ; again my eventlogs full with errors ; id=18 and id=19 , so, this problem is still not fixed ( grrrrr !) Went back to 16-version . 2. " So to make this simple, we can remain on V16 without issues and eventually a v17 fix will pop up ? "............still no answer to this important question ! Several people , included me , are still waiting for a fixed new updated 17.0.15 ...........
-
" would have to load ver. 17.0.13 into Early Access section of the forum for you to download it. "........yes, please, give me a link to this version , or tell me HOW(?) /WHERE (?) to get this version . 17 .0.15 gives me ( and others too) lots of event-errors , look in this forum , you know ! Im on 16.2.15 , updating to 17.0.13 , will be fine ( untill 17.0.15 is fixed )
-
Itman ; " 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. "................WHERE/HOW ( ??) to get version 17.0.3 ? Nowhere to be found ! Want to update to 17.0.3 , coz 17.0.15 gives eventlog-errors.............
-
" What new release do you mean? We don't plan to release any newer version, we'll resume automatic upgrade to v17.0.15. ".................I dont understand , how(?) can we upgrade from 16 to 17 , with these eventlog-errors ( Im not the only one with id=18 and id=19 , see all the previous posts !) . Then we have to wait for a fix ........... If not , have to stay at 16-version !
-
" 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; "..............dont you think its time to change this behaviour ? Impossible to update , without eventlog-errors , if ESET wont properly signed its eamsi.dll........
-
" 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."...........it is indeed on my Win11, then why(??) these eventlog-errors ( id=18 and id=19 ) still ??? ESET version16 does not make any eventlog-error at all , so it seems this 17-version is corrupt ......... btw ; when trying to update the program ( from 16 to 17 ) , this version ( 17 ) is not offered anymore....