Dave said:
The MSE definition updates are treated like any other updates. If you
want them to be updated automatically, you have to set your update
options to update automatically. Open "Windows Update" and click on
"Change settings" in the left hand column of the page. Use the drop down
menus and check boxes to set the update options.
From past discussions, some including MVPs who said they had internal MS
contacts, you need to leave the AU service enabled and set to Automatic
startup but you do NOT need to leave WU setup to do automatic updates.
MSE uses the AU service to get its updates. It doesn't rely on the WU
settings. So you can configure WU to only alert you of Windows updates
(but not download or install them) to prevent Microsoft from changing
the state of your host until you decide to permit it but MSE can still
use the AU service to get its automatic updates. That is, you don't get
stuck with having your Windows automatically updated if you don't want
that but you can still have MSE get its updates as long as the AU
service is enabled and running (Automatic startup).
MSE uses the AU service to check for its own updates. MSE does not use
the schedule for the WU updates. MSE uses its own schedule (once every
24 hours but may lag if the computer was powered off) which is not user
configurable but it does it updates through the AU service. The closest
that I've seen to let the user schedule when MSE gets its updates
(through the AU service) is to add an event in Task Scheduler that runs
"MpCmdRun.exe -SignatureUpdate" (I no longer have MSE so I can't verify
this command-line switch will work). Another way was to configure the
scheduled scan to check for updates before scanning and then schedule a
[quick] scan every day. That was back a couple years (2009) when MSE
had problems initiating its update so this was a workaround to make it
to an update whenever you scheduled a scan.
It's possible some anti-virus/malware disabled the Automatic Updates
service or the user thought it was an unneccessary and disabled it which
means MSE won't be able to get its updates. The AU service should be
set to Automatic for startup on Windows startup and should currently be
running. See
http://support.microsoft.com/kb/959894, method 3. In the
past, MS has used the AU service to push covert updates even if WU
settings were to notify only. As a consequence, many users that got
burned with BSOD bricks upon return to their host decided to disable the
AU service. When they wanted to do a WU update (after saving a backup
image of their OS partition), they would enable the AU service and
perform a manual WU update, install the updates, and then disable the AU
service. For such users, that also meant MSE wouldn't get its separate
updates. See article
http://preview.tinyurl.com/27k5l9o to see how MS
decided you will have WU set to automatic which you have to set back.
Other users found updates getting applied when WU was set to disable and
managed to avoid the covert updates by disabling the AU service.