New
#1661
The default scheduled scanning is around 2 am when many have the computer off (so no scan). It is also the default to do the scan after startup if missed which hinders initial startup productivity and resource use right after boot. On higher-end computers this is not an issue but on older slower computers with spinning drives (non-SSD) and single or just a dual-core processor and 4 gigs of ram it is an issue.
it will not effect the default during the back up process ?
Hi,
Was said by mbam that scanning on ssd's is bad and not to overdue it
So now you're saying a every night or everyday scan is good
I saw this scanning doing a benchmark and thought great this is what I want going on in the background as I'm pushing the crap out of my rig a silly scan I know I deleted
Bottom line the default scanning schedules were deleted and an update must of added it back that is unacceptable.
I do a quick scan daily and a threat scan weekly. SSD's are not what they used to be. People overdo the scans by doing Custom full scans of the drives instead of letting MB do the threat scan.
If you want to do your scans manually then it is up to you. Some like the set and forget approach.
The default scan schedule will be reinstated if a clean install or a repair is done with the support tool. Don't quote me on this but I think it is also restored when a full version upgrade is applied. I have seen clients with an added default schedule back on top of the scans I set up originally. Since you deleted all the schedules you got back just the default at one point.
A lot of people go overboard with their scans, really all you need is to scan once a month unless you think you recently were infected by something. There is a reason AV's have real-time protection, if its working why over scan??