Hi Borneq

 

Welcome to the Community Forums.

 

What you are reporting is an 'issue' that has been going on for some time now and there are a number of routes to effectively slimming down the size of the WRData folder re. the .db files. These are, in order of most appropriate & safest first, as follows:

 

1. Open a Support Ticket so that the Support team can review what is being monitored and whitelist any files that may need so doing so that the next time that you run a scan WSA should recognised that the item(s) being monitored are not longer 'undertimed' and then WSA should effectively stop monitoring the file(s) and remove the jornal (.db file).

 

2. Uninstall WSA, check to see if the WRData folder has been deleted and if not then delete it manually, and then do a clean reinstall WSA (we can provide instructions on how to do that).

 

3. If you are technical there is another way 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.

 

This is not ideal but it does avoid the uninstall/reinstall and also preserves to some extent the rationale for those files; as you may or may not have surmised, from analysis, 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.

 

An 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 t63D4BC1DABF35B13C94A9FAE02D7C0FF]. 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.

 

None of the above are a 'solution' in itself but may assist with you reclaiming space from the WRData folder.

 

Hope that helps?

 

Regards, Baldrick

---