Why is Windows 8.1 Update and its prerequisites considered “not required” by SCCM

sccmsccm-2012-r2windows-8.1

I have a fresh (<2 months old) installation of a standalone SCCM 2012R2 server. I have installed the software update point and WSUS on the same server. SCCM and WSUS are synchronizing and some updates are deploying to freshly-deployed Windows 8.1 test clients.

The problem is this: The troubled Windows 8.1 Update KB2919355 does not deploy automatically.

SCCM seems to consider Windows 8.1 Update (KB2919355) "Not Required" despite that all 3 of the assets are Windows 8.1 clients:

enter image description here

I am aware that KB2919442 is a prerequisite for KB2919355. However, WSUS reports the prerequisite KB291442 as superceded by KB2989647:

enter image description here

KB2975061, KB2969339, and KB2904440 are each also superceded by KB2989647.

As it turns out, the update that supercedes the prerequisite to Windows 8.1 Update, KB2989647, is also considered "not required" by SCCM.

Which leaves me with the following questions:

  1. Why is Windows 8.1 Update and its prerequisites considered "not required" by SCCM?
  2. How does SCCM decide which updates are "required" and which are "not required"?
  3. Is there a way to override updates from "not required" to "required"?

Best Answer

The solution (see this technet thread) is to manually download and install the superseded prerequisite patch KB2919442. Once KB2919442 is installed, all subsequent updates should install through the usual SCCM Software Update deployment method.

To streamline this workaround a bit more, I packaged the prerequisite patch KB2919442 as an SCCM application and made it a required deployment. This strategy seems to be working and freshly-deployed Windows 8.1 RTM machines seem to eventually end up with current patches without intervention.