I recently added 2 HDDs to my system. Exclusions will not accept them. The paths were entered correctly; F:* & R:*.
I’ve tried these two suggestions without effect:
Left click the “a” icon, select standard shield, customize button, advanced tab. (the paths DO remain here)
(After entering the paths in Exclusions and hitting OK) right click on tray icon and select Stop On-Access Protection and Exit, now restart your computer
In both cases I’ve entered the paths as shown above and hit the OK buttons where applicable. They still do not show in Settings>Exclusions. What am I missing?
Sorry but avast is confusing you. The exclusions entered in the Standard Shield panel are not shown in the Program Settings > Exclusions panel because …
There are two different exclusion functions in avast.
There is one set of exclusions for the Standard Shield (on access protection) which is managed via the Standard Shield Panel.
There is a separate set of exclusions for the “On Demand” scanners that is shown in and managed by the Settings > Exclusion panel.
You need to decide when you want these disks excluded, if from both On Access and On Demand then you must enter them in both lists.
Thanks Tech, that worked. And Igor, you were right too.
Alanrf, I understand the dif. Trying to present all actions taken, just in case.
Anyone have an idea why?
I’d like to not have to remember what I did in case something similar happens in the future (old brain, faulty memory).
(edit) I should add that although I’m new to the forum, I’ve used Avast Home for nearly a year and already had 2 entries in the Exclusions list that were unaffected. What ever happened, it was fairly recent.
We should probably ask which version of avast are you using.
I am testing with the current beta version but having no problem adding F:* and R:* to the exclusion list and it staying there (in Program Settings > Exclusions) even though I do not have an R: drive.
By the the way is it the same with both manual add and the “Browse” option?
Thanks for getting involved LorenzoC but, if you go back a few replies, you will see that that’s how I was able to make the changes as per Tech’s advice.
Now I’m just trying to find out why the normal way still doesn’t work.
I have XP-Home, SP2 with all current updates on a PC with 2 hard drives (4 NTFS partitions - C:,D:,E:,F) and I’m using Avast! 4.8.1192 with VPS 080510-0. For the purpose of the test I manually entered exclusions for D:*, E:* and F:* in the Standard shield\advanced - locations not scanned, and also in the Program Settings\Exclusions using both manual add and browse methods. In all cases the settings remained after a reboot. When I subseqently did a right click, Start Avast! Antivirus and then selected local hard disks, all partitions were still shown in the selected paths, however only the C: partition was scanned. I did not disable the self defense module to do these tests.
The selection of the local disks will select all local disks, but on the scan the Exclusions will come into effect as you have found.
You shouldn’t need to disable self-defence to do the tests you mention as you weren’t directly editing the avast4.ini file, the avast interface (Program Settings, Exclusions) was so the self-defence shouldn’t object.
olddog has essentially confirmed the testing with the same avast version and conditions that I reported earlier in the thread. It is good to get confirmation that we are getting the same results.
However, for the problem reported by d4l3d we either need someone with version 4.8.1169 to repeat the tests or for d4l3d to be convinced to try the latest beta version of avast and repeat the attempts to update the exclusion list.