Dandandan
-
Posts
5 -
Joined
-
Last visited
Posts posted by Dandandan
-
-
UPDATE: after a total combined time of 400 hours the "first scan" and the first scheduled scan have finally finished. Did not expect it to take that long.
-
@Marcos I tried running it but it says Scanner initialization failed
-
@Marcos It hasn't even finished the first scan when installation is complete and it is at 120 hours
-
So I recently installed file security on my Windows Server 2008 R2 and the first scan has now been going for 120 hours and seems to have no end in sight. A smart scan was also started by schedule and it too has now been going on for around 30 hours.
The real time protection is still working but the scans are showing threats on my system but because the scans aren't finished the program isn't doing anything.
How long should a scan usually take?
ESET File Security Scan taking 100+ Hours
in ESET Products for Windows Servers
Posted
@MarcosHow do I set the scans so archives are left out? After an extensive review of the scan log it certainly appeared that archives seemed to be the big issue. I am working on a very large server that is running a large law firm so I expected some time to complete the scan.
Also in the scans it said it detected several threats and yet nothing was done about them. What should I do for that?