I’ve noticed that due to a bug in the beta version, the sensitivity of the Standard Shield provider in avast was most likely reset from Normal to High during the upgrade process. This is not intended and can lead to unwanted situations such as the 100% ashServ.exe CPU bound discussed in the forum.
To reset the sensitivity back to normal (recommended), please double-click the avast tray icon, click “Details >>” (if not done so already in the past), scroll the provider list down to “Standard Shield” and move the sensitivity slider to Normal.
The Normal level is recommended for most users as it should provide optimal balance between protection and performance.
Same here, no problems with the standard shield. It was set to normal and stayed that way.
Still no answer/solution for the problem I found with the IM and Mirc though.
I dont have the beta but even if i put it in Normal level i still get well protection? And can anyone tell me what the difference between Normal and high, when in high it scans the files extra good or what?
A little search in the board will help…
Normal level does not scan inside archive files (zip, arj, etc.). When extracted, the files will be scanned. Normal is the best balance between security and performance.
