Recent updates are unchecked in Windows Update. Why?

So it looks like we finally have an answer as to why not all important updates are always checked! This has drove me crazy for ages. I presume if I don't manually check this update I can forgot about it and Microsoft will check it and it will install itself when they're ready.

I had the same update unchecked. I took all updates (including unchecked) and no problems. I did however take a couple updates at a time and the unchecked one by itself.

Here's something everybody might find interesting it comes DIRECTLY from a Doug Neal a MS update software engineer. Susan Bradley, a Community Moderator over at the Microsoft Answers forums posted this.

-----------------------------------------------------------------------------------------------------------------------------------
What you are seeing is "throttling" or an update that it not being flagged by Microsoft as optional.
In the case of Office file validation, it is optional.
They may at a later date after they see that there's no problems with the update, go back and reflag it and precheck the box.

http://marc.info/?l=patchmanagement&...6109306522&w=2

Although we don't generally use the word 'throttling' externally, that's exactly what \
this is. An unchecked update in the WUapp (Windows Update Control Panel applet) is \
an indication of an update that's being throttled (publicly called, "gradually \
releasing update x over a period of time"). This only affects the consumer \
scenarios: automatic update (AU) and Windows/Microsoft Update (WU/MU). And usually \
only the tech savvy folks would see it since they would need to open WUapp, see the \
update and notice it's unchecked). Enterprise scenarios (WSUS, SMS, SCCM, SBS, SCE, \
MBSA) and the MU Catalog are not affected since there's no concept of throttling \
(local admins like you have this control).

Updates are generally throttled when they are (a) major releases that need to be \
gradually deployed (like a major version upgrade for Internet Explorer), (b) when \
there are potential quality issues found in the first day or two of release (so we \
can slow the deployment while we gather data to assess the scope of an issue), or - \
as in this case - (c) we don't want to hit every Windows consumer PC on the planet \
at an inopportune time (like during the holidays) - but still give tech-savvy admins \
the ability to release the update (through WSUS/SMS/SCCM or by checking the box in \
WUapp).

A throttled update can be seen in the LOGs as the "regulation server" not permitting \
the download of the update. Of course, if you interactively check the checkbox in \
WUapp, you will circumvent the regulation server (throttling) and receive the update \
anyway.

doug neal
Microsoft Update (MU)

legacy7955 said:

Here's something everybody might find interesting it comes DIRECTLY from a Doug Neal a MS update software engineer. Susan Bradley, a Community Moderator over at the Microsoft Answers forums posted this.

http://marc.info/?l=patchmanagement&...6109306522&w=2

Posted that same link earlier in this thread . Don't go there today, he's participating in the blackout.

forkboy said:

So it looks like we finally have an answer as to why not all important updates are always checked! This has drove me crazy for ages. I presume if I don't manually check this update I can forgot about it and Microsoft will check it and it will install itself when they're ready.

I specifically asked that question of Susan but never got a response. I'm not exactly sure if what you describe will eventually happen.

Some have reported problems that they think they can trace to this update. Others no issue. I haven't installed it yet but it is a security update so I wish MS would figure it out.

bru said:

forkboy said:

So it looks like we finally have an answer as to why not all important updates are always checked! This has drove me crazy for ages. I presume if I don't manually check this update I can forgot about it and Microsoft will check it and it will install itself when they're ready.

I specifically asked that question of Susan but never got a response. I'm not exactly sure if what you describe will eventually happen.

Some have reported problems that they think they can trace to this update. Others no issue. I haven't installed it yet but it is a security update so I wish MS would figure it out.

Bru I installed it on to Win 7 PC's without any issues.

Lo and behold today WU has KB2585542 checked and ready for installation. Curious if anyone else who did not install it also now has it checked.

I have to think it was done because I posted about how ridiculous the situation was on MS Answers. It seems someone actually listened.