Configuration Manager 2012 – Software Updates That Require Multiple Reboots may Cause Task Sequence Failure 2

Oke so sometimes your OSD Task Sequence in ConfigMgr 2012 (or even 2007..) fails on you? Tried all the usual troubleshoot steps..

Well maybe not all, check your Windows Updates!

Yes, Microsoft has confirmed that there are updates out there that will break your Task Sequence.

This is the KB about that:

KB2894518 – Software Updates That Require Multiple Reboots may Cause Task Sequence Failure within Configuration Manager (http://support.microsoft.com/kb/2894518)

If a Configuration Manager (ConfigMgr 2007 or ConfigMgr 2012) Task Sequence that leverages the Install Software Updates step installs a software update that triggers multiple reboots, the task sequence may fail to complete successfully. This occurs because the first reboot initiated by the software update is properly controlled by the Task Sequence, however the second reboot request is initiated by a Windows component (typically Component-Based Servicing) and therefore not controlled by the Task Sequence.

In short the following updates are affecting your OSD Task Sequence:

• 2862330 MS13-081: Description of the security update for 2862330: October 8, 2013
• 2771431 A servicing stack update is available for Windows 8 and Windows Server 2012
• 2871777 A servicing stack update is available for Windows RT, Windows 8, and Windows Server 2012: September 2013
• 2821895 A servicing stack update is available for Windows RT and Windows 8: June 2013
• 2545698 Text in some core fonts appears blurred in Internet Explorer 9 on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2
• 2529073 Binary files in some USB drivers are not updated after you install Windows 7 SP1 or Windows Server 2008 R2 SP1
• 2871690 Microsoft security advisory: Update to revoke noncompliant UEFI boot loader modules

Especially the 2862330 has the statement in the description 😉

After you install security update 2862330 on a computer that is running Windows 7 or Windows Server 2008 R2, your computer may restart two times. The additional restart is required to make sure that the security update is completely installed. Installation of this update may leave the system in a partly updated and therefore vulnerable state. To address this issue, the update performs an additional step to update the computer. This additional step may require an additional restart of the computer.

Note Task sequence could fail in System Center Configuration Manager if the task sequence uses an “Install Software Updates” step to install a software updates that require multiple restarts.