New
#211
Thanks, I too have noticed it will run and not run, yet getting the (0x2) more often than not.
Windows Defender Scheduled Scan does not work; message 0x2 is returned - Windows 10 Forums
The problem I have with Defender's scheduled scan task when it does run is it's really unpredictable, often starting then stopping at any mouse movement while I'm in the middle of my work as I have never seen Windows honor my maintenance time window under Control Panel > Security and Maintenance > Change Maintenance Settings > Run Maintenance Tasks daily at : [ Time ]
Nor by adding a trigger in Window's task properties for that matter which again would get reset every month anyway. Just easier to run my own and turn theirs off.
Hi there
If you guys are really serious about protecting your machines you should understand the whole concept of "Event Driven Processes".
Since a new threat could appear at ANY time -- not predictable in say a typical "Tuesday update" cycle or similar then presumably you want to get your system protected as soon as possible so I'm quite happy for a WD update / definition update to be performed any time it wants to.
I'm sure some of you on these forums have often heard of highly paid economists or politicians complaining that a country's earnings fall is due to "poor productivity" -- however this is absolute 100% garbage in an essentially modern service driven and event driven process economy-- most post 1st world economies aren't predictable things like production in factories etc -- my favourite question to these people is "How do you measure the productivity of say an Opera Singer" .
In any case with things like Just In Time ordering and delivery what's the point of producing large inventories of stock, stored in expensive real estate when you've got no idea when or if the demand for it materializes.
Just let WD do its job whenever it needs to. Consider it as an event driven process or a just in time component.
Cheers
jimbo
It's a natural manifestation of your client detection interval (22 hours, by default), and the frequency of Defender updates. If the client only checks once a day, then only the latest update will be "Needed", and the others were synchronized in vain.
If it is your intent to maintain signature files for Windows Defender, Microsoft Security Essentials, or Forefront (now part of System Center 2012) via WSUS, I suggest the following:
Configure an automatic approval rule for the Definition Update classification
Enable the policy option "Allow Automatic Updates immediate installation"
Configure your clients with a 6-hour detection frequency so that they can regularly get the newest signature file from WSUS.
I don't have WD Verification Task in my task scheduler but am still
getting the windows modules installer restore points on a daily basis.
Any other options to try and stop these restore points?