Updates Won't Download !

This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?

On 9/21/2016 6:21 PM, SteveGG wrote:
This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?

I had one W7 machine doing the same thing. Ran it by the usual "fixes"
with no change.

Then I downloaded WSUS, found at http://download.wsusoffline.net/ and
told it to download everything for W7. After updating the system with
the resulting downloaded updates the system was back to normal,
including being able to download and install the latest updates that
came out later.

Might be worth a try to see if WSUS will flush out something stuck in
your PC like it did on mine.

On 9/21/2016 4:21 PM, SteveGG wrote:
This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?


With a very recent release of updates, I am quite sure Microsoft's
servers are operating at capacity. Many users want their updates
immediately, and there are those users who enable automatic updates.
Both of those can cause delays in downloading.

I always wait a week after an update is released befor installing it.
My primary reason for delaying is to see if anyone reports a problem
here about an update making things worse instead of better.

However, my delay also allows Microsoft's servers to finish delivering a
heavy load of updates. Then, I rarely have any trouble getting and
installing updates.

--
Donald Trump claims everyone likes him. Does that
include his ex-wives? How about the students who
discovered that their education at Trump University
was worthless? And how about the contractors,
suppliers, and employees he stiffed in his several
bankruptcies?

David E. Ross wrote:
On 9/21/2016 4:21 PM, SteveGG wrote:
This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?


With a very recent release of updates, I am quite sure Microsoft's
servers are operating at capacity. Many users want their updates
immediately, and there are those users who enable automatic updates.
Both of those can cause delays in downloading.

I always wait a week after an update is released befor installing it.
My primary reason for delaying is to see if anyone reports a problem
here about an update making things worse instead of better.

However, my delay also allows Microsoft's servers to finish delivering a
heavy load of updates. Then, I rarely have any trouble getting and
installing updates.


Yesterday, I used MBSA 2.3 to generate a list of 70 updates
for Windows 7. I used the Microsoft Catalog server, downloading
the files in one download session.

There was *no* delay using the shopping cart interface and
a copy of Internet Explorer, to download ~425MB of updates.
I installed each one later, one at a time, by double clicking the
downloaded installer file.

A couple of the updates downloaded in that way, were classed
by their installer as "not applicable". And after most
all of the updates where installed, MBSA 2.3 run again,
indeed, the two "failures" to install were no long dependencies.
That means some other update superseded those two, so they
weren't needed.

And that means MBSA cannot "do the math" to figure out
which update is not needed. But the updates themselves
seem to carry the proper information with them. Or at least,
query "something" to figure it out. Since MBSA doesn't
do the math, it doesn't get stuck in a loop like
wuauserv can.

And, without using *any* fancy Windows Update repair (no
July 2016 Cumulative, no '612 WU software update), the next
invocation of Windows Update only took a couple minutes.
And that's because there were only two security updates
pending at the time (updates I chose not to install
because their "Issues" section warned me away from them).

It took *forever* to do it this way. Probably 3+ hours
work. I do not recommend bringing an OS up to date this way.
And did it mainly to investigate the characteristics. I was
surprised that WU responded so rapidly when I was finished.

And one weird part, is in a previous experiment, I used
WU to patch up all the various versions of .NET. And after
doing all of them in one "session", WU then listed five
other updates that "magically" appeared to be needed
after the reboot. By using the MBSA method, there was
no "rinse and repeat cycle". The .NET patches where resolved
in just "one wave" of updates, and no new ones magically
appeared later.

That method does not process the optional updates, and
I'll be looking at them later. (At least some of those
need to be hidden, as I really don't care about "DST
in PagoPago". Ones like new certificates, I will
probably be adding.)

*******

On Windows 10, I've observed some strangeness related to
the define "usage interval". A Win10 install might be marked
as "user will be using system from 9AM to 5PM", with dialog
boxes for the user to adjust the time. And what's weird
about that, is the download logic for acquiring a new
version of the OS, *waits until 9AM* before it downloads.
In other words, it absolutely insists on waiting until
the user is working, to download an OS. That means, if
the OS download stage completes at 10AM, and the user decides to
reboot between 10AM and 5PM, the OS installation could
very well take place, *while you're trying to use the OS*.

