Windows 7 maintenance discontinued by MS?

Except for Security Essential virus DB updates, I have not received any
other Win7 updates since the end of June. Two important updates that I
did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates is
perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I tend
bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.

"cameo" wrote in message
news
Except for Security Essential virus DB updates, I have not received any
other Win7 updates since the end of June. Two important updates that I
did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates is
perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I tend
bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.


See Paul's post in the thread "install msu file".

cameo wrote:
Except for Security Essential virus DB updates, I have not received any
other Win7 updates since the end of June. Two important updates that I
did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates is
perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I tend
bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.


You can review your updates, and check for "successful" or "failed"
status. If a "successful" instance of an update comes after
a failed one, then it is fixed. If the last instance was "failed",
then it needs to be fixed.

https://s18.postimg.org/hbmqwnjrd/reviewyourupdates.gif

You can go to catalog.update.microsoft.com and get MSU versions
of updates. If you have a failed one, you go to the catalog
server and download the correct version (Win7 x64 say). The trick
is installing them.

The MSU file, when you double-click, it starts to install. But,
it wants to talk to wuauserv process on your machine, just
like an update would. If wuauserv is busy, this prevents
the MSU from installing efficiently.

To stop this, you could stop and start wuauserv. But
an easier solution is to disconnect the network cable,
reboot, then install the MSU after it comes up.

If you see several failed updates, you'd download all the failed
ones that need repair. The MSU has an option to not reboot after
it is installed, and if you're stringing several of them
together, you only reboot the machine after the last one
is installed.

Then, you can go back and review your update history.

If all looks good, and the plumbing is no longer
jammed with broken updates, the update process should
then finish the job of installing more updates. You'll
need to connect the network cable again, before this
will happen.

For large numbers of updates, the "wusa.exe" program
is what installs an MSU. You can script the installs
of all the MSUs, then walk away while it runs. The wusa
accepts command line options, like an option to prevent
reboots. So you have some basic controls for scripting
them and getting a good result. In your case, the number
of failed updates that needed to be added by hand, is
probably only one or two at most. So you won't need
to learn about any scripting, and it can all be done
while you watch it.

Any time my Windows Update was broken, so far I haven't
needed to reset Windows Update. (There are some scripts
to do that.) Instead, installing MSU files by hand,
generally gets Windows Update working again.

*******

Windows Update also has the wuauserv bug, when it
spins in a loop for hours on end. The above recipe
is for "jammed plumbing". Fixing the looping wuauserv bug
requires a certain couple patches, and most
likely you already have these installed.

If wuauserv is looping, it might take 5-20 hours
to come back. If the problem is not present, the
time drops to around 3-5 minutes or so. If you install
MSU files, then that part of it is less evident.
As long as you pull the network cable, reboot,
so wuauserv cannot get into a looping mood,
the MSUs will work.

Paul

In article , lid (cameo) wrote:

*From:* cameo
*Date:* Fri, 25 Nov 2016 00:29:42 -0800

Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit
Edition

I wonder if the Win7 software module that processes these MS
updates is perhaps corrupted, but I would not know how to refresh
that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.

Follow http://wu.krelay.de/en/ and see if that gets things running again.

--
Regards
John ) Remove the obvious to reply...

On Fri, 25 Nov 2016 10:35:34 +0200, Live wrote:

See Paul's post in the thread "install msu file".

A message-id would be nice.

--
s|b

"s|b" wrote in mesage
...
On Fri, 25 Nov 2016 10:35:34 +0200, Live wrote:

See Paul's post in the thread "install msu file".

A message-id would be nice.

Message-ID:

On Fri, 25 Nov 2016 20:16:18 +0200, Live wrote:

A message-id would be nice.

Message-ID:

Tnx!

--
s|b

On 11/25/2016 1:35 AM, Paul wrote:
cameo wrote:
Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates
is perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.


You can review your updates, and check for "successful" or "failed"
status. If a "successful" instance of an update comes after
a failed one, then it is fixed. If the last instance was "failed",
then it needs to be fixed.

