fails to install KB2872339

[gcon60]

Fails 8024200D.
This has been going on for a couple of months. Tried everything. All I want is a definitive answer - a bit optimistic I know.
Gerard

 

[Vic 40]

Did you look if the update already is installed?

You can find these on the left side next to the programs that are installed on your pc=configuration panel->programs->programs and parts (?)->left side ->show installed updates.
If it is you can "hide" the update by rightclicking it and choose hide.

Did you use the "System Update Readiness Tool" to try and fix this problem? Google this one.

 

[gcon60]

Checked and it is not listed under installed updates.

 

[Vic 40]

No answer on this one? Did you try it?

Did you use the "System Update Readiness Tool" to try and fix this problem? Google this one.

 

[gcon60]

Yes, that and everything else that was suggested.

 

[Vic 40]

Did you try it manually? Could be done via the next,
http://www.microsoft.com/en-us/download/details.aspx?id=40068

 

[gcon60]

Interesting; I downloaded it and manually tried to install it. The result was a message saying that it was already installed on my computer. I check the installed patches again and it is definitely not shown as installed. I checked the install history and every incident of this update is recorded as a failure. ???

 

[gcon60]

I have another update that has been failing along with the above. I downloaded this and tried to update. The message this time was that this is not applicable to this computer.

So, one is already installed and the other one doesn't count. Instead if failing it would be easier to let me know the real reasons for the failures, or is that too much for Microsoft?

Thanks for the hint about trying it manually - solved my problem.

GREAT!!!

 

[Vic 40]

I also found the next which in the end gives the recommendation to ignore the update or hide it,
http://news.softpedia.com/news/Windows-7-KB2872339-Update-Still-Stuck-in-Installation-Loop-384980.shtml

 

[gcon60]

"Botched updates", I couldn't have put it better myself. Not so sure MS is working to resolve the problem.

Thanks.