I don't think the Win7 WU behavior functions this way,
but it's just another data point to consider.

Paul

On 22/09/2016 9:21 AM, SteveGG wrote:
This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?

Try this


http://answers.microsoft.com/en-us/w...6b36d0c?auth=1


--
~~~~~~~~~~~~
Maurice Helwig
~~~~~~~~~~~~

I went for the WSUS thing and it downloaded / installed lots of stuff
for about a half hour, but no change in the problem etc.

In article ,
says...

This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?

This is probably the same kernel update issue that has been causing
issues for nearly a year. Basically, with the current version of Windows
update, it gets stuck in a loop checking for which files to download if
there is a newer kernel file available.

That said, one of the recommended updates is the July rollup (was
optional before). This includes a newer version of Windows Update that
fixes the slow search/download issue. You can manually download this one
update, then install it. If it stalls trying to install this update, one
fix is to disconnect your computer from the network (unplug Ethernet
cable or disable WiFi), reboot, then install the update. After that,
turn your networking back on.
https://support.microsoft.com/en-us/kb/3172605

--
If there is a no_junk in my address, please REMOVE it before replying!
All junk mail senders will be prosecuted to the fullest extent of the
law!!
http://home.comcast.net/~andyross

On Thu, 22 Sep 2016 07:14:22 -0400, SteveGG
wrote:

I went for the WSUS thing and it downloaded / installed lots of stuff
for about a half hour, but no change in the problem etc.

I've used WSUS on several Windows 7 SP1 reinstalls, all of which
refused to update, as well as fixing some unupdatable machines. Worked
fine every time. Windows update and everything else seemed to function
OK afterwards, and the process went fairly quickly. Much easier than
rolling the dice with a few manually downloaded "key" updates or
slipstraming all the updates (which you somehow have to get anyway),
and burning a DVD. But WSUS isn't real user friendly. I had to study
it a little to establish a routine for what I do, and couldn't figure
out a way to automate it. Wish the WSUS developers would release an
automated utility to do what Windows Update is supposed to do.

SteveGG wrote:
I went for the WSUS thing and it downloaded / installed lots of stuff
for about a half hour, but no change in the problem etc.


WSUSOffline is a two-stage process.

The first stage, you run the tool and tick the
boxes for what materials you want downloaded.

WSUSOffline gets the Microsoft manifest file, and
figures out what to download. If you ticked the box
for Win7 updates, it would get the Security Updates
and not the Optional Updates.

The actual update files, are downloaded from Microsoft,
not from the wsusoffline.net site. Microsoft lawyers would
descent, if it was done any other way. So the files are
traceable to Microsoft, as *direct* downloads.

The program has storage options, for preparing
optical media. flash key or whatever.

*******

Now, with USB flash key in hand, say you have a half
dozen Windows 7 computers in your house. You walk
from computer to computer with the USB key. One
of the folders has an executable you run, and that
does the actual *install* onto the destination machine.

*******

So the stage you've done is the "Preparation" phase.
The first phase.

Now, you go to the folder with the collected materials
in it, and run the executable that does the
install, and it installs the stuff.

For any materials that are "not applicable", I would
expect them to stop early in the install process. So
if Win7 normally had 200 updates, you had installed
185 of them, you plug in the USB key and run the
executable, it would install 15 more.

That's the basic idea.

*******

And as long as you can find the folder which is intended
for doing the install, it should have the gigabytes
of materials collected in it. Here is a picture showing
how easy it is to figure this out. If your browser is
zoomed out, click to magnify.

http://s14.postimg.org/3qhhtj0yp/wsusoffline.gif

That picture, shows the folder structure of my collection
for Windows 7, and the folder sizes tell you where the
"goldmine" is.

Paul

On 21 Sep 2016, Maurice Helwig
wrote in alt.windows7.general:

Try this

http://answers.microsoft.com/en-us/w...6b36d0c?auth=1

This worked for me. Hooray!