https://s18.postimg.org/hbmqwnjrd/reviewyourupdates.gif

You can go to catalog.update.microsoft.com and get MSU versions
of updates. If you have a failed one, you go to the catalog
server and download the correct version (Win7 x64 say). The trick
is installing them.

The MSU file, when you double-click, it starts to install. But,
it wants to talk to wuauserv process on your machine, just
like an update would. If wuauserv is busy, this prevents
the MSU from installing efficiently.

To stop this, you could stop and start wuauserv. But
an easier solution is to disconnect the network cable,
reboot, then install the MSU after it comes up.

If you see several failed updates, you'd download all the failed
ones that need repair. The MSU has an option to not reboot after
it is installed, and if you're stringing several of them
together, you only reboot the machine after the last one
is installed.

Then, you can go back and review your update history.

If all looks good, and the plumbing is no longer
jammed with broken updates, the update process should
then finish the job of installing more updates. You'll
need to connect the network cable again, before this
will happen.

For large numbers of updates, the "wusa.exe" program
is what installs an MSU. You can script the installs
of all the MSUs, then walk away while it runs. The wusa
accepts command line options, like an option to prevent
reboots. So you have some basic controls for scripting
them and getting a good result. In your case, the number
of failed updates that needed to be added by hand, is
probably only one or two at most. So you won't need
to learn about any scripting, and it can all be done
while you watch it.

Any time my Windows Update was broken, so far I haven't
needed to reset Windows Update. (There are some scripts
to do that.) Instead, installing MSU files by hand,
generally gets Windows Update working again.

*******

Windows Update also has the wuauserv bug, when it
spins in a loop for hours on end. The above recipe
is for "jammed plumbing". Fixing the looping wuauserv bug
requires a certain couple patches, and most
likely you already have these installed.

If wuauserv is looping, it might take 5-20 hours
to come back. If the problem is not present, the
time drops to around 3-5 minutes or so. If you install
MSU files, then that part of it is less evident.
As long as you pull the network cable, reboot,
so wuauserv cannot get into a looping mood,
the MSUs will work.

I figured that much myself. No failed ones succeeded later.
My last successful updates were on June 29.

cameo wrote:
On 11/25/2016 1:35 AM, Paul wrote:
cameo wrote:
Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates
is perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.


You can review your updates, and check for "successful" or "failed"
status. If a "successful" instance of an update comes after
a failed one, then it is fixed. If the last instance was "failed",
then it needs to be fixed.

https://s18.postimg.org/hbmqwnjrd/reviewyourupdates.gif

You can go to catalog.update.microsoft.com and get MSU versions
of updates. If you have a failed one, you go to the catalog
server and download the correct version (Win7 x64 say). The trick
is installing them.

The MSU file, when you double-click, it starts to install. But,
it wants to talk to wuauserv process on your machine, just
like an update would. If wuauserv is busy, this prevents
the MSU from installing efficiently.

To stop this, you could stop and start wuauserv. But
an easier solution is to disconnect the network cable,
reboot, then install the MSU after it comes up.

If you see several failed updates, you'd download all the failed
ones that need repair. The MSU has an option to not reboot after
it is installed, and if you're stringing several of them
together, you only reboot the machine after the last one
is installed.

Then, you can go back and review your update history.

If all looks good, and the plumbing is no longer
jammed with broken updates, the update process should
then finish the job of installing more updates. You'll
need to connect the network cable again, before this
will happen.

For large numbers of updates, the "wusa.exe" program
is what installs an MSU. You can script the installs
of all the MSUs, then walk away while it runs. The wusa
accepts command line options, like an option to prevent
reboots. So you have some basic controls for scripting
them and getting a good result. In your case, the number
of failed updates that needed to be added by hand, is
probably only one or two at most. So you won't need
to learn about any scripting, and it can all be done
while you watch it.

