Cybercapture interfering with batch / command line calls

AVG Performance
3

Thank you for providing us the information, Kevin. 

We appreciate your technical knowledge in finding the workaround.

To help you pointing in right direction, we'd suggest you to try submitting a false positive request by visiting this link (https://www.avg.com/en-us/false-positive-file-form). If the file is found to be clean, it will be whitelisted by the concerned team. 

Thank you for your understanding in advance!

5

Hi Kevin,

I'm sorry for the delayed response.
Does the specific application you execute have Digital Signature? We can try whitelisting the application if it has Digital Signature. If not, we will have to disable the Cybercapture each time we execute the application.

1

Cybercapture incorrectly ends a program after "testing" it for viruses with a successful status causing a calling program to "think" the program has successfully completed a batch (i.e. command line) invocation. 
Example:
MyProg1 calls MyProg2 (and waits for an errorcode at completion)
Cybercapture starts MyProg2 and when done "testing" ends the program with a successful completion
MyProg1 receives the successful completion code even though the process was NOT completed.
Cybercapture then restarts MyProg2 leaving a SNAFU

Disabling the Cybercapture feature (i.e.creating an exception) is not an option for me.
For Cybercapture to work properly, it needs to find a way to finish its test and continue running the program without returning to the calling program.

In the meantime, if anyone has found an easy alternative to solve this problem, please advise.

 Thanks

4

Hi Kevin,

I'm sorry for the delayed response.
Does the specific application you execute have Digital Signature? We can try whitelisting the application if it has Digital Signature. If not, we will have to disable the Cybercapture each time we execute the application.

2

Yes, I digitally sign it but I frequently update the program (both the calling program and the called program) causing AVG to re-screen it every time I update it.  As such, whitelisting is a moving target.

I have already found a work around (since I posted) but I would still encourage Avast to try to solve the problem.  Any program being invoked through a command line call shouldn't return to the calling program unless it has really "completed".  As an example, the cybercapture appears to let the program begin running while it tests for viruses, it then  stops it and restarts it; why not let it keep running if the test shows no viruses?   

Thanks,
Kevin