Jump to content

Pete12

Members
  • Posts

    114
  • Joined

  • Last visited

Posts posted by Pete12

  1. 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..........!!  🤨

  2. On 12/4/2023 at 6:23 PM, Pete12 said:

    despite the errors being logged "............I like a clean eventlog , always trying to keep it clean , so I do hope these errors will be fixed soon ! 

    btw; made a support-ticket and have to wait for working solution .

    So far , nothing , only uninstall completely , tried this already , no luck !

    I still dont understand why (?) its not been fixed ..........

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

  4. "   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 )

  5. 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 !

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

×
×
  • Create New...