Stealth updates to Windows Update broke updating for some users.
Last month's
stealth updates to Windows Update caused a commotion within the community, with many arguing that the Microsoft should not update the updater if automatic updates were turned off while others argued that it seemed logical that the updater updated itself when the feature wasn't completely disabled by being told to not even check for updates.
Those arguing against the self updating Windows Update found a solid grip on their side of the argument when a select group of users found it impossible to install updates after using the "Restore from CD" function in Windows XP.
The problem that users ran into happens when users used the repair feature on genuine XP CD-ROMs. Generally, this is only done when Windows XP becomes unbootable for some reason or another.
Using the repair function on the CD will roll back drivers, patches, and Internet Explorer to the shipping variations found on the CD and should fix any problems that had occurred. Normally, the feature works flawlessly but in these particular cases, it created problems on its own.
After doing the restore and downloading updates from Windows Update, some of the executables do not get registered with Windows. This prevents updates from installing even if you had downloaded the updates. The Microsoft Update Product Team blog acknowledged the problem and began working hard to isolate the problems and offer up a fix.
Within a day of the problems being reported, Microsoft responded
with a Knowledge Base update. The KB article explains how to register the files with Windows that are failing to be registered automatically. Following the steps should take no more then a minute or two but you can expect an update to Windows Update to correct the update breaking issues sometime in the near future.
Were you one of the few affected by the update breaking update to Windows Update? Let us know if you ran into any problems by telling us
over in the forums.
:(
Updates to the update engine are perfectly fair, you would want the latest one when you decide to get updates etc. (Also, only users with "non legit versions" of windows will have it disabled at home.. offices would uses SUS servers.. so that isn't an issue here)
But most of the "non-critical" bugs in windows takes months, if not years to get addressed
I guess the only reasons this was fixed so much is that it breaks a fixing solution for windows XP (which is pretty important for a MS OS) and because after the anger at the update happening, forcing a bugged piece of software on people would have caused an uproar
Uh...oracle DOES have bugs that seem to last forever...dunno if you really ever used it, but yeesh.
2- WinXP reparation is crap. It usually creates more problem than it repairs (form my experience) and takes the SAME TIME (close the the minute) then doing a fresh re-install including formating and re-installing yourself all the applications and doing the updates.
I guess you don't have that many programs installed then... It's a breeze for those of us that sits a whole day or two configuring all the installed applications ><
With windows repair I could even exchange the mainboard and CPU without any problem at all, and it'll only take maximum 2 hours total to get the drivers installed and win repaired ;)