I have been noticing on various domain computers that critical updates are
available, but not automatically installing since the move to v5. This has
been asked over and over on Usenet and on here, but with no answer from MS,
so I'm not the only one seeing the issue. I implemented mine via group
policies, and have disabled the ability for the end user to change the
settings. When I check, the updates are supposed to be running at 3:00 pm,
but this isn't happening.
Under the registry hive for the windows update service, this is what I have:
HKLM\software\microsoft\windows\currentversion\win dowsUpdate\Auto Update:
ConfigVer (dword) : 1
DetectionStartTime (SZ) : 2004.08.11 01:38:27
NextDetectionTime (SZ) : 2004-10-13 16:12:42 (tomorrow's date)
ODFFileURL (SZ) :
http://v4.windowsupdate.microsoft.com/odf/wuodf.xml
ResetAU (dword) : 1
ScheduledInstallDate (SZ) : 2004-10-13 22:00:00
I can run the updates manually, and see the critical updates that were
supposed to be installed automatically waiting to be downloaded.
What it looks like to me is that during the v4 to v5 update, the registry
changes haven't been made to the v5 site. If this is the case, and if this
is being implemented via group policies, how do we correct this across a
domain if the updates themselves aren't running? this is pretty aggravating.
Thanks.