Can't install 3 stubborn Windows Updates

Hi folks,

I seem to be stuck in a loop when it comes to installing 3 Windows Updates.

(Running a 64-bit PC with 16GB RAM, Windows 10 Home 1703 15063.608)

The 3 culprits are all 32-bit if that could be part of the problem, but here
they a

KB3128030 PowerPoint Viewer 2010 (Important)
KB4011055 Office 2010 (Important)
KB3213621 Office 2010 (Critical)

When I try installing them, I get the following under "Update Status":

"We can't install some updates because other updates are in progress.
Restarting your computer may help, and we'll keep trying to update."

--------
[Retry]
--------

This has been going on for several days now, I've rebooted many times
and even tried the emptying/deleting of the "SoftwareDistribution" contents
as discussed in another thread here. Nothing seems to solve the mystery.

I know it's not a huge problem, but I'd like to get it straightened out if
possible.
As always, any help/advice/suggestion is always appreciated!!


Neil ¦¬D
--

Neil Turkenkopf wrote:
Hi folks,

I seem to be stuck in a loop when it comes to installing 3 Windows Updates.

(Running a 64-bit PC with 16GB RAM, Windows 10 Home 1703 15063.608)

The 3 culprits are all 32-bit if that could be part of the problem, but here
they a

KB3128030 PowerPoint Viewer 2010 (Important)
KB4011055 Office 2010 (Important)
KB3213621 Office 2010 (Critical)

When I try installing them, I get the following under "Update Status":

"We can't install some updates because other updates are in progress.
Restarting your computer may help, and we'll keep trying to update."

--------
[Retry]
--------

This has been going on for several days now, I've rebooted many times
and even tried the emptying/deleting of the "SoftwareDistribution" contents
as discussed in another thread here. Nothing seems to solve the mystery.

I know it's not a huge problem, but I'd like to get it straightened out if
possible.
As always, any help/advice/suggestion is always appreciated!!


Neil ¦¬D

The message you saw is usually correctable by following the advice that Paul
provided(stop Windows services, delete the Software Distribution Downloads
folder, restart the machine and run Windows Update manually to check for
updates and re-attempt to install them. If the same error occurs, download
the offline installers for those KB's from the MSFT Catalog, repeat the stop
Services method, delete that same folder, restart the device, log on
disconnect from the internet and attempt to manually install using the
downloaded KB exe files.

If it still fails, then consider the DISM method for analyzing and repairing
a corrupted component store. DISM is run in an elevated/Admin Command prompt
or Power Shell) to CheckHealth, ScanHealth. If DISM reports the component
store is corrupted(and repairable) then use the DISM RestoreHealth optino.

https://www.tenforums.com/tutorials/...-10-image.html

Note: If using the DISM command to point to(as indicated in the article)
media(Windows 10 on DVD or USB)good files to repair a corrupted component
store it might be good idea to verify your media has an install.wim file
instead of the install.esd file(the install.esd file has been known to fail)
Ensure your Win10 media is same version(e.g. 1703) as the installed
version of Windows 10.

If DISM /RestoreHealth fails(can't fix, can't find or use the source) then
you may have to restore using a prior image to a known good Windows 10
system free of Windows Update problems and component store corruption.

If none of the above fixes the issue, your other(few and more brutal)options
may be to:
- wait until next month for the next cumulative update
- Refresh or Reset Windows 10
- Clean Install Windows 10



--
...winston
msft mvp windows experience 2007-2016, insider mvp 2016-2018

Neil Turkenkopf wrote:
Hi folks,

I seem to be stuck in a loop when it comes to installing 3 Windows Updates.

(Running a 64-bit PC with 16GB RAM, Windows 10 Home 1703 15063.608)

The 3 culprits are all 32-bit if that could be part of the problem, but
here they a

KB3128030 PowerPoint Viewer 2010 (Important)
KB4011055 Office 2010 (Important)
KB3213621 Office 2010 (Critical)

When I try installing them, I get the following under "Update Status":

"We can't install some updates because other updates are in progress.
Restarting your computer may help, and we'll keep trying to update."

--------
[Retry]
--------

This has been going on for several days now, I've rebooted many times
and even tried the emptying/deleting of the "SoftwareDistribution" contents
as discussed in another thread here. Nothing seems to solve the mystery.

