WRData bloated logs.

Hello and Welcome to the Webroot Community!
 
If you use not well known Programs and they update frequently as I do and many others it's best to Submit a Support Ticket and get them Whitelisted as I don't mind pestering Support about unknown files. When they reply and ask you to do a Scan then you can go here C:ProgramDataWRData Folder and delete the old monitored database files. Only these ones: db.numbers.db and no others.
 
Thanks,
 
Daniel 😉

That's the problem I shouldn't be required to contact support/wait 24 hours every time I compile a new exe or update a piece of software that was previously whitelisted.
 
If i flag something safe that should be it!

Hi knocks
 
Welcome to the Community Forum.
 
If I may just add here, by way of information, that we are waiting for the implementation of a feature request that would allow the user to flag specific folders for exclusion from scanning by WSA. This I believe implemented in the Business version of the product but as yet we have no news as to when the same will be done for the consumer version...but hopefully it will be soon, and then you would be able to exclude your development libraries from scanning and therefore from your new versions of programs from being 'picked up' as new/unknown and therefore monitored.
 
I appreciate that this does not help at present but as I said hopefully there will be a solution to your issue.
 
Regards, Baldrick

Baldrick,
 
This is a big flaw! One should not be poweless to stop such poor/unnecessary behaviour from an antivirus.
 
I will need to look at my options.
 
I have grown tired of support's copy and paste responses that are totaly irelevent to the question asked so thank you for the reply.

?,
 
I had a look at your ticket and created whitelist rules for the applications that appear to have been causing the issues. With the rules in place the new files should now be whitelisted when the apps are updated/rebuilt.
 
-Dan

Hi Dan
 
Many thanks for stepping in on this one. Much appreciated as always. :D
 
Hi knocks
 
Whilst I understand your frustration I would humbly disagree that this is a 'flaw' as it affects a very small minority of users...but having said that the affected users are understandably peeved by it.
 
If I may suggest that you head over to the Feature Exchange and kudo/comment this feature request:
 
https://community.webroot.com/t5/Ideas-Exchange/WSA-all-versions-Exclusion-of-specific-files-folders-from-scans/idi-p/3300
 
The Development Team review the requests regularly and therefore your views will be picked up more easily and directly via that mechanism...and hopefully if enough support the idea/provide suitable feedback we will see the feature implemented sooner rather than later. ;)
 
Regards, Baldrick

Yes the log writing has settled down since contacting support. But I still needed to contact support after the first application that needed updating started writing GB's of data again after having previously been whitelisted.
 
Anything that renders my system unstable from behavior I am powerless to stop is a flaw in my opinion regardless if it only effects a minority of users. An antivirus should assist its users but the final say in an applications behavior should be that of the system owner not the antivirus.
 
As this issue has been addressed in the business version its disheartening to see the issue is only under consideration for the consumer version. Especially given the original request goes back to 2012!

Hi knocks
 
Whilst I have sympathy with what you say I would repeat that the best approach would be for you, if you have not already done so, to flip over to the Fearture Request in question and record your very cogent acrguments and experiences there, and then kudo the request as that way the feedback will get to the Development Team more quickly/more directly.
 
Regards, Baldrick