On 02/07/2017 11:11 AM, Paul wrote:
The Real Bev wrote:


Win7SP1 x64

3020369

I downloaded and 'saved' that one. Killed the wusWhatever so only one
instance would be running. It's been "Searching for updates on this
computer for maybe an hour now, and I'm going to let it run all night.
I'd previously let it attempt to download the latest 2 essential updates
for maybe 24 hours with no result. POS, but NO I'm not going to switch
to win10.

These two should be enough to re-establish operation,
until February 14. After the second Tuesday (Patch Tuesday),
this will need to be re-tested again for efficacy.

I let that run for another hour with no result and killed it. Started
up the download of the 2 essential updates, which is still running with
no result roughly 12 hours later.

People should NOT have to go to this much trouble. Heretofore I had
assumed that it was a queueing problem and that M$ is running the update
server on a 386 machine with a 64K modem, but now I'm not so sure :-(

Servicing Stack

http://catalog.update.microsoft.com/...aspx?q=3020369

July 2016 update rollup for Windows 7 SP1

http://catalog.update.microsoft.com/...aspx?q=3172605

Vista is a lot harder to fix, and Windows Update might never
paint the screen with updates on that one. But I did get
very lucky, and I found a single post from the wsusoffline
forum with the list of updates to tip Vista upright again.

The Wsusoffline guys have a text file with "prerequisites".
These are patches they know they have to load first, before
they call wuauserv. And while their methodology doesn't always
work, it's the list of patches that I'm interested in. So I'll
be "mining" that when necessary, from now on. If they know
the answer, it'll be hiding in a file in their downloadable
package.

HTH,
Paul

I H too, but it didn't :-(


--
Cheers, Bev
"Anonymity is a shield from the tyranny of the majority."
-- U.S. Supreme Court, McIntyre v Ohio Elections,1995