Solved
wrdata folder
Anyone know if the wrdata folder can be cleaned out or deleted? It grows to an enormous size over time.
Show first post
+56Sorry but I have no interest with his cleanup tool and you know me I'm a realist and Brad could be breaking Webroot's EULA in some way and would not recommend anyone to use his tool if it ever comes to be and@ wrote:
Hi Brad
I am looking forward to it.
Regards, Baldrick
Just my opinion,
Daniel
+3You make some valid and relevant points there Daniel, and it's difficult to envisage how Webroot could do other than advise against its usage.@ wrote:
Sorry but I have no interest with his cleanup tool and you know me I'm a realist and Brad could be breaking Webroot's EULA in some way and would not recommend anyone to use his tool if it ever comes to be and@ wrote:
Hi Brad
I am looking forward to it.
Regards, Baldrick
@ should check with the internal staff on this@ @ . Also we know it's on the Webroot's Developers list to make WSA clean it's own old files.
Just my opinion,
Daniel
FYI, I already private messaged Nic on this subject to let him know that I will be sending him the link for approval before posing the link on this public forum.
1 person likes this
P.S. This utility is really targeted for programmers who have massive amounts of data accumulating in the WRData folder due to repetitive creation of EXE files (every time we compile a new version of our software). General-purpose users will not really need this, but on my system, the dbNNNN.db files were taking up nearly 20% of my 1TB drive.
I intend to continue using WSA, so this will be an ongoing issue for me. That's why I'm doing this.
I intend to continue using WSA, so this will be an ongoing issue for me. That's why I'm doing this.
Hi Brad
A good point well worth pointing out for those who might be confused or unsure. And use of this utility is very much on the basis that the user is warned that it could cause issues with the installation of WSA on their system, requiring a reinstall at the very least.
Regards, Baldrick
A good point well worth pointing out for those who might be confused or unsure. And use of this utility is very much on the basis that the user is warned that it could cause issues with the installation of WSA on their system, requiring a reinstall at the very least.
Regards, Baldrick
+56Brad has reached out to me, and I will take his utility and run it by the folks here. We actually have lots of folks on our support team who do similar workaround utilities to fix issues, and they sometimes get incorporated in the product. So who knows - maybe we'll end up doing the same with your utility Brad!
Obviously I land with TH on this.. but all is good as long as given an "OK" after being reviewed. As for becoming a part of the product... that would be... pretty doggone cool if it works well and is polished enough to not remove rollback data that is still needed!
:)
:)
1 person likes this
+56@ wrote:
FYI, I already private messaged Nic on this subject to let him know that I will be sending him the link for approval before posing the link on this public forum.
@ wrote:
P.S. This utility is really targeted for programmers who have massive amounts of data accumulating in the WRData folder due to repetitive creation of EXE files (every time we compile a new version of our software). General-purpose users will not really need this, but on my system, the dbNNNN.db files were taking up nearly 20% of my 1TB drive.
I intend to continue using WSA, so this will be an ongoing issue for me. That's why I'm doing this.
I still don't agree sorry! The Webroot Developers are more and capable of doing what needs to be done and keeping the client as small it can be. It's already on there list for WSA to clean up it's own files. This is the Webroot Product support Forum not a forum where someone can come by and make a utility and offer it to staff or it's members.@ wrote:
Brad has reached out to me, and I will take his utility and run it by the folks here. We actually have lots of folks on our support team who do similar workaround utilities to fix issues, and they sometimes get incorporated in the product. So who knows - maybe we'll end up doing the same with your utility Brad!
IMO,
Daniel
OK, keep me posted on your decision. I did some further work on it this weekend but didn't get it finished to my satisfaction quite yet. I will squeeze in some more time as I am able. If the development team wants to do this themselves, I understand; I'm not trying to step on anyones toes here, but I had to do something to reclaim that space on my HD (and I wasn't going to pick through 3900 files manually).
FYI, Here is an updated shot of the main window; the list is sorted by total size of db files associated with each exe, the blue db items are to be left alone, the red db items are to be recycled, the gray db items are referenced in the log but do not exist on disk.
There is now also a filter which allows the user to show only excluded exe & db files and also db files which are associated with exes which have been deleted (marked with the (FILE NOT FOUND) suffix):
If something similar could be added to WSA, that would be great; otherwise, I'm going to be using this.
FYI, Here is an updated shot of the main window; the list is sorted by total size of db files associated with each exe, the blue db items are to be left alone, the red db items are to be recycled, the gray db items are referenced in the log but do not exist on disk.
There is now also a filter which allows the user to show only excluded exe & db files and also db files which are associated with exes which have been deleted (marked with the (FILE NOT FOUND) suffix):
If something similar could be added to WSA, that would be great; otherwise, I'm going to be using this.
Hello, I'd just like to say that just this morning I had 20GB free of my 250GB SSD and after installing an update to an application of mine Webroot kept complaining about it and I had to allow access. However after this my HDD kept decreasing in size to only 700MB left and I discovered my WRData folder to be over 46GB in size. I want to know what can be cleared from this folder.
Hi nebula
I have posted this before but cannot find the thread to direct you to so I will repost the information here.
If you are technical (and I believe that you are) then are there are other ways that avoids the uninstall/reinstall, which involves the review of the 'dbnnnn.db files in the C:ProgramdataWRDATA folder, and then the deletion of selected ones of this file type. But I should stress at the outset that you need to be careful when employing these approaches.
The first is not ideal but it does avoid the uninstall/reinstall and also preserves to some extent the rationale for those files; as you may have surmised from the thread these files are the journal files produced when WSA sets a file/app to 'Monitor' and so are important in case WSA has detected a suspicious or an as yet undetermined (in terms of goodness/badness) file/app and then determines it is bad and then needs to roll back its activities, etc., in which case the relevant 'dbnnnn.db' file is required.
The problem is that we cannot easily tell which 'dbnnnn.db' relates to which file/app in the system (there is a way by looking in the Registry but I have lost my notes on that...must try to find them) so the best thing to do is to (i) check all places in WSA where files could be set to 'Monitor', decide whether they are OK or not (and if in doubt leave them as such), (ii) try to work out roughly when a file/app that is set to 'Monitor' was so set & (iii) then go to the C:ProgramdataWRDATA folder and carefully delete all 'dbnnnn.db' files that are either prior to a certain period, i.e., say more than 2 weeks old, on the basis that WSA should have been in a position to sort out if the journal is required or not, or delete everything except for the 'dbnnnn.db' files that are circa the dates that you believe that you 'Monitored' files/apps may have started to be monitored, etc.
The above may seem more convoluted that an uninstall/reinstall, but I have found that it seems to work well, and does give you a better chance of keeping 'dbnnnn.db' files that may be needed; after all an uninstall/reinstall should clear all the files in that folder regardless of whether they are needed or not.
A second, alternative way which may be more accurate but takes longer is to run Save a Scan Log and from the text file produced do a search for ‘(nnnn)’ (without the ‘’ marks) where ‘nnnn’ is the ‘nnnn’ portion of the ‘dbnnnn.db’ file(s) found in the C:ProgramdataWRDATA folder. This should find an entry in the Log from which you can identify the application/file that is being monitored and to which the journal file concerned belongs;
Sat 12-09-2015 10:21:40.0098 Monitoring process C:BrowsersMaxthonPortableBinMaxthon.exe [63D4BC1DABF35B13C94A9FAE02D7C0FF]. Type: 3 (1235)
relates to file ‘db1235.db in the C:ProgramdataWRDATA folder.
Of course, this is not ideal in terms of dealing with many ‘dbnnnn.db’ files but if one can identify the largest of these files and start with those then one can reduce (safely) the size of the folder.
Hope that helps you with your space issue and the size of your WRData folder.
Regards, Baldrick
I have posted this before but cannot find the thread to direct you to so I will repost the information here.
If you are technical (and I believe that you are) then are there are other ways that avoids the uninstall/reinstall, which involves the review of the 'dbnnnn.db files in the C:ProgramdataWRDATA folder, and then the deletion of selected ones of this file type. But I should stress at the outset that you need to be careful when employing these approaches.
The first is not ideal but it does avoid the uninstall/reinstall and also preserves to some extent the rationale for those files; as you may have surmised from the thread these files are the journal files produced when WSA sets a file/app to 'Monitor' and so are important in case WSA has detected a suspicious or an as yet undetermined (in terms of goodness/badness) file/app and then determines it is bad and then needs to roll back its activities, etc., in which case the relevant 'dbnnnn.db' file is required.
The problem is that we cannot easily tell which 'dbnnnn.db' relates to which file/app in the system (there is a way by looking in the Registry but I have lost my notes on that...must try to find them) so the best thing to do is to (i) check all places in WSA where files could be set to 'Monitor', decide whether they are OK or not (and if in doubt leave them as such), (ii) try to work out roughly when a file/app that is set to 'Monitor' was so set & (iii) then go to the C:ProgramdataWRDATA folder and carefully delete all 'dbnnnn.db' files that are either prior to a certain period, i.e., say more than 2 weeks old, on the basis that WSA should have been in a position to sort out if the journal is required or not, or delete everything except for the 'dbnnnn.db' files that are circa the dates that you believe that you 'Monitored' files/apps may have started to be monitored, etc.
The above may seem more convoluted that an uninstall/reinstall, but I have found that it seems to work well, and does give you a better chance of keeping 'dbnnnn.db' files that may be needed; after all an uninstall/reinstall should clear all the files in that folder regardless of whether they are needed or not.
A second, alternative way which may be more accurate but takes longer is to run Save a Scan Log and from the text file produced do a search for ‘(nnnn)’ (without the ‘’ marks) where ‘nnnn’ is the ‘nnnn’ portion of the ‘dbnnnn.db’ file(s) found in the C:ProgramdataWRDATA folder. This should find an entry in the Log from which you can identify the application/file that is being monitored and to which the journal file concerned belongs;
Sat 12-09-2015 10:21:40.0098 Monitoring process C:BrowsersMaxthonPortableBinMaxthon.exe [63D4BC1DABF35B13C94A9FAE02D7C0FF]. Type: 3 (1235)
relates to file ‘db1235.db in the C:ProgramdataWRDATA folder.
Of course, this is not ideal in terms of dealing with many ‘dbnnnn.db’ files but if one can identify the largest of these files and start with those then one can reduce (safely) the size of the folder.
Hope that helps you with your space issue and the size of your WRData folder.
Regards, Baldrick
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
1 person likes this
Thanks for the information. I wish there was a way to tell webroot where to store these DB files because this took up almost the entirety of my SDD
Hi Nebula
Completely understand where you are coming from. Hopefully things will improve in that area in the future as I believe that the Development Team are looking at this whole area.
I try to temper things by remembering that the .db files in the WRData folder forma a valuable part of the insurance that WSA provides should an unknown fiel/app be found on your system and then prove to be malicious. ;)
Regards, Baldrick
Completely understand where you are coming from. Hopefully things will improve in that area in the future as I believe that the Development Team are looking at this whole area.
I try to temper things by remembering that the .db files in the WRData folder forma a valuable part of the insurance that WSA provides should an unknown fiel/app be found on your system and then prove to be malicious. ;)
Regards, Baldrick
Webroot SecureAnywhere Complete Beta Tester v9.0.24.49, imaged by Macrium Reflect v7.2
1 person likes this
Reply
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.