Windows update fails with error code 0x643

Our site was having the same issue for 100+ computers using Windows Update Server. All were XP or 2003. We resolved it by doing the following via a script:

1. Uninstall KB976569 - No Reboot Required
2. Install KB974417 - No Reboot Required
3. Install KB976569 - No Reboot Required

Apparently KB974417 needs to be installed before KB976569

Similar issue  XP Pro system, trying to install KB974417 getting error, and finding  0x80070643 code in the errorlog for the update error.

Process above fixed the issue for us.

By way of background this box is a test system, which is not left turned on.. It can sometimes go months between being 'powered up'.  So it tends to get updates in clumps when it is turned on to be used for some particular bit of testing that calls for the config on the box.  That might have a lot to do with what appears in this case to be an 'order sensitive' issue (where a system turned on and updated more frequently may not have had this issue

--Chuck

Our site was having the same issue for 100+ computers using Windows Update Server. All were XP or 2003. We resolved it by doing the following via a script:

1. Uninstall KB976569 - No Reboot Required
2. Install KB974417 - No Reboot Required
3. Install KB976569 - No Reboot Required

Apparently KB974417 needs to be installed before KB976569

If you have problems installing KB974417, try this first. Worked for me on three 2003 servers.

Thank you Brainstormer!

I looked the above statement over but I still don't understand the solution. Could you please email the results to me? My email address is: *** Email address is removed for privacy ***. Or just write a reply directly to me.

Thanks.

Sincerely,

Sheridan_Esmerelda.

My PC has Windows XP Professional SP3 and all the automatic updates.  However, after suffering from the .NET Framework 1.1, 2.0 and 3.5 security updates failing for the last several months, I finally researched, found this thread and read it and a bunch of other threads for two days before committing my main production PC to a repair attempt.  I used the davelasker method (above) and that worked for me.

Here are some notes:

(1) after using the Aaron Stebner .NET Framework remover I  did a restart.

First there was a message from Intuit Sync Manager.exe not being able to initialize.  Then I opened a C: drive folder and got a BSOD and automatic restart.

Evidently removing Framework crushed QuickBooks Pro 2009 and Acronis 10 Backup - they both complained after the second restart.  Further, QB attempted to do a reinstall and fell into a Windows Installer loop.  It took several End Tasks in TaskManager to kill it dead.

(2) began installing .NET Framework from 1.1 (don't know which app uses it, but since my PC is > 4 years old, I figured it may be vital for some app and started there).  I had downloaded all the update files to my network server and installed from that machine.

(3) I ignored any prompts for restart until i finished with the .NET Framework 3.5SP1 install, then I did a restart.

(4) Did Windows Update and that found a NET Framework 3.5 SP1 and NET Faramework 3.5 family (KB951847) update which installed okay. This required a restart.

My PC appears to be back to normal.  QB 2009 and Acronis both appear to be operational.

Now it appears I have some VS2008 and SQL2005 update failures, but that's for another thread.  Oh, and I talked myself into getting a new Win7 PC just for my web development work and hopefully keep this production PC more stable.

Thanks to everyone for all the posts.  This forum is a useful resource.

Any tips on fixing Windows 7 message at start up: "microsoft.net framework version 2.0 is required to continue"