I know it's not a huge problem, but I'd like to get it straightened out
if possible.
As always, any help/advice/suggestion is always appreciated!!


Neil ¦¬D

Fixing this stuff, isn't an exact science. It would be, if
there was a status panel saying what it was actually doing at the moment :-)
Like, what update it thinks is "in motion".

I would go to Settings (gear wheel) and find the Windows Update panel.
Then, check the Windows Update "history" page in there. There is a link
to the install history on that page. You shouldn't have to look too
far, as 15063.608 update (Patch Tuesday?) just came in recently, and
it wouldn't have worked if things were jammed up at that point.

You want to see what kind of failure messages are in there,
from just before this stuff started to happen.

If it was really stuck, you'd see it trying to get Windows Defender
updates too.

The updates can be downloaded individually. I can't really give
a good picture of what you can expect to find in here. Some items
I've fetched from here, needed some unique search terms to get.
In this case, I can see the PPTViewer is available for download,
using nothing but the KB number as a search term.

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

After reviewing the history, try to download the ones that failed
and never succeeded, as well as the three in your list. Disconnect
the network cable and reboot. Leave the network cable disconnected
while you install the .msu files you downloaded. (Leaving the
network cable disconnected, is to prevent wuauserv from working
on updates automatically, while you're trying to massage the
updates manually. Reboot with the cable disconnected so wuauserv
will be "waiting on you".)

Dealing with the SoftwareDistribution folder at this point in time,
may help it forget about any "updates in motion", so that may still
be required (with network cable disconnected), to get the files
to install.

Some updates, Microsoft makes it a real chore to figure out which file
to use. I've seen as many as ten links in a single download item,
some called "Delta" for delta update method, some are just regular
..msu files. And your job is to, as best you can, pick the regular one.
I cannot narrow it down much more than that. The .msu contains
sufficient info, to figure out whether the file is "valid" for
your setup or not. It won't break the machine. That might be
different, if you dabbled in driver files. I'm sure if you
try hard enough, you'd eventually break something (touchpad filter
driver) :-) But for the most part, the thing is defensively designed,
and isn't an instant disaster area.

If you rely on Microsoft to fix it, you'll be waiting a long
long time. I had some redist libraries (PPTViewer actually
uses some), that the patch got into a loop and they tried
to re-install themselves over and over again. And it took
quite a while for MS to fix it.

And PPTViewer is considered to be a part of Office, which
is why there are two "Office" patches as well.

When I used MBSA 2.3 Baseline Security Analyzer, some years
ago on WinXP, I think the three "free Office Viewer tools"
had a total of 15 patches against them. To give some idea
just how much of a nuisance those can be. And a fair number
of the patches would be VCRedist, as well as patches for
the main code.

The .msu status messages can be a bit deceiving. If you
try to load a 32bit OS patch on a 64bit OS, it'll give
a "this update is not for this..." type error. Yet, if
a Servicing Stack update is missing (a dependency), it
can give the same error. When an update fails, you can
try Googling the KB number, and see if anyone has
noticed a dependency. In the case I had, I don't know
if the Servicing Stack patch was in the list of things
it wanted to update or not. But I found advice as to
which prerequisite I needed to install first for that
one. That should not happen to you in your case, as your
patches are in the "Office orbit".

Paul

". . .winston" wrote in message news
Neil Turkenkopf wrote:
Hi folks,

I seem to be stuck in a loop when it comes to installing 3 Windows
Updates.

(Running a 64-bit PC with 16GB RAM, Windows 10 Home 1703 15063.608)

The 3 culprits are all 32-bit if that could be part of the problem, but
here
they a

KB3128030 PowerPoint Viewer 2010 (Important)
KB4011055 Office 2010 (Important)
KB3213621 Office 2010 (Critical)

When I try installing them, I get the following under "Update Status":

"We can't install some updates because other updates are in progress.
Restarting your computer may help, and we'll keep trying to update."

--------
[Retry]
--------

This has been going on for several days now, I've rebooted many times
and even tried the emptying/deleting of the "SoftwareDistribution"
contents
as discussed in another thread here. Nothing seems to solve the mystery.