Any time my Windows Update was broken, so far I haven't
needed to reset Windows Update. (There are some scripts
to do that.) Instead, installing MSU files by hand,
generally gets Windows Update working again.

*******

Windows Update also has the wuauserv bug, when it
spins in a loop for hours on end. The above recipe
is for "jammed plumbing". Fixing the looping wuauserv bug
requires a certain couple patches, and most
likely you already have these installed.

If wuauserv is looping, it might take 5-20 hours
to come back. If the problem is not present, the
time drops to around 3-5 minutes or so. If you install
MSU files, then that part of it is less evident.
As long as you pull the network cable, reboot,
so wuauserv cannot get into a looping mood,
the MSUs will work.

I figured that much myself. No failed ones succeeded later.
My last successful updates were on June 29.


Do you have some failed ones then ? Or not ?

Using the MBSA 2.3 tool, you can check for security
updates.

https://www.microsoft.com/en-ca/down...s.aspx?id=7558

Take one of the "missing" ones from the listing,
then visit the catalog server catalog.update.microsoft.com
and enter the KB number and download the corresponding MSU.
Install that, after a reboot with network cable disconnected,
and see if the update "takes". Look in Windows Update history,
and the freshly installed security update should be listed
in the history.

That does *not* prove that Windows Update works. It proves
it has successfully taken an update. It doesn't
say anything about the health of BITS or wuauserv
and so on.

Most of the problems people see with Win7 are of the
"looping wuauserv" kind. That's where, you check for
updates, and the list never appears on the screen. At
one time, you would use

This used to be sufficient at one time, to make the
looping stop. The first one is a servicing stack update
from a while back. The second one has an actual update
to Windows Update materials. But really, the problem
is with the Windows Update manifest file, and it is one
of the reasons Microsoft is changing how updates work.

You may already have these updates, so check for these first
in your History.

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

Only if all reasonable workarounds have been investigated,
do you need to use stuff like this.

http://www.sevenforums.com/tutorials...ate-reset.html

Paul

On 11/25/2016 10:31 PM, Paul wrote:
cameo wrote:
On 11/25/2016 1:35 AM, Paul wrote:
cameo wrote:
Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates
is perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.


You can review your updates, and check for "successful" or "failed"
status. If a "successful" instance of an update comes after
a failed one, then it is fixed. If the last instance was "failed",
then it needs to be fixed.

https://s18.postimg.org/hbmqwnjrd/reviewyourupdates.gif

You can go to catalog.update.microsoft.com and get MSU versions
of updates. If you have a failed one, you go to the catalog
server and download the correct version (Win7 x64 say). The trick
is installing them.

The MSU file, when you double-click, it starts to install. But,
it wants to talk to wuauserv process on your machine, just
like an update would. If wuauserv is busy, this prevents
the MSU from installing efficiently.

To stop this, you could stop and start wuauserv. But
an easier solution is to disconnect the network cable,
reboot, then install the MSU after it comes up.

If you see several failed updates, you'd download all the failed
ones that need repair. The MSU has an option to not reboot after
it is installed, and if you're stringing several of them
together, you only reboot the machine after the last one
is installed.

Then, you can go back and review your update history.

If all looks good, and the plumbing is no longer
jammed with broken updates, the update process should
then finish the job of installing more updates. You'll
need to connect the network cable again, before this
will happen.

For large numbers of updates, the "wusa.exe" program
is what installs an MSU. You can script the installs
of all the MSUs, then walk away while it runs. The wusa
accepts command line options, like an option to prevent
reboots. So you have some basic controls for scripting
them and getting a good result. In your case, the number
of failed updates that needed to be added by hand, is
probably only one or two at most. So you won't need
to learn about any scripting, and it can all be done
while you watch it.

Any time my Windows Update was broken, so far I haven't
needed to reset Windows Update. (There are some scripts
to do that.) Instead, installing MSU files by hand,
generally gets Windows Update working again.

*******

