We've just discovered this bug about an hour ago...what a coincidence. This issue is going to be fixed in the next 5.0.16.0 build.UPDATE: fixed in the 5.0.16.0
Please note if you change settings for a DSF folder that have active scan running, those changes won't be picked-up by the scan.