Task Sequence Fails in Configuration Manager if Software Updates Require Multiple Reboots

New KB article for ConfigMgr 2012

Symptoms

If a Configuration Manager Task Sequence that leverages the Install Software Updates step installs a software update that triggers multiple reboots, after successfully running the Install Software Updates task, the task sequence can fail with the following error message:

“Task Sequence environment not found”

Cause

The first restart that is initiated by the software update is controlled by the task sequence. However, the second restart request is initiated by a Windows component (typically, Component-Based Servicing) and therefore is not controlled by the task sequence. As the second reboot is not controlled by the Task Sequence, the Task Sequence execution state is not saved before the restart. When the task sequence resumes after the second restart, no state is available to continue successfully.

Resolution

To resolve this issue, we recommend that you apply any updates that require dual restarts by using the usual Software Updates feature of Configuration Manager instead of using task sequences. The following software updates were reported as requiring multiple restarts. This article will be updated as more updates are reported.

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