I know it's not a huge problem, but I'd like to get it straightened out if
possible.
As always, any help/advice/suggestion is always appreciated!!


Neil ¦¬D
===========================

The message you saw is usually correctable by following the advice that Paul
provided(stop Windows services, delete the Software Distribution Downloads
folder, restart the machine and run Windows Update manually to check for
updates and re-attempt to install them. If the same error occurs, download
the offline installers for those KB's from the MSFT Catalog, repeat the stop
Services method, delete that same folder, restart the device, log on
disconnect from the internet and attempt to manually install using the
downloaded KB exe files.

If it still fails, then consider the DISM method for analyzing and repairing
a corrupted component store. DISM is run in an elevated/Admin Command prompt
or Power Shell) to CheckHealth, ScanHealth. If DISM reports the component
store is corrupted(and repairable) then use the DISM RestoreHealth optino.

https://www.tenforums.com/tutorials/...-10-image.html

Note: If using the DISM command to point to(as indicated in the article)
media(Windows 10 on DVD or USB)good files to repair a corrupted component
store it might be good idea to verify your media has an install.wim file
instead of the install.esd file(the install.esd file has been known to fail)
Ensure your Win10 media is same version(e.g. 1703) as the installed
version of Windows 10.

If DISM /RestoreHealth fails(can't fix, can't find or use the source) then
you may have to restore using a prior image to a known good Windows 10
system free of Windows Update problems and component store corruption.

If none of the above fixes the issue, your other(few and more brutal)options
may be to:
- wait until next month for the next cumulative update
- Refresh or Reset Windows 10
- Clean Install Windows 10
--
...winston
msft mvp windows experience 2007-2016, insider mvp 2016-2018
================================================== =========

Hi Winston!

That's a lot of info for me to digest, so I think I'm just going to take one
of
your last options and "wait until next month for the next cumulative
update".

As always, thanks for your help!
Neil ¦¬D
--

"Paul" wrote in message news
Neil Turkenkopf wrote:
Hi folks,

I seem to be stuck in a loop when it comes to installing 3 Windows
Updates.

(Running a 64-bit PC with 16GB RAM, Windows 10 Home 1703 15063.608)

The 3 culprits are all 32-bit if that could be part of the problem, but
here they a

KB3128030 PowerPoint Viewer 2010 (Important)
KB4011055 Office 2010 (Important)
KB3213621 Office 2010 (Critical)

When I try installing them, I get the following under "Update Status":

"We can't install some updates because other updates are in progress.
Restarting your computer may help, and we'll keep trying to update."

--------
[Retry]
--------

This has been going on for several days now, I've rebooted many times
and even tried the emptying/deleting of the "SoftwareDistribution"
contents
as discussed in another thread here. Nothing seems to solve the mystery.

I know it's not a huge problem, but I'd like to get it straightened out if
possible.
As always, any help/advice/suggestion is always appreciated!!


Neil ¦¬D

================================================== ====

Fixing this stuff, isn't an exact science. It would be, if
there was a status panel saying what it was actually doing at the moment :-)
Like, what update it thinks is "in motion".

I would go to Settings (gear wheel) and find the Windows Update panel.
Then, check the Windows Update "history" page in there. There is a link
to the install history on that page. You shouldn't have to look too
far, as 15063.608 update (Patch Tuesday?) just came in recently, and
it wouldn't have worked if things were jammed up at that point.

You want to see what kind of failure messages are in there,
from just before this stuff started to happen.

If it was really stuck, you'd see it trying to get Windows Defender
updates too.

The updates can be downloaded individually. I can't really give
a good picture of what you can expect to find in here. Some items
I've fetched from here, needed some unique search terms to get.
In this case, I can see the PPTViewer is available for download,
using nothing but the KB number as a search term.

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

After reviewing the history, try to download the ones that failed
and never succeeded, as well as the three in your list. Disconnect
the network cable and reboot. Leave the network cable disconnected
while you install the .msu files you downloaded. (Leaving the
network cable disconnected, is to prevent wuauserv from working
on updates automatically, while you're trying to massage the
updates manually. Reboot with the cable disconnected so wuauserv
will be "waiting on you".)

Dealing with the SoftwareDistribution folder at this point in time,
may help it forget about any "updates in motion", so that may still
be required (with network cable disconnected), to get the files
to install.

