Seriously?  I am constantly fighting with something reseting my settings from download but don't install to download and install on vista.

My current candidates are the update system itself, onecare or vista itself.

Either way, I hate the freaking setting because it inevitably kills something I left running and looses data when it forces a reboot.

I have taken to checking the setting from time to time to make sure nothing changes it back.  Annoyingly, you can miss the window and still find your machine rebooted at the login screen letting you know it applied unapproved updates.

OneCare will reset the settings like this.

http://weblogs.asp.net/jgalloway/archive/2006/02/09/437790.aspx

The approval settings for the Windows Desktop Search update, aswell as 2 updates for .net Framework where apparently overwridden or reset to default, totally ignoring the automatic approval settings we defined in our WSUS server.

The result was that over 500 clients and 12 servers received these updates unintentionally.

I blogged about it here, includes screenshots from WSUS:

http://geekswithblogs.net/jemimus/archive/2007/10/25/116319.aspx

And looking at the blogosphere, we are not the only ones this happened to:

http://www.theregister.co.uk/2007/10/25/windows_update_snafu/

I am a little pissed off about this.

After reading this:

http://blogs.technet.com/wsus/archive/2007/10/25/wds-revision-update-expanded-applicability-rules-auto-approve-revisions.aspx

I have a better understanding of what might have happened. And it seems like the behavior is by design.

However, I believe the way this update was packaged and presented, undermines the logic we have come to expect from WSUS updates.

The problem is that the package is presented internally as a revision -update-, which are by default -always- automatically approved (your other approval settings don't override this), but it was combined with a scope change, that allowed the package to also install WDS on systems that did not have it previously.

It is the second behavior that causes the problem. Installation on systems that did not have it previously, is NOT an -update-, they should not behave as such.

Revision 105 was called "Windows Desktop Search 3.01 for Windows XP (KB917013)".  Classification: Update

Now from the name alone, it looks like its not an update, but a complete installation (which it was). I never got to see the name before the fact of course, because it auto-approved and installed itself.

The classification is "Update", and this is what troubles me. Surely, if this "update" can install itself on systems without previous revisions, it does not belong in the "update" classification?

This should have been split into 2 packages.

1. An -update- with new revision number 105, possibly with a slighty differnet name including the word "update". This would have been automatically approved if the default option for revisions auto-approving was not altered by the admin. The scope would be only install on systems with previous revisions of WDS

2. A new package, called "Windows Desktop Search 3.01 for Windows XP (KB917013)", possibly a new revision number, but certainly a different classification. I don't have a list of all the WSUS classifications here, but I am sure there is one that is suitable, wasn't their something for new Windows features?

Ever since I applied the SP1 update, I'm experiencing a nagging problem:

- Each time an office application (any one) starts, "Office is configuring..." and it goes through a installation sequence over and over for about 30 seconds. Very frustrating.

Your article was very nice thank you I was injured blogger

Your article was very nice thank you I was injured blogger

http://www.parcakontorbayiniz.com

http://www.yenilezzet.com

http://www.webreklamajans.com

Thanks this is great news for everyone in

updates on a computer, we use our safe and beautiful way microsoft a thank you

read your post was very good article you would like to follow continuously