Windows Update also has the wuauserv bug, when it
spins in a loop for hours on end. The above recipe
is for "jammed plumbing". Fixing the looping wuauserv bug
requires a certain couple patches, and most
likely you already have these installed.

If wuauserv is looping, it might take 5-20 hours
to come back. If the problem is not present, the
time drops to around 3-5 minutes or so. If you install
MSU files, then that part of it is less evident.
As long as you pull the network cable, reboot,
so wuauserv cannot get into a looping mood,
the MSUs will work.

I figured that much myself. No failed ones succeeded later.
My last successful updates were on June 29.


Do you have some failed ones then ? Or not ?

I wrote in my first post about those two important KB-s that had been
just sitting there in Windows Update page but every time I try to
manually force their install, they keep trying for hours (as the
progress bar indicates) but they can't complete. So after hours of that,
I just cancel the install. However, they don't show up in the update
history as failed installs.

cameo wrote:
On 11/25/2016 10:31 PM, Paul wrote:
cameo wrote:
On 11/25/2016 1:35 AM, Paul wrote:
cameo wrote:
Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit Edition

I wonder if the Win7 software module that processes these MS updates
is perhaps corrupted, but I would not know how to refresh that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.


You can review your updates, and check for "successful" or "failed"
status. If a "successful" instance of an update comes after
a failed one, then it is fixed. If the last instance was "failed",
then it needs to be fixed.

https://s18.postimg.org/hbmqwnjrd/reviewyourupdates.gif

You can go to catalog.update.microsoft.com and get MSU versions
of updates. If you have a failed one, you go to the catalog
server and download the correct version (Win7 x64 say). The trick
is installing them.

The MSU file, when you double-click, it starts to install. But,
it wants to talk to wuauserv process on your machine, just
like an update would. If wuauserv is busy, this prevents
the MSU from installing efficiently.

To stop this, you could stop and start wuauserv. But
an easier solution is to disconnect the network cable,
reboot, then install the MSU after it comes up.

If you see several failed updates, you'd download all the failed
ones that need repair. The MSU has an option to not reboot after
it is installed, and if you're stringing several of them
together, you only reboot the machine after the last one
is installed.

Then, you can go back and review your update history.

If all looks good, and the plumbing is no longer
jammed with broken updates, the update process should
then finish the job of installing more updates. You'll
need to connect the network cable again, before this
will happen.

For large numbers of updates, the "wusa.exe" program
is what installs an MSU. You can script the installs
of all the MSUs, then walk away while it runs. The wusa
accepts command line options, like an option to prevent
reboots. So you have some basic controls for scripting
them and getting a good result. In your case, the number
of failed updates that needed to be added by hand, is
probably only one or two at most. So you won't need
to learn about any scripting, and it can all be done
while you watch it.

Any time my Windows Update was broken, so far I haven't
needed to reset Windows Update. (There are some scripts
to do that.) Instead, installing MSU files by hand,
generally gets Windows Update working again.

*******

Windows Update also has the wuauserv bug, when it
spins in a loop for hours on end. The above recipe
is for "jammed plumbing". Fixing the looping wuauserv bug
requires a certain couple patches, and most
likely you already have these installed.

If wuauserv is looping, it might take 5-20 hours
to come back. If the problem is not present, the
time drops to around 3-5 minutes or so. If you install
MSU files, then that part of it is less evident.
As long as you pull the network cable, reboot,
so wuauserv cannot get into a looping mood,
the MSUs will work.

I figured that much myself. No failed ones succeeded later.
My last successful updates were on June 29.


Do you have some failed ones then ? Or not ?

I wrote in my first post about those two important KB-s that had been
just sitting there in Windows Update page but every time I try to
manually force their install, they keep trying for hours (as the
progress bar indicates) but they can't complete. So after hours of that,
I just cancel the install. However, they don't show up in the update
history as failed installs.



OK, using my Seamonkey web browser. I can go here and see.

http://www.catalog.update.microsoft....aspx?q=3162593

"Update for Microsoft Silverlight" 61.1MB

