Hi!
I scan a infected file on a UNC path, e.g. \\SERVER\SomeShare\SomeExe.exe with a2cmd.exe (in service mode).
a2cmd says scanned : 0, found : 0 and returns 0 = No infections were found
When scanning the same file on a local disk it detects the infection and cleans it.
Why is this?
Anguel

First, thank you very much for the thorough answer. I did not realize that EEK and EEK PRO are actually the same file. So it looks like I will go with command line scanner PRO because I want to scan mail attachments as soon as a user opens them and the scans have to be fast. So I will use the service mode.
Many thanks, that looks good.
I tested it, if you run an update (e.g. via task) and a scan starts at the same time, the scan will not execute. This means that I have to run update first and scan hereafter in a batch file, instead of the task. This is slower, but at least I make sure that I have the latest updates.
Thank you once again, I will do some more testing but will probably go with the command line scanner.
Anguel

Hi!
In our small business (about 10 PCs) we are using Kaspersky Endpoint Security as primary scanner. Now we are considering to add a second opinion scanner for e-mail attachments.
Emsisoft Command Line Scanner looks interesting and as far as I understand, if we also want to have a GUI option we would need the Emergency Kit PRO. What I don't understand is how licensing is done there:
1. Will I be able to use Kit PRO on 10 PCs and how much will this cost? There is this strange 250 cleanups license...
2. Does Kit PRO include the PRO command line scanner, as far as I understand only PRO can be loaded as service.
3. Can Kit PRO perform automatic signature updates in the background? If so, also for the command line scanner?
4. The command line scanner seems to require a manual update via /u switch. What is the approx. frequency of signature updates? What will happen if I run the command line updates via task and a command line scan is started while the task is updating signatures?
Thanks in advance!
Anguel