First post, by feipoa
I pulled two of my PIII systems out of the closet recently. One system is a dual PIII-850 coppermine, the other is a dual PIII Tualatin 1.5 GHz. They run XP Pro SP3 with POS2009 updates.The last I updated was sometime in late 2016 on the Tualatin and early 2017 on the Coppermine. Since I had the systems out, I decided to let the Windows Update Service update both systems. Well, it seems there is some update or group of updates between late 2016 until now which is causing issues. The Win32 Services hangs with an unexpected error. The system doesn't work well now, like it is expecting some services to be running and is waiting for them to come alive. Update service doesn't work. Cannot really do anything. It boots, but even with automatic updates disabled, it spits out an "unexpected" Win32 error. I looked up the particular error on google, but it is so general that it can be anything.
During installation of automatic updates, the system seems to need to reboot a few times in sequence. This is not unexpected as there are over 2 years worth of updates. The following updates caused errors,
.NET Framework 3.0 - KB4338597
.NET Framework 2.0 - KB4014580
.NET Framework 2.0 - KB4054178
however I am uncertain if an update just prior to these is what was leading to the errors of later updates. As I have a P4 Prescott and an Opteron 185 receiving the same updates without error, I suspect some updates are requiring a CPU-specific hardware feature, e.g. SSE2 or SSE3, in which the PIII does not possess. I would have thought that the update process would have checked for this condition though.
Have any of you run into this issue and determined which update or updates are causing the problem? Two years worth of updates is a lot to go through one by one. I think there were 92 updates. I used a restore point to restore both systems back to the state just before running today's updates, so at least I'm back at square one.
The obvious idea is to not install those four KB updates, but I suspect there is more to it than that alone. I was thinking to first install all the Windows OS-specific updates. If OK, move onto .NET, Office, etc. If the issue is Windows OS-specific, break the updates into halves, and halves again until the faulty update is discovered. Very cumbersome though. Lots of restoring the system and trial and error. Anyone run into this issue and find the fault?