Some updates, Microsoft makes it a real chore to figure out which file
to use. I've seen as many as ten links in a single download item,
some called "Delta" for delta update method, some are just regular
..msu files. And your job is to, as best you can, pick the regular one.
I cannot narrow it down much more than that. The .msu contains
sufficient info, to figure out whether the file is "valid" for
your setup or not. It won't break the machine. That might be
different, if you dabbled in driver files. I'm sure if you
try hard enough, you'd eventually break something (touchpad filter
driver) :-) But for the most part, the thing is defensively designed,
and isn't an instant disaster area.

If you rely on Microsoft to fix it, you'll be waiting a long
long time. I had some redist libraries (PPTViewer actually
uses some), that the patch got into a loop and they tried
to re-install themselves over and over again. And it took
quite a while for MS to fix it.

And PPTViewer is considered to be a part of Office, which
is why there are two "Office" patches as well.

When I used MBSA 2.3 Baseline Security Analyzer, some years
ago on WinXP, I think the three "free Office Viewer tools"
had a total of 15 patches against them. To give some idea
just how much of a nuisance those can be. And a fair number
of the patches would be VCRedist, as well as patches for
the main code.

The .msu status messages can be a bit deceiving. If you
try to load a 32bit OS patch on a 64bit OS, it'll give
a "this update is not for this..." type error. Yet, if
a Servicing Stack update is missing (a dependency), it
can give the same error. When an update fails, you can
try Googling the KB number, and see if anyone has
noticed a dependency. In the case I had, I don't know
if the Servicing Stack patch was in the list of things
it wanted to update or not. But I found advice as to
which prerequisite I needed to install first for that
one. That should not happen to you in your case, as your
patches are in the "Office orbit".

Paul
================================================== ====

Hi Paul!

As I just said to Winston regarding his reply, you both have given me
*lots* of info to ponder and tinker with! Since it doesn't seem to be
an urgent matter, I think I'm just going to wait for the next bus and
see what happens. g

Thanks very much for your help!
Neil ¦¬D
--

Neil Turkenkopf wrote:


Hi Paul!

As I just said to Winston regarding his reply, you both have given me
*lots* of info to ponder and tinker with! Since it doesn't seem to be
an urgent matter, I think I'm just going to wait for the next bus and
see what happens. g

Thanks very much for your help!
Neil ¦¬D

Now this sounds like a practical answer, but...

Microsoft just doesn't fix these in as timely a fashion
as I would like. When they broke my webcam in Win10, it
took maybe three months for them to fix it (and I'd given
up even checking any more at that point). I'm as lazy as the
next person, but nagging stuff like this gets on my
nerves, and sooner or later, I'll be fixing it.

Paul

Neil Turkenkopf wrote:

Hi Winston!

That's a lot of info for me to digest, so I think I'm just
going to take one of your last options and "wait until
next month for the next cumulative update".

As always, thanks for your help!


The message "We can't install some updates because other updates are in
progress. Restarting your computer may help, and we'll keep trying to
update." is more important and takes precedent over the Office updates
failure to install.

It indicates an issue occurring with Windows Update from the current attempt
or prior installed update, thus the suggestion to use the DISM tool in an
elevated command prompt to rule out a corruption in the component store. If
the issue centers on a problem with the component store or Windows Update,
the next update could very well have the same issue, thus waiting might not
be a solution.

At this stage if you do decide to wait..at least use the DISM command to
CheckHealth or ScanHealth.

Open Command in an elevated prompt(Run as Administrator) and cut and paste
the following after cursor. Should take a few seconds.
Dism /Online /Cleanup-Image /CheckHealth

Once the above is done, repeat again with the following. Could take a few
minutes to complete.
Dism /Online /Cleanup-Image /ScanHealth


Report the results.

--
...winston
msft mvp windows experience 2007-2016, insider mvp 2016-2018

--
". . .winston" wrote in message news
Neil Turkenkopf wrote:

Hi Winston!

That's a lot of info for me to digest, so I think I'm just
going to take one of your last options and "wait until
next month for the next cumulative update".

As always, thanks for your help!

