Post by AmmammataI'm using WSUS
at 14:38 it started "listing ids of missing updates (please be patient...)"
now, at 14:59, it hasn't yet finished :(
what the hell is doing?
it's an intel core i3, with 8Gb ram and 256gb ssd, capable of zillions of
operations per second! The internet connection is ok and runs at 50mbps
I mean, if I manually make a list of ids and thick away what's already been
installed, I spend less time then this disgusting update procedure
WSUSoffline and MBSA and WUA (Windows Update Agent) have to retrieve
Microsoft's latest wsusscn2.cab file. That has the most recent list of
security updates for Windows. Sorry but I don't know how often
Microsoft publishes a new version of their wsusscan.cab file.
WSUSoffline (and MBSA) will only retrieve security updates, not any of
the important or recommended updates. That's because Microsoft doesn't
publish a .cab file with that list. The .cab file (with the update
manifest, not for one of the many updates) is about 160MB in size. With
a fast Internet connection, it should download quickly UNLESS
Microsoft's server is slow to respond or unresponsive. Just because an
update is listed in the .cab file doesn't mean it should be applied.
There are supercedes and dependencies that have to be resolved which
requires interrogation of your current Windows setup.
I just ran WSUSoffline and it reported that the version of wsusscn2.cab
was the same as it downloaded before. I ran it about 10 days ago so
Microsoft didn't have any newer version of the manifest file. Then
WSUSoffline proceeded to the Office update retrieve. I'm not sure how
that works, only how WSUSoffline (and MBSA) have to get the .cab file to
get a list of Windows updates.
In the "log" subfolder (under wherever you put WSUSoffline) should be a
log file showing the download progress. Might clue you in on where
WSUSoffline is getting stuck or if it is doing something that takes a
long time.
UpdateGenerator.exe does not apply updates. It only retrieves the
wsusscn2.cab file to determine what update *files* to download. You get
a local repository of updates. Updates are not applied until you later
run UpdateInstaller.exe. So it is unclear which process is hanging:
retrieving the updates or applying them. Applying updates can take a
long time and several reboots.
While you could post in their forums as to what is your problem (not
well expressed here so be sure to have the download log and note what
the console window shows as the hanging point and whether you are
retrieving or applying the retrieved updates). I tried posting there 8
days ago about how UpdateInstaller.exe works and never got a response.
I've use UpdateGenerator.exe to retrieve the updates and create a local
repository of them but I've yet had to run its UpdateInstall.exe.