Hello,

Yesterday Microsoft revised KB3001652 which was initially published in October 2014.

Because the original KB was part of a software update group currently deployed (to cover patch new computers), the new/revised version has been automatically deployed to all existing computers.

How can I prevent automatic deployment of new version of an existing update ?

Regards.

To my knowledge, nothing is automatically done with revisions unless you have an ADR running that would have included it. Thus, just because you previously included a revision of an update in an update group, it does not mean future revisions are also included.

Hello Jason,

As a matter of fact it did happen. I do not use ADR.

On Wednesday, the software update group containing the original KB was now containing the revised one.

Sylvain06,

This happened to us today with KB3013769. We approved the version released on 12/9/2014 a few months ago and today a revision was released. We started getting calls from clients that they were being offered KB3013769. One person ran it but couldn't download the content.

When I looked at the Software Update Group containing this update, the revision for today was in there. It was deployed but the content wasn't downloaded. I've never seen this type of behavior before so I killed it for now.

I found your post and thought this sounded similar to what you experienced.

Dave

Hello Dave,

Same situation with same KB. I just checked following your post.

This being said, last time (when I initially wrote this post), it was slightly different in the sense that the new release was downloaded (I never understood how it did happen).

Anyway in both cases, I do not like this behavior. As per our company policy, updates should be deployed once a month and I do not really appreciate to have this kind of uncontrolled behavior. I would like a way to systematically consider a new revision as a new update, aka not to automatically replace the previous revision by the new one in a software update group. I do not know if this behavior is by-design.

Regards.

I'm also seeing this. After today's updates were released, I'm showing all three editions of KB3013769 as not downloaded and deployed. There appears to be an additional file in the content information tab for the update:

Yet according to https://support.microsoft.com/en-us/kb/894199, only the metadata for this update has changed, not the binaries. What are we meant to do with this?

Interesting. You should open a case with Microsoft Customer Support Services and classify it as a bug and/or file a design change request on connect.microsoft.com.

Wow... Just did a search online as I found this happened to us last night when the server sync'd... The ADR pulled the "revised" update released in 2014 and added it to our 2015 package. I see two issues here:

1) ADR's should have an option to only download NEW RELEASES instead of new releases AND revised.

2) Why is a "revised" update causing a reinstall? Should this type of major change be a superseded condition thus issuing brand new meta data and associated patch files?