Test draft copy of forum answers associated with lates XP updates issues

http://www.eileenslounge.com/viewtop...249846#p249846
https://social.technet.microsoft.com...eitproprevious
https://tinyurl.com/t73r3pg
https://social.technet.microsoft.com...?forum=outlook
( ( Locked Threads:
https://answers.microsoft.com/en-us/...lc=1031&page=6
https://answers.microsoft.com/en-us/...fb63739&page=4
https://answers.microsoft.com/en-us/...16500c3?page=1
https://answers.microsoft.com/en-us/...2-7df17e82fb3d )
 )

I just finished unwrapping my Xmas present from Microsoft. It took me a couple of days. Despite having automatic updates disabled, occasionally a massive amount of updates still come down unexpectedly. It does not happen very often. I think theoretically it should never happen. But it does.

So one of my XP machines got the present.
I do have an extensive library of known "good and bad" Updates, and coding to sort through and compare them etc.. That usually helps identify the culprits. This time it only saw the old favourites that Microsoft like to send to cripple Active X controls, but never the less my XP was crippled by the issues discussed in this Thread.

I did identify some new updates that I had not seen before, but de installing them did not solve the problem , at least initially. After a lot of painstaking manual de installing and re installing updates I sorted the problem out…

It was very strange this time. By removing recent updates, I noticed that other updates suddenly appeared in the update this. They were not visible before. After removing some of those , the XP problem was solved. Furthermore I could re install most of the updated which I had originbally removed and still the XP problem does not return

Just to explain that again: In order to find the killer updates, you first have to de install some non offending updates. Only then do the killer updates show so that you can de install them. (A few other harmless updates may also suddenly appear). Then you can put the others back, if you like.

So finally below is the current list, with the recent ones at the bottom

If you don't find those,
or
you find some, de install them,
and still have the problem,
then try de installing a few other recent updates and then look at your update list again . If you then see any of the bad updates , then de install them. If that cures the problem then you may be able to re install some of the others you de installed without getting the problem.

In actual fact in my recent case, following the procedure that I have described, I now have all the updates that were showing after the unwanted Xmas present, and a few more, but I no longer have the problem, because I have de installed some of the bad updates, which were initially not showing after the unwanted present. Crazy situation!

Current Killer List
KB4461522 ( no longer available )
KB4461614 ( available , but not been offered for some time )
KB4462157 ( available , but not been offered for some time. ( Originally this was introduced to solve the problem. It never did. Quite the opposite: If you have the problem, then installing this update has no effect; but if you do not have the problem , and you instal this update, it causes the problem, just as all the other "killers do !!. ) )
KB4462174 ( available, and until recently, was still offered )
KB4462223
KB4464566 Probably the most recent killer
The last two may be hidden , and you may need to go through the steps I described to find them. Unfortunately I still have not figured out how to automate messing around with Office updates in XP ( I can do it with most everything else ). So you will need a few days to unwrap your present if you get one…




(P.s. Microsoft have locked some Threads on this, making it difficult to update people on the problem. But a few new Threads have also been started)

Ref:
https://social.technet.microsoft.com...eitproprevious
https://tinyurl.com/t73r3pg
https://social.technet.microsoft.com...?forum=outlook
Locked Threads:
https://answers.microsoft.com/en-us/...lc=1031&page=6
https://answers.microsoft.com/en-us/...fb63739&page=4
https://answers.microsoft.com/en-us/...16500c3?page=1
https://answers.microsoft.com/en-us/...2-7df17e82fb3d