=======================================
The message "We can't install some updates because other updates are in
progress. Restarting your computer may help, and we'll keep trying to
update." is more important and takes precedent over the Office updates
failure to install.

It indicates an issue occurring with Windows Update from the current attempt
or prior installed update, thus the suggestion to use the DISM tool in an
elevated command prompt to rule out a corruption in the component store. If
the issue centers on a problem with the component store or Windows Update,
the next update could very well have the same issue, thus waiting might not
be a solution.

At this stage if you do decide to wait..at least use the DISM command to
CheckHealth or ScanHealth.

Open Command in an elevated prompt(Run as Administrator) and cut and paste
the following after cursor. Should take a few seconds.
Dism /Online /Cleanup-Image /CheckHealth

Once the above is done, repeat again with the following. Could take a few
minutes to complete.
Dism /Online /Cleanup-Image /ScanHealth


Report the results.

--
...winston
msft mvp windows experience 2007-2016, insider mvp 2016-2018
================================================== ======

Hi Winston!

The CheckHealth came back with:
"No component store corruption detected.
The operation completed successfully."

The ScanHealth however said:
"The component store is repairable.
The operation completed successfully."

SO... what/where is this "component store"
and how do I repair it?

"Paul" wrote in message news
Neil Turkenkopf wrote:


Hi Paul!

As I just said to Winston regarding his reply, you both have given me
*lots* of info to ponder and tinker with! Since it doesn't seem to be
an urgent matter, I think I'm just going to wait for the next bus and
see what happens. g

Thanks very much for your help!
Neil ¦¬D
=======================================
Now this sounds like a practical answer, but...

Microsoft just doesn't fix these in as timely a fashion
as I would like. When they broke my webcam in Win10, it
took maybe three months for them to fix it (and I'd given
up even checking any more at that point). I'm as lazy as the
next person, but nagging stuff like this gets on my
nerves, and sooner or later, I'll be fixing it.

Paul
=========================================

Hi Paul!

I agree, and as I just replied to Winston, there is
definitely a problem with my "component store".

Now the question is, how do I repair it?

Neil Turkenkopf wrote:
"Paul" wrote in message news
Neil Turkenkopf wrote:


Hi Paul!

As I just said to Winston regarding his reply, you both have given me
*lots* of info to ponder and tinker with! Since it doesn't seem to be
an urgent matter, I think I'm just going to wait for the next bus and
see what happens. g

Thanks very much for your help!
Neil ¦¬D
=======================================
Now this sounds like a practical answer, but...

Microsoft just doesn't fix these in as timely a fashion
as I would like. When they broke my webcam in Win10, it
took maybe three months for them to fix it (and I'd given
up even checking any more at that point). I'm as lazy as the
next person, but nagging stuff like this gets on my
nerves, and sooner or later, I'll be fixing it.

Paul
=========================================

Hi Paul!

I agree, and as I just replied to Winston, there is
definitely a problem with my "component store".

Now the question is, how do I repair it?

You run the DISM commands as administrator (like, in an administrator
command prompt). The following description is stored
in my notes file, for later usage...

*******

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

/CheckHealth - This switch option only checks to see if a component
corruption marker is already present in the registry.
It is just a quick way to see if corruption currently
exists, and to inform you if there is corruption. It
does not fix anything or create a log.
This should be finished almost instantaneous.

/ScanHealth - This switch option does not fix any corruption.
It only checks for component store corruption and records
that corruption to the log file.

This is useful for only logging what, if any, corruption
exists. This should take around 5-10 minutes to finish.

/RestoreHealth - This switch option checks for component store corruption,
records the corruption to the log file, and FIXES the
image corruption using Windows Update. This should take
around 10-15 minutes up to a few hours to finish depending
on the level of corruption.

*******

And before getting too excited about your discovery,
note that some "damage" in WinSXS, is actually mistakes made
by Microsoft. For example, there were a couple HTML files that
should not have been included in the coverage of the tool,
that report they are corrupted. When it's just a mistake and
nothing to do with actual operation of the computer. If some
actual EXE or DLL files got repaired, that would be news indeed.

C:\Windows\Logs\DISM\dism.log

Whereas sfc /scannow, dumps in CBS.log.
CBS.log can be a big file, and using findstr can filter for
just certain lines of it.

