New install... then Microsoft Update fails...?

[Kenneth]

Howdy,

After too many years, I decided to do a re-install of Win
2000 Pro on one of our machines.

I installed from the OEM CD.

When up and running, I created an image of the system.

Next, I went to the Microsoft Update site. It installed the
necessary software (to allow use of the site) and then told
me that I needed to update Windows to fully use the
functions of the site.

I did that, bringing the box to SP4.

Next, I clicked on the "Microsoft Update" shortcut on my
start menu but nothing at all happened.

I then went directly to the Update site, launched the
process, but saw after a few minutes that it was hung up.
The progress bar just sailed along, eventually, for more
than 30 minutes.

With that, rather than trying some sort of repair, I just
thought it easier to return to the former state (for which I
had an image.)

I restored the image, and followed the steps above,
unfortunately, with exactly the same result:

So, with the second attempt, if I click on the Update
shortcut, nothing happens, and if I go to the Update site,
it just loops endlessly.

I would certainly appreciate any suggestions about solving
this hassle.

Sincere thanks,

 

[Jim Howes]

Kenneth wrote:
[snip]

So, with the second attempt, if I click on the Update
shortcut, nothing happens, and if I go to the Update site,
it just loops endlessly.

I would certainly appreciate any suggestions about solving
this hassle.

Are you connecting to the internet via a proxy server by any chance?
I find that some proxy servers cause no end of grief and timeouts in windows update.

 

[NewScience]

First, until you install the Microsoft Update ActiveX control from the
Windows Update site, the Microsoft Update shortcut will not work. You need
muweb.dll for that to work and the correct calling parameters to the DLL.

Windows Update check for Service Packs do take a great deal of time. It
basically has to take a COMPLETE snapshot of your system. I MEAN
EVERYTHING.

The best way to determine what is going on is to use an application called
FileMon, turn the filter on for svchost.exe and wuaclt.exe and watch what
happens when you wait for Windows Update.

Depending on your connection speed (dial-up, DSL, Cable,...?), this can take
a LONG time. On my system (which IS very slow ... Pentium I 166mkhz), it
can take at least 2-3 hours.

I'm sure you have a faster CPU, but FileMon will tell you if it is
processing if it is gathering data from the filesystem.

Also make sure that BITS is on in Services (Manual or Automatic), and
Automatic Updates is set to Automatic and has been started.

 

[Kenneth]

First, until you install the Microsoft Update ActiveX control from the
Windows Update site, the Microsoft Update shortcut will not work. You need
muweb.dll for that to work and the correct calling parameters to the DLL.

Windows Update check for Service Packs do take a great deal of time. It
basically has to take a COMPLETE snapshot of your system. I MEAN
EVERYTHING.

The best way to determine what is going on is to use an application called
FileMon, turn the filter on for svchost.exe and wuaclt.exe and watch what
happens when you wait for Windows Update.

Depending on your connection speed (dial-up, DSL, Cable,...?), this can take
a LONG time. On my system (which IS very slow ... Pentium I 166mkhz), it
can take at least 2-3 hours.

I'm sure you have a faster CPU, but FileMon will tell you if it is
processing if it is gathering data from the filesystem.

Also make sure that BITS is on in Services (Manual or Automatic), and
Automatic Updates is set to Automatic and has been started.

Hello again,

I sincerely appreciate all of your suggestions...

The problem turned out the be the BITS setting:

It was (somehow) set to "On-Manual."

I changed it to "On-Auto" and tried the Update site with no
luck.

Then, before doing anything further, I decided to re-boot.

Happily, that eliminated the problems I was having.

All the best, and sincere thanks,