http://www.catalog.update.microsoft....aspx?q=3115321

"Definition Update for Microsoft Office 2010 (KB3115321)" 3.1MB
(Select 32 bit or 64 bit, according to your installed system type)

I can download those right now if I want, without any
Windows Update getting in the way. All I need is a
web browser and a working network connection.

Now, disconnect the network cable. Reboot the computer.
Double-click each MSU file that downloaded. Let WUSA
install them. Re-connect the network cable and
reboot the computer. If there is a tick box showing to
stop rebooting from happening, you can use that to
control reboot well enough, so that you can install
both before a reboot is required.

After the reboot, check Windows Update history. MSU installs
register there. If you have to do "cab" installs with DISM,
those are not logged in Windows Updates. Only some of the
very oldest updates were CAB based. Modern updates should
be MSU download files.

HTH,
Paul

On 11/25/2016 4:13 AM, John K.Eason wrote:
In article , lid (cameo) wrote:

*From:* cameo
*Date:* Fri, 25 Nov 2016 00:29:42 -0800

Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit
Edition

I wonder if the Win7 software module that processes these MS
updates is perhaps corrupted, but I would not know how to refresh
that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.

Follow http://wu.krelay.de/en/ and see if that gets things running again.

This German method sounds much simpler than what Paul suggested (and is
way over my head,) but even here the downloaded Win7 x64 Servicing Stack
Update for Sep 2016 (KB3177467) Takes forever to Search for updates on
my PC. After an hour watching the progress bar I pressed the Cancel
button to no avail; the progress bar still keeps going as before.
BTW, what does a stack mean in this context? I know what it means for
programmers (a last-in, first-out memory buffer) but that does not apply
here, I guess.

cameo wrote:
On 11/25/2016 4:13 AM, John K.Eason wrote:
In article , lid (cameo)
wrote:

*From:* cameo
*Date:* Fri, 25 Nov 2016 00:29:42 -0800

Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit
Edition

I wonder if the Win7 software module that processes these MS
updates is perhaps corrupted, but I would not know how to refresh
that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.

Follow http://wu.krelay.de/en/ and see if that gets things running
again.

This German method sounds much simpler than what Paul suggested (and is
way over my head,) but even here the downloaded Win7 x64 Servicing Stack
Update for Sep 2016 (KB3177467) Takes forever to Search for updates on
my PC. After an hour watching the progress bar I pressed the Cancel
button to no avail; the progress bar still keeps going as before.
BTW, what does a stack mean in this context? I know what it means for
programmers (a last-in, first-out memory buffer) but that does not apply
here, I guess.


The following applies, if you have a .msu file in
hand, and it is taking forever to install. It's
basically stuck, talking to wuauserv...

1) Unplug the network cable.
2) Reboot.
3) Try to install KB3177467 using your .msu file.
It should work.
4) Now, plug the network cable back in.

If you have a Wifi router for the machine, just
power off the router, then start at Step 2
and reboot with no network present.

This recipe is simpler than some recipe
involving administrator command prompt, and
typing stuff in there. Some people hate stuff
like that :-)

*******

I don't have an official definition of Servicing Stack,
except to say:

1) Can thwart pirates.
2) Prepares OS for next set of updates or upgrades.

The OS has WinSXS folder, which is used for Component Based Servicing.
That's where all these patches are stored, as individual
notarized system files. Each one is named to indicate its
version. Those are hard linked into the Windows folder
and the name is changed to a shorter name when doing so.
"Servicing" the computer then, refers to CBS and
working with that folder of stuff.

But as to whether the Servicing Stack changes are focused
on some specific folder or set of files (i.e. control info),
I don't know the details.

Paul

On 12/1/2016 7:02 PM, Paul wrote:
cameo wrote:
On 11/25/2016 4:13 AM, John K.Eason wrote:
In article , lid (cameo)
wrote:

*From:* cameo
*Date:* Fri, 25 Nov 2016 00:29:42 -0800

Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit
Edition

