As part of a new project, we're building a few Windows 2012 R2 VHDXs from scratch (and starting with RTM) and I've run into a problem when it comes to windows updates.
I can confirm that the problem definitely does not seem to be SCCM specifically, as a few of our packages get installed (after the client is installed, etc) AND one of the windows updates does get installed.
When I run Microsoft Update on a fresh, RTM copy of Windows 2012 R2, I get the following list of Windows Updates as needed:
KB2931366, KB2862152, KB2868626, KB2892074, KB2893294, KB2912390, KB3172729*, KB2843630, KB2884846, KB2887595, KB2903939, KB2911106, KB2913152, KB2913270, KB2919394, KB2923528, KB2928680, KB2939087, KB3021910
I have searched all updates in our SCCM catalog, and the only one that shows up (for 2012 R2) is KB3172729. And sure enough, as soon as I run the Update actions, my new VM will see KB3172729 as needed and install it. But that seems to be the only update it will "see" in SCCM. The rest will show as needed via Windows/Microsoft Update. But nothing will ever happen from SCCM.
Now, I imagine the problem is one of detection. Every single one of those updates has been superseded many, many times and I imagine all of them exist in the more current rollup updates.
My question is, does anyone know what patches I should (or can) manually apply to my base VHDX to update it's patching to a point where it can finally detect the needed updates from SCCM?