Windows Updates Not installing but show compliant

[whoishomer1]

So about 2/3's of my SCCM computers aren't getting the latest windows updates.

I've downloaded all of last months windows updates to a software upgrade group, which I have them deployed to my distribution point.

It seems only about 1/3 of the PC's are showing the updates as "in progress" and they have downloaded them.

The other 2/3's of my PC's shows up as Compliant. If I go into the details of one of the compliant computers and press the Software Updates tab, it is just completely empty.

Any suggestions on where to start troubleshooting this and what could be causing the issue?

 

The UpdatesDeployment.log file seems to indicate that the PC's are finding the updates:

 

 

<![LOG[Raising client SDK event for class CCM_SoftwareUpdate, instance CCM_SoftwareUpdate.UpdateID="Site_6E7C6557-2495-437D-A4A6-DC476C11FBD7/SUM_250150ea-7e14-4a95-bfc1-e5baed59f03c", actionType 12l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time="02:08:11.239+360" date="08-12-2015" component="UpdatesDeploymentAgent" context="" type="1" thread="15292" file="event.cpp:405">
<![LOG[update (Site_6E7C6557-2495-437D-A4A6-DC476C11FBD7/SUM_250150ea-7e14-4a95-bfc1-e5baed59f03c) Name (Update for Windows 7 (KB3075851)) ArticleID (3075851) added to the targeted list of deployment ({62667FCC-E03D-423F-817F-5F9D894AFCDF})]LOG]!><time="02:08:11.239+360" date="08-12-2015" component="UpdatesDeploymentAgent" context="" type="1" thread="15292" file="updatesmanager.cpp:420">

 

 

But its saying there aren't any actionable items?

 

<![LOG[user logon system task]LOG]!><time="06:59:36.236+360" date="08-12-2015" component="UpdatesDeploymentAgent" context="" type="1" thread="5020" file="systemtasks.cpp:90">
<![LOG[EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0]LOG]!><time="06:59:56.775+360" date="08-12-2015" component="UpdatesDeploymentAgent" context="" type="1" thread="1324" file="updatesmanager.cpp:945">

[HotdogSCCM]

Sounds a lot like this:

http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx

I'd personally, on an impacted box (assuming the deployment is correct, etc, etc), install the best/current Windows Update Agent, manually, available from here:

https://support.microsoft.com/en-us/kb/3075851

Reboot it, bounce it, etc etc, then do a rescan for updates.

The "Stuck in Complaint" comment makes me think it's that, more than a deployment issue in and of itself.

[whoishomer1]

Hmm, I think this may be my issue!

I'm going to test this out, thanks for the great response!

[HotdogSCCM]

No problem. MS isn't staying up on keeping the hotfix article up to date, unfortunately. They're still referencing https://support.microsoft.com/en-us/kb/3050265 when in fact it's been updated several times; we're obviously up to August now. The 3050265 will obviously fix the issue, but it'll need to be updated again to August, so it'd make sense just to hop to August. They should add a disclaimer in the original link to be like "Going forward, download the most up to date Windows Update Agent client patch", instead of linking to a quickly-out-of-date monthly-updated patch.

[whoishomer1]

So I've confirmed that this hotfix does resolve the issue on a couple of test PCs.

I'll have to get this installed on all my boxes now.

Thanks

[Level4Analyst]

Please help! I need this fix for Windows10. Only Clients with the September patch got the october. Clients that were newly imaged only got the may update but shows compliant for the october.