https://support.microsoft.com/en-ca/...indows-resourc

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

HTH,
Paul

"Paul" wrote in message news
Neil Turkenkopf wrote:
"Paul" wrote in message news
Neil Turkenkopf wrote:


Hi Paul!

As I just said to Winston regarding his reply, you both have given me
*lots* of info to ponder and tinker with! Since it doesn't seem to be
an urgent matter, I think I'm just going to wait for the next bus and
see what happens. g

Thanks very much for your help!
Neil ¦¬D
=======================================
Now this sounds like a practical answer, but...

Microsoft just doesn't fix these in as timely a fashion
as I would like. When they broke my webcam in Win10, it
took maybe three months for them to fix it (and I'd given
up even checking any more at that point). I'm as lazy as the
next person, but nagging stuff like this gets on my
nerves, and sooner or later, I'll be fixing it.

Paul
=========================================

Hi Paul!

I agree, and as I just replied to Winston, there is
definitely a problem with my "component store".

Now the question is, how do I repair it?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^

You run the DISM commands as administrator (like, in an administrator
command prompt). The following description is stored
in my notes file, for later usage...

*******

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

/CheckHealth - This switch option only checks to see if a component
corruption marker is already present in the registry.
It is just a quick way to see if corruption currently
exists, and to inform you if there is corruption. It
does not fix anything or create a log.
This should be finished almost instantaneous.

/ScanHealth - This switch option does not fix any corruption.
It only checks for component store corruption and records
that corruption to the log file.

This is useful for only logging what, if any, corruption
exists. This should take around 5-10 minutes to finish.

/RestoreHealth - This switch option checks for component store corruption,
records the corruption to the log file, and FIXES the
image corruption using Windows Update. This should take
around 10-15 minutes up to a few hours to finish depending
on the level of corruption.

*******

And before getting too excited about your discovery,
note that some "damage" in WinSXS, is actually mistakes made
by Microsoft. For example, there were a couple HTML files that
should not have been included in the coverage of the tool,
that report they are corrupted. When it's just a mistake and
nothing to do with actual operation of the computer. If some
actual EXE or DLL files got repaired, that would be news indeed.

C:\Windows\Logs\DISM\dism.log

Whereas sfc /scannow, dumps in CBS.log.
CBS.log can be a big file, and using findstr can filter for
just certain lines of it.

https://support.microsoft.com/en-ca/...indows-resourc

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log

HTH,
Paul
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Hi Paul!

I ran all 3 , and I'm happy to report that there is NO corruption.

I even rebooted, but I'm still stuck in the same Windows Update loop
regarding KB3128030, KB4011055, KB3213631. Occasionally there is a 4th one
for Defender, but I forgot to write it down. The only other thing to try
that I can think of is System Restore, do you think that's a good idea, too
drastic, etc.?

Neil Turkenkopf wrote:


Hi Paul!

I ran all 3 , and I'm happy to report that there is NO corruption.

I even rebooted, but I'm still stuck in the same Windows Update loop
regarding KB3128030, KB4011055, KB3213631. Occasionally there is a 4th
one for Defender, but I forgot to write it down. The only other thing to
try that I can think of is System Restore, do you think that's a good
idea, too drastic, etc.?

You already tried deleting SoftwareDistribution.

In control panels, there is a Troubleshooter control panel,
which should have an item for debugging "update". You can use the search
box, to enter terms to make a prospective troubleshooter show up.
The troubleshooter does the same thing as the TenForums script
does.

If I was there, what I'd be trying next is:

1) catalog.update.microsoft.com - enter the KB numbers, download the
.msu file for each update.

2) Now, unplug the network cable.

3) Reboot. Install the .msu files one at a time. Don't select
"restart now" if it is offered at the bottom of the dialog.
You should be able to install all three, and then reboot.

Can it "be in the middle of an update" when SoftwareDistribution
is completely empty ? Dunno. I hope not.

I've had pretty good luck with manually installing updates
from the "catalog" server. I reserve the Whack-A-Mole
"delete the entire SoftwareDistribution folder" for my
two copies of Win10 Insider. It's my favorite technique
for kicking ass there. I don't normally need that
for the Release stream. A little coaxing, to get a
"jammed" update installed with a downloaded "catalog"
server file, is enough.

