Are you guys having issues doing a build and capture or deployment, while including the recent patches ?

It looks like another patch is requiring multiple reboots which breaks the task sequence...

Long story short... the last time I created a .Wim file was in June (with ZTIWindowsUpdate) - it included all the patches as of June 2014. This image has been deployed since then with no problem. All the other monthly patches (07/08/09/10/11/12/01) can be installed successfully through the deployment task sequence with no problem.

Then last week, I decided to create a new .Wim file to include all the patches as of January 2015. In my build and capture step, it exits because one of the updates requires multiple reboot. I checked on the following website and it has not been updated since October 22nd : http://support.microsoft.com/kb/2894518

Do any of you experiences issues with a WSUS that requires multiple reboot recently ?

Thanks!

Yes, everyone does; there's even a KB on it: http://support.microsoft.com/kb/2894518

The only real solution is to either use (stand-alone) MDT to build your image or to inject your updates offline using DISM directly or the Offline Updates task from MDT (or the offline updates functionality in 2012).

Hmm ok. But do you know a quick way to inject the updates into the Wim file? I have about 200 updates to install...

The only solution I see is to get the list of all the 200 updates installed on a computer, manually download them and inject them? Is there something better than that that I could do...?

As mentioned, the MDT offline updates task will do it. Add it to your build and capture and it will do the work for you using the updates in an update package that you've previously created. Alternatively, use a stand-alone instance of MDT to create your image (using a build and capture TS of course) -- this can then use a stand-alone instance of WSUS to install the updates into your image which you then import into ConfigMgr.