I wonder if the Win7 software module that processes these MS
updates is perhaps corrupted, but I would not know how to refresh
that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.

Follow http://wu.krelay.de/en/ and see if that gets things running
again.

This German method sounds much simpler than what Paul suggested (and
is way over my head,) but even here the downloaded Win7 x64 Servicing
Stack Update for Sep 2016 (KB3177467) Takes forever to Search for
updates on my PC. After an hour watching the progress bar I pressed
the Cancel button to no avail; the progress bar still keeps going as
before.
BTW, what does a stack mean in this context? I know what it means for
programmers (a last-in, first-out memory buffer) but that does not
apply here, I guess.


The following applies, if you have a .msu file in
hand, and it is taking forever to install. It's
basically stuck, talking to wuauserv...

1) Unplug the network cable.
2) Reboot.
3) Try to install KB3177467 using your .msu file.
It should work.
4) Now, plug the network cable back in.

If you have a Wifi router for the machine, just
power off the router, then start at Step 2
and reboot with no network present.

This recipe is simpler than some recipe
involving administrator command prompt, and
typing stuff in there. Some people hate stuff
like that :-)

Doggone it, it worked! So thanks, but now I'm not sure what's the safest
way to catch up with all the missed updates.

cameo wrote:
On 12/1/2016 7:02 PM, Paul wrote:
cameo wrote:
On 11/25/2016 4:13 AM, John K.Eason wrote:
In article , lid (cameo)
wrote:

*From:* cameo
*Date:* Fri, 25 Nov 2016 00:29:42 -0800

Except for Security Essential virus DB updates, I have not received
any other Win7 updates since the end of June. Two important updates
that I did receive since then could not be installed:

Update for Microsoft Silverlight (KB3162593) and
Definition Update for Microsoft Office 2010 (KB3115321) 32-Bit
Edition

I wonder if the Win7 software module that processes these MS
updates is perhaps corrupted, but I would not know how to refresh
that one.

I must say that even the Security Essential updates are not always
successful through the Update function of the program itself, so I
tend bypass the program and use the manual method (mpam-fe.exe).

Can anybody give me some pointers on this issue?
Thanks.

Follow http://wu.krelay.de/en/ and see if that gets things running
again.

This German method sounds much simpler than what Paul suggested (and
is way over my head,) but even here the downloaded Win7 x64 Servicing
Stack Update for Sep 2016 (KB3177467) Takes forever to Search for
updates on my PC. After an hour watching the progress bar I pressed
the Cancel button to no avail; the progress bar still keeps going as
before.
BTW, what does a stack mean in this context? I know what it means for
programmers (a last-in, first-out memory buffer) but that does not
apply here, I guess.


The following applies, if you have a .msu file in
hand, and it is taking forever to install. It's
basically stuck, talking to wuauserv...

1) Unplug the network cable.
2) Reboot.
3) Try to install KB3177467 using your .msu file.
It should work.
4) Now, plug the network cable back in.

If you have a Wifi router for the machine, just
power off the router, then start at Step 2
and reboot with no network present.

This recipe is simpler than some recipe
involving administrator command prompt, and
typing stuff in there. Some people hate stuff
like that :-)

Doggone it, it worked! So thanks, but now I'm not sure what's the safest
way to catch up with all the missed updates.

You mean Windows Update is actually listing your
missing updates now ?

If so, that would be a miracle.

If WU works, you count how many.

If the number is small, you review them one at a time.

If the number is large, you take up another hobby :-)

I spent around *25 working hours* patching
computers here in September. Then shutting off
Windows Update again. Just to give you some idea
how much effort it takes to review what
you are installing. I don't have a particular
reason to install Cumulative Monthly updates.
But maybe you'll like them, and you trust
Microsoft for some reason. My level of trust
in this business is pretty low, and I don't
even wear a tinfoil hat. The whole thing is
an unnecessary make-work project for end-users,
and I disapprove of the mess that has been made.

Paul