gentlemen, i owe you an apology…it seems as tho i had not run both kis & avira removal tools b4…i reran both kis & avira
removal tools & tested more scans…THE BEEP is no longer sounding!!!
i am puzzled tho as to why it only beeped via command line & not the gui…
also even tho there were program traces left after removal via
the win 7 control panel, what would cause avast to beep &
why??? it did not indicate that there were any viruses
or any other problems… the scan log was clean, no errors,
etc., just the beeps!!
another unrelated question…does avast scan the registry
during a ‘c’ drive or full system scan or any other time??
also does avast scan for rootkits during any scans other than
when specified as one of the parms setup for a ‘custom scan’??
Can you try running the EXACT same scan from GUI and check any messages and log results? Even when you no longer get the beeps, you could still compare the log results between command line scan and GUI scan.
also even tho there were program traces left after removal via
the win 7 control panel, what would cause avast to beep &
why???
Once again, you really need to check the log results of those specific scans (and maybe report them here).
The logged result may not include every detail of the scan (so maybe the answer for those questions is not there anyway), but if there is an answer for those specific scans in “some” place, it is there.
avast will not scan the registry only files which can be infected. To scan the registry use CCleaner.
Rootkits; avast by default does a quick scan. You do have the option to create a "custom scan. On a custom scan avast allows the user to set certain parameters. I would suggest leaving the packer setting at the default setting. If you do a full scan for rootkits you may get some false positives. For the most part the default full system scan will be sufficient. I do a full system scan once a week and a quick scan twice a week. To do more than one full scan a week is overkill due to the fact that avast has some very strong resident shields. That is unless you play with fire, then you might get burned.
Now its time for you to go to PROFILE then Modify Profile then Forum Profile Information then select your country in Please select your country: then update your Signature: with information like my signature as this helps the helpers offer pertinent advice.
In Account Related Settings select Hide email address from public? to prevent scammers and spammers harvesting your yahoo.com email address.
Note: Your email address will still be available for Moderators.
this beeping sound is still there…only when running a FULL
rootkit scan…tried unloading avast, ran 3 progs. to clear
out any previous avs, ran aswclear to clean out avast,
did clean install of avast 6.0.1289…
setup custom scan in avast to scan only rootkits(full scan)
setup batch file using ashcmd pointing to /@custom scan
ran scan with rootkits(full scan) & beep SOUNDS again…
changed custom scan to scan only rootkits(quick scan)
ran scan again & no beep…
this only occurs when running avast, & only when using a batch file with ashcmd.exe…does not occur when running the same scan in gui…
would someone be kind enough to setup scan as i did
and see if you have same problem…
this is driving me nuts…
have to know where problem is…
No apparent malware in the logs… Have you tried disabling the windows sounds in control panel ? Does that stop it, if so then re-enable one at a time until you find the culprit
I’m starting to think that some Avast’s developer should comment here, whether there is some command line argument or some situation where this “beep” behaviour should be expected or if it can be otherwise changed; specially keeping in mind that this is happening with Avast running from command line only (not when ran from GUI).