My Win7-64 laptop has not been able to check for updates for about
the past 2 months. It would spend hours or days searching for
updates and either never complete that process or would find
nothing. I just applied the above fix and it kickstarted WU back
into action and it found 6 or 8 pertinent updates.

On 9/22/2016 6:14 AM, SteveGG wrote:
I went for the WSUS thing and it downloaded / installed lots of stuff
for about a half hour, but no change in the problem etc.

For what it's worth, when I run WSUS I usually download both versions
32/64-bit since I have both versions around someplace but you can
download only the one you want to speed things up.

As for the rest of the options on the main WSUS "Generator" page under
Options, I usually check all of them except the Create ISO image(s) and
the USB medium sections.

Then after running the Generator to get the updates from Microsoft I go
to the Client folder and run the Updateinstaller.exe program to actually
do the update to my local copy of Windows.

Is this what you did, or did you just do the first part where it
captured the updates from Microsoft but not actually run the
updateinstaller in the client folder?

On Wed, 21 Sep 2016 19:21:26 -0400, SteveGG wrote:


This is a follow up to a posting about a week ago on the same problem.

Windows update now shows about 12 important and 9 optional updates,
but stalls after a bit, when trying to download them. Anyone else
having this trouble?

In spite of this, everything seems to continue to work, but I guess
that's not surprising.

Tried everything suggested so far, but N/G.

Further solutions to try ?

Have you tried this?

http://wu.krelay.de/en/

(Since you've started a new thread I'm reluctant to check.)

--
s|b

On Thu, 22 Sep 2016 10:09:11 -0600, Nil wrote:

On 21 Sep 2016, Maurice Helwig
wrote in alt.windows7.general:

Try this

http://answers.microsoft.com/en-us/w...6b36d0c?auth=1

This worked for me. Hooray!

My Win7-64 laptop has not been able to check for updates for about
the past 2 months. It would spend hours or days searching for
updates and either never complete that process or would find
nothing. I just applied the above fix and it kickstarted WU back
into action and it found 6 or 8 pertinent updates.

Your "Hooray" motivated me to read the link posted by Maurice, and I am glad I did. I was unaware that MS is
changing the way Windows update works on October 8, 2016. I did a little research and found some articles on
the topic which I will post separately.

On 22 Sep 2016, Stormin' Norman wrote
in alt.windows7.general:

Your "Hooray" motivated me to read the link posted by Maurice, and
I am glad I did. I was unaware that MS is changing the way
Windows update works on October 8, 2016. I did a little research
and found some articles on the topic which I will post separately.

Thank you. I saw that comment, too, and realized I don't know what the
plan is, either. I bet it's something I should know. I'm already set up
for manual updates and I'm prepared to cease updating altogether if
need be.

I seem to recall talk about updates coming in aggregate lumps,
eliminating the ability to pick and choose. If that's what he's talking
about I think I can do without further updates at this late stage of
Windows 7's career.

On Thu, 22 Sep 2016 11:13:24 -0500, GlowingBlueMist
wrote:

On 9/22/2016 6:14 AM, SteveGG wrote:
I went for the WSUS thing and it downloaded / installed lots of stuff
for about a half hour, but no change in the problem etc.

For what it's worth, when I run WSUS I usually download both versions
32/64-bit since I have both versions around someplace but you can
download only the one you want to speed things up.

As for the rest of the options on the main WSUS "Generator" page under
Options, I usually check all of them except the Create ISO image(s) and
the USB medium sections.


I would only add that there is an easily overlooked check box on the
WSUS Generator UI that, when checked, allows WSUS to reboot as
required when installing updates. On a new Windows 7 SP1 install there
will be upwards of 150 updates. If you don't check the reboot box, it
will install four or five, then wait for you to reboot the machine,
then after you reboot, install a few more and wait again for you to
reboot etc. etc.
Then after running the Generator to get the updates from Microsoft I go
to the Client folder and run the Updateinstaller.exe program to actually
do the update to my local copy of Windows.

Is this what you did, or did you just do the first part where it
captured the updates from Microsoft but not actually run the
updateinstaller in the client folder?

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus