Jump to content

Yuriy85

Members
  • Posts

    2
  • Joined

  • Last visited

About Yuriy85

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Ukraine
  1. What are protoscan and local.db file for? Can you explain?
  2. 1). This bug appeared in the version 9.1.2051.0. Until this moment, I had already discovered it five or six years ago in yours products. Then you quickly fixed it. Now it has appeared again. Steps to reproduce: 1: Reboot yours router. 2: After reboot ekrn.exe try to connect UDP 192.168.1.1 without using any ports. Version 9.0.2046.0 and lower not have this bug. 2). This bug appeared in september 2021 and still exists. All Eset Endpoints versions are affected. Steps to reproduce: 1: Remove any planned modules updates from schedule tasks. 2: Start manual update. 3: Wait when modules downloads and will be updated. Immediately after that EES again start search updates and this time show red warning "The program is not updated. No connection with the server". When using proxy red warning changes to "The program is not updated. Not authorized access." Second "failed" modules updates happens only when disable scheduled tasks updates and using only manual updates. It never happens when for updates use only scheduled tasks. I don't know why this happens. Why EES after successful manual update immediately start a new updates attempt and it fails showing red warning. 3). Most funny bug. It harmless, but I thought that you should know about this. Steps to reproduce: 1: Open C:\ProgramData\ESET\ESET Security 2: Create new folder through right-click context menu. 3: After this will appear total FOUR folder "New folder 1,2,3...". As I said it harmless. But creates some difficulties with removing these folders for unprepared users.
×
×
  • Create New...