@emilemma,

From your report, it “seems” like Avast command line scanner is using beeps to “tell you something”, just as the GUI would use some sounds in some cases.

Maybe there is some command line argument / parameter to run Avast command line scanner with no beeps, but please pay attention to what exactly Avast is trying to “tell you” with those beeps.

If the beep is only saying “I’ve finish the scan and all is OK”, then it would be “acceptable” to set the scan to be “soundless” (“beepless”). Note however that I am NOT recommending cancelling the beep in such case either.

If, OTOH, the beeps are saying “hey, please pay attention to the results, since something seems fishy”, then I wouldn’t take that situation as “acceptable”.

I guess the only way to find out is to start a short / middle command line scan (instead of having to wait for the complete “C:” drive), and after the beeps:

1._ Compare the new beeps with the previous ones you had; and,
2._ Check the log results of the scan, so to (maybe) relate the beeps to the specific results.

I hope I was clear enough (don’t hesitate to ask again).