You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

"dslman" wrote:
> Check the windows update log. Only entries in there are automatic update
> checks.
>
> I even tried the things that Rajesh suggested. Please see my reply to him.
>
> Thanks so much for your help and I'm still open for suggestions.
> --
> Thanks, dslman
>
>
> "MowGreen [MVP]" wrote:
>
> > Initiate a manual visit to Windows Update. If the system still cannot
> > access it, open the WindowsUpdate.log and post the last 40 or so lines
> > of it into your reply, please.
> >
> > Start > Run > type in [or copy&paste]
> >
> > %windir%\windowsupdate.log
> >
> > Click OK or press Enter
> >
> > MowGreen [MVP 2003-2007]
> > ===============
> > *-343-* FDNY
> > Never Forgotten
> > ===============
> >
> >
> >
> > dslman wrote:
> >
> > > I tried all on the winhelponline .com article. Did not improve. Still can't
> > > get to the update site. I show mozilla/4.0 (compatible; msie 6.0) in the
> > > java script. I do not have the firewall on and even when I did, I was able
> > > to get to the Windows Update site with out any problems in the past. Still
> > > seems like there is something being passed to the update site that makes the
> > > site think I am NOT an XP user.
> > >
> > > I did receive auto update notification today and was able to download and
> > > install everything that way, but I would like to go out to the update site
> > > and check for other than critical updates.
> > >
> > > Any suggestions and/or additional help would be greatly appreciated.
> > >
> > > Thanks for the replies so far.
> >

The update being delayed is 1B9AADDD-421C-4484-811D-D0B1B28332D0
The portion of the log you showed us doesn't include when that was first seen,
so we don't know how long you have already been delayed by this.

If you think that that you have been delayed by it too long you might try
using bitsadmin (in a cmd window) to resume that job manually.
FWIW doing that once worked for me when I noticed that an update
had apparently been in that state for several weeks.