Here's the deal: Check for Updates goes via AutoUpdate. For the average
home user, that should be working just fine. For some corporate users, that
goes to a SUS or WSUS server centrally maintained by corporate network
administrators.
In those cases:
SUS--Windows Defender signature updates are not available via SUS, which has
an end-of-life of December 2006.
WSUS--The administrator must enable the new class of updates for Windows
Defender.
So--for some users, manually going to Windows Update works, while the
background, automatic update doesn't--because of network infrastructure
issues.
Does that fit your situation? It is possible to dig into this more deeply:
Do an attempted update: help, about, check for updates.
Then do start, run, notepad %windir%\windowsupdate.log <enter>
This can be a very large file--leave it some time to "settle."
Then go down the very end, and cut and paste (or just read yourself if so
inclined) that last session .--you can paste it to a response here, if you
want. I may (can't tell--pretty inexperienced, but gaining fast) be able to
spot what is happening from those log entries.
In general, however, if you are on a managed corporate lan, you'll need help
from the network administrators to get automatic updates for Windows
Defender.
--
Matt Kershaw said:
Bill Sanderson said:
Have you been to Windows Update to see whether Signature updates are
offered?
Thanks, Bill, I just tried that. I did see the new update [Definition
Update
1.13.1286.1 for BETA Windows Defender (KB915597)] and downloaded/installed
it. This is the required process for getting updates? Is the "Check for
Updates" button on WD itself non-functional at this time?
-m-