THE VOLE HAS ADMITTED that a flaw in its Windows XP repair system will permanently screwball systems and prevent them from updating to the latest security patches.
Earlier this year, Microsoft pushed out what is being termed a 'stealth update' to Windows Update. Normally, users are asked via the Update system what new patches, security fixes and the like to install and are prompted to install and reboot. However, this fix - which was to the Update system itself - was a stealth push from Microsoft, and installed under the radar.
However, it turns out that any system subsequently suffering a problem of any kind that requires the use of the Windows 'repair' function in installation will be locked out from Windows Update. Because the stealth update modifies original Windows files, attempting the repair will nix the fix and cause Windows Update to hang - thus preventing users from staying up to date.
Sure, you can go in and manually hack the Registry to get the whole thing to start working again - but this is hardly an ideal solution.
There's been no official Microsoft response on the issue so far, but many sysadmins are wondering why Windows Update needed to be patched in the first place, especially in this stealthy manner. µ
Tags: Microsoft
Good stuff to share. Also, i have something great to share with you too: a href="http://www.drivers-updates.net/" b Driver Robot /b /a . Believe it or not, it's the best a href="http://ww.best-driver-updater.com/" b Driver updater /b /a i've elver used.
I found that when my XP update last "worked", it installed IE 7 and promptly broke it. I cannot use any other browser to update XP and I cannot fix IE 7 with a patch because I cannot update or download any patches for it. Microsoft refuses to let Firefox assist in the update so the only solution I have is to live with a broken system... oh well, just as well I do not depend on it, I rely on Linux :)
Use windizupdates from 62nds or try to locate a "custom", ahem, edition of IE7 from somewhere!
"Windows Genuine Advantage" broke my update ages ago. It evidently stems from a problem with AMD cpu's. MS admitted it was a problem, but never came up with a fix so I haven't patched my machine for about a year.
ahem:

http://support.microsoft.com/kb/943144
I had this problem after repairing a P4 Prescott 2.8 GHz installation to an AMD Opteron 1212 HE installation (ie. changed mobo, cpu, and memory! -- never a good idea). The solution I came across can be found here: http://www.wsuswiki.com/ProceduretomanuallyRe-InstallAutomaticUpdateClient
1) Start -> Run, type CMD, and click Ok
2) Type rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemroot%\inf\au.inf and press enter
3) When asked, insert your installation CD, and when asked, restart.
Before I found this solution, I resorted to using IE Windows Update to tell me the updates I needed, I downloaded each, and created a batch to script their installation (with the start /wait prefix and /quiet /norestart suffix switches/commands)
I have Windows XP running on all three of my computers. Each one has a slightly different version- OEM and retail, although the main difference between them just seems to be how my logon/shutdown screens appear.

My OEM XP just received an automatic update notification for XML, and a retail version was able to connect to Windows Update through Internet Explorer to download a Root Certificates update.

I doubt Microsoft missed my network when stealth bombing XP, so users should still be able to access Update, so long as their system doesn't need to be repaired...
http://wiki.djlizard.net/Dial-a-fix will fix this problem easy!