Stealth Windows Updates Causing XP Repair Headaches

Rich Tate

Supreme [H]ardness
Joined
Jun 9, 2005
Messages
5,955
It looks as though those stealth updates that everyone was up in arms about are now causing issues with the repair feature in XP.

A set of Windows updates that Microsoft silently pushed out to users' PCs this summer is interfering with the repair function of Windows XP, an independent researcher said Thursday.
 
I'm not big on conspiracies but this does smell bad.
Stealth updates don't make me happy, quite the opposite!
 
I ran into an issues like this just doing a upgrade from window 2k to xp recently and from doing a repair install a few months ago. Both cases were resolved by reinstallng the newest version of windows update auto update.

Even if they didn't do this as a stealth upgrade, how many people test repair installs and upgrading to newers versions of an OS when doing their checks of an update? Is everyone making sure that every patch they install on XP will not cause any issues if you decide to upgrade to Vista later on? If not then you better otherwise you might miss some "issue".

I think this is just another thing for people to bitch about that really isn't as big of an issue as they are trying to make it out to be.
 
I ran into an issues like this just doing a upgrade from window 2k to xp recently and from doing a repair install a few months ago. Both cases were resolved by reinstallng the newest version of windows update auto update.

Even if they didn't do this as a stealth upgrade, how many people test repair installs and upgrading to newers versions of an OS when doing their checks of an update? Is everyone making sure that every patch they install on XP will not cause any issues if you decide to upgrade to Vista later on? If not then you better otherwise you might miss some "issue".

I think this is just another thing for people to bitch about that really isn't as big of an issue as they are trying to make it out to be.

I disagree. MS should NEVER install anything on a PC if the user hasn't agreed to it. When this update was first exposed, an MS employee blogger said that they had to do it this way, otherwise people couldn't get updates down the road. Of course this is a complete crock, as all they had to do is insist that users grab that update before they grab more updates.

In the case of people, like myself, who have it set up to download, but not install, the update is there, and I can choose to install it or not.

Mistakes happen, and bugs get past QA. I have no beef with that (well no more than any other bug, and I can promise you there are far more in some industry specific software my company uses than in XP); however, it's unacceptable to update a system that's specifically says don't install without my permission.

Let's hope MS never does this again. And if other companies are doing this, then the same goes for them as well.
 
Let's hope MS never does this again. And if other companies are doing this, then the same goes for them as well.
You act like this is the first time. It's not. For some reason this is the first time anyone made a big deal out of automatic updates updating itself. It's always worked that way for years, something that you completely dismiss when "an MS employee blogger" explained it a couple of weeks ago.

http://blogs.technet.com/mu/archive/2007/09/13/how-windows-update-keeps-itself-up-to-date.aspx
This is helpful and important feedback, and we are now looking at the best way to clarify WU’s behavior to customers so that they can more clearly understand how WU works. At the same time, however, we wanted to explain the rationale for the product’s behavior so our customers know what the service is doing: WU updates itself to make sure it continues to work properly.
Other than the bug described in the OP, it seems to be doing that.
 
You act like this is the first time. It's not. For some reason this is the first time anyone made a big deal out of automatic updates updating itself. It's always worked that way for years, something that you completely dismiss when "an MS employee blogger" explained it a couple of weeks ago.

http://blogs.technet.com/mu/archive/2007/09/13/how-windows-update-keeps-itself-up-to-date.aspxOther than the bug described in the OP, it seems to be doing that.

Then why is it when you install a XP (no SP) does it work fine? It clearly does not need a stealth update. You log onto Windows update and the first update is an update to Windows Update.

Either They have to do it for it to work, in which case reinstalling from the original XP should be broken (now or in the near future) or it doesn't need to sent as they did.

If you install an original copy of XP, does it work when you go to windows update? Why yes, yes it does. Does Windows update automatically download updates? Why yes, yes it does. Is one of those updates an update to Windows Update? Why yes, yes it is.

It's not necessary, and they shouldn't do it to any machine that isn't listed as automatically download and automatically install.

And FYI, people were making a big deal of this before the bug. I just heard about the bug a day or so ago, which was at least a week or 2 after people were upset about the update.
 
Mistakes happen, and bugs get past QA. I have no beef with that (well no more than any other bug, and I can promise you there are far more in some industry specific software my company uses than in XP); however, it's unacceptable to update a system that's specifically says don't install without my permission.

however, it's unacceptable to update a system that's specifically says don't install without my permission.

It is always unacceptable for a company to install something on your machine without your knowledge and permission.
It is kinda like breaking and entering, which is a felony...:rolleyes:
 
Then why is it when you install a XP (no SP) does it work fine? It clearly does not need a stealth update. You log onto Windows update and the first update is an update to Windows Update.
Because the wu*.* files get updated during regular updates too. You know the 3.1 installer that comes on the first XP update? That also updates the wu*.* files, allowing you to get further updates. :rolleyes:
 
Because the wu*.* files get updated during regular updates too. You know the 3.1 installer that comes on the first XP update? That also updates the wu*.* files, allowing you to get further updates. :rolleyes:

Thanks for basically repeating what I already said, that one of the first 2 or 3 updates that you see is an update to windows update. It's not exactly hidden. Now if that's the WMI 3.1 installer, ok, but Windows update shows a message stating that you need to update windows update to the latest version. After that, all the other updates follow.
 
Back
Top