Win10 has "shades of the wuauserv" problem, but it
doesn't manifest quite as badly as in the other Windows
versions. Unplugging the network cable, is sufficient
to keep wuauserv responsive after a reboot, such
that double clicking a .msu you downloaded, works.

And those Defender updates are a damn nuisance. It's
yet another reason to unplug the network cable when
attempting to resuscitate the thing.

Paul

"Paul" wrote in message news
Neil Turkenkopf wrote:


Hi Paul!

I ran all 3 , and I'm happy to report that there is NO corruption.

I even rebooted, but I'm still stuck in the same Windows Update loop
regarding KB3128030, KB4011055, KB3213631. Occasionally there is a 4th one
for Defender, but I forgot to write it down. The only other thing to try
that I can think of is System Restore, do you think that's a good idea,
too drastic, etc.?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^

You already tried deleting SoftwareDistribution.

In control panels, there is a Troubleshooter control panel,
which should have an item for debugging "update". You can use the search
box, to enter terms to make a prospective troubleshooter show up.
The troubleshooter does the same thing as the TenForums script
does.

If I was there, what I'd be trying next is:

1) catalog.update.microsoft.com - enter the KB numbers, download the
.msu file for each update.

2) Now, unplug the network cable.

3) Reboot. Install the .msu files one at a time. Don't select
"restart now" if it is offered at the bottom of the dialog.
You should be able to install all three, and then reboot.

Can it "be in the middle of an update" when SoftwareDistribution
is completely empty ? Dunno. I hope not.

I've had pretty good luck with manually installing updates
from the "catalog" server. I reserve the Whack-A-Mole
"delete the entire SoftwareDistribution folder" for my
two copies of Win10 Insider. It's my favorite technique
for kicking ass there. I don't normally need that
for the Release stream. A little coaxing, to get a
"jammed" update installed with a downloaded "catalog"
server file, is enough.

Win10 has "shades of the wuauserv" problem, but it
doesn't manifest quite as badly as in the other Windows
versions. Unplugging the network cable, is sufficient
to keep wuauserv responsive after a reboot, such
that double clicking a .msu you downloaded, works.

And those Defender updates are a damn nuisance. It's
yet another reason to unplug the network cable when
attempting to resuscitate the thing.

Paul
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv vvvvvvv

SUCCESS!! :-D

Unplugging the network cable did the trick! (Who knew?)

I *never* would have thought of that on my own (I'm not sure how 'you' even
figured that one out) but it makes sense now.
One other oddity - I wasn't able to install (or uninstall) anything at all
because I kept getting the "Another installation is in progress. Please
complete, etc."
I didn't have anything else installing or uninstalling of course, so I
checked another thread and discovered that Stopping the Windows Installer
was the fix.
It was, it did, and all 3 of those stubborn updates finally installed for
good. Now I have the nice green checkmark saying "My device is up to date."

I can't thank you enough Paul, you really took the time & effort to help me
fix my problem!
(I hope that by reading this thread, someone else down the road might
benefit by it too.)

Thanks again!!
(Happy guy) Neil ¦¬D
--

Neil Turkenkopf wrote:


SUCCESS!! :-D

Unplugging the network cable did the trick! (Who knew?)

I *never* would have thought of that on my own (I'm not sure how 'you'
even figured that one out) but it makes sense now.
One other oddity - I wasn't able to install (or uninstall) anything at
all because I kept getting the "Another installation is in progress.
Please complete, etc."
I didn't have anything else installing or uninstalling of course, so I
checked another thread and discovered that Stopping the Windows
Installer was the fix.
It was, it did, and all 3 of those stubborn updates finally installed
for good. Now I have the nice green checkmark saying "My device is up to
date."

I can't thank you enough Paul, you really took the time & effort to help
me fix my problem!
(I hope that by reading this thread, someone else down the road might
benefit by it too.)

Thanks again!!
(Happy guy) Neil ¦¬D

I learned this trick, working on older problems.

Like getting WSUSOffline installer to work.

Same looping wuauserv problem. Same solution.
Pull network cable. Reboot. Start WsusOffline.

The poor design of wuauserv exists in WinXP/Vista/W7/W8/W8.1/W10.
I've had a lot of practice.

Paul