Software Updates not Installing during Task Sequence

I am having a problem where software update were not getting installed during the "Install Updates" step in the task sequence.  All the roles on my SCCM 2012 Server are configured correctly for software updates.  Updates are deployed correctly to the correct collection.  I know this because once the system completes imaging the updates that were not installed in the task sequence start downloading and installing automatically.

I was trying to build my gold image by using the default Build & Capture task sequence.  When the task sequence would come to the "Install Updates" step it would stop for about 3-5 minutes but never say downloading or installing updates.  After the 3-5 minutes, it would just go to the next step.  I also checked "Continue on Error" on the "Install Updates" step or the whole task sequence would error out.

This fix will work with any task sequence you create not just Build & Capture.

Create the additions steps like the task sequence pictured below.

By adding multiple "Install Updates" steps in the task sequence all your updates will get installed.  Certain updates depend on other updates before they can get installed.  Also the great amount of updates release will cause the "Install Updates" step to time out.

Numbering each step in the task sequence will make troubleshooting easier.

The first step is to start the "Scan for Updates" SCCM action by using the command line below.

WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE

Here is a screen shot.

The next step holds the task sequence for five minutes before it starts the "Install Updates" step.  This gives the update scan time to complete.  Add the command line below.

ping 127.0.0.1 -n 300

Here is a screen shot

The next step is the standard "Install Updates" task sequence step.

This solution worked for me in getting my updates to install during the task sequence.  

A big thanks to this TechNet post and to Toolzz.com blog post to help solve this issue for me.