cbowers 0 Posted April 30, 2019 Share Posted April 30, 2019 Hello, We have some development endpoints with ESET Endpoint AV 5.0.2272.7 which scan local Docker Containers fine to various degrees (apart from access denies in parts). However if there is a Windows Server 2016 Container, if the PC is scanned, the scan never ends, until the ESET scan log file grows to the drive capacity, or is stopped. We haven't been successful finding a filter which works. Has anyone resolved this, or noted it a non-issue in later Endpoint versions? If one scans: C:\ProgramData\Docker\windowsfilter\[container ID GUID]\UtilityVM\Files\Users\All Users\Docker\windowsfilter\[container ID GUID]\Files\Users\All Users\Docker\windowsfilter\[container ID GUID]\Files\Users\All Users\Docker\windowsfilter\[container ID GUID]\Files\Users\All Users\Docker\windowsfilter\[container ID GUID]... over and over That string seems endless Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted May 1, 2019 Administrators Share Posted May 1, 2019 Would it be possible to provide us with the container so that we can look into it? Also I strongly recommend upgrading Endpoint v5 to the latest version 7.1 for maximum protection, to make sure that it works alright with current OS's and that possible issues would be fixed. According to https://support.eset.com/kb3592/, it's in the phase of basic support which means: Availability of regular engine module updates Availability of module updates is not guaranteed Product is no longer available for download from ESET download servers Technical support is no longer available, no bugs will be fixed Link to comment Share on other sites More sharing options...
Recommended Posts