Assume that a Microsoft System Center Configuration Manager task sequence that uses the "Install Software Updates" step installs a software update that triggers multiple restarts after the task sequence successfully runs the Install Software Updates task. In this situation, the task sequence can fail and generate the following error message:
Task Sequence environment not found
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 is not controlled by the task sequence. Therefore, the task sequence execution state is not saved before the restart because the second restart is not controlled by the task sequence. When the task sequence resumes after the second restart, no state is available to continue successfully.
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 to require multiple restarts. This article will be updated when more updates are reported.
MS15-030: Description of the security update for Remote Desktop protocol: March 10, 20153039976
MS15-030: Vulnerability in Remote Desktop protocol could allow denial of service: March 10, 20152984976
RDP 8.0 update for restricted administration on Windows 7 or Windows Server 2008 R22981685
Security updates cannot be installed if BitLocker is not installed on your computer2966034
MS14-030: Description of the security update for Remote Desktop Security Release for Windows 8.1 systems that do not have the 2919355 update installed: June 10, 20142965788
MS14-030: Description of the security update for Remote Desktop Security Release for Windows: June 10, 20142920189
Description of the update rollup of revoked noncompliant UEFI modules: May 13, 2014 2871777
A servicing stack update is available for Windows RT, Windows 8, and Windows Server 2012: September 20132871690
Microsoft security advisory: Update to revoke noncompliant UEFI boot loader modules 2862330
MS13-081: Description of the security update for USB drivers: October 8, 20132771431
A servicing stack update is available for Windows 8 and Windows Server 20122821895
A servicing stack update is available for Windows RT and Windows 8: June 2013
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
Binary files in some USB drivers are not updated after you install Windows 7 SP1 or Windows Server 2008 R2 SP1
Because this second restart is not controlled by the task sequence, no execution state is saved before the restart. When the task sequence resumes after the restart, no state is available to continue successfully. Additionally, the Smsts.log file may contain the following message when you experience this issue:
Task Sequence environment not found
Also, clients that are running release versions that are earlier than Microsoft System Center 2012 Configuration Manager Service Pack 1 may contain the following log entry:
Task sequence completed in Windows PE.
The client computer may also be stuck in provisioning mode after the task sequence fails. To determine whether the computer is in provisioning mode, check the following registry subkey:
should be set to false
. If it set to true
, use one of the following methods to take the client out of provisioning mode:
- Use the Windows Management Instrumentation (WMI) method SetClientProvisioningMode to correctly take the client out of provisioning mode. The easiest way to do this is to run the following Windows PowerShell command:
Or, run the following command at an elevated command prompt:
Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false
powershell Invoke-WmiMethod -Namespace root\CCM -Class SMS_Client -Name SetClientProvisioningMode -ArgumentList $false
- Reinstall the client.
Do not try to fix the client by changing the value of ProvisioningMode
. This action will not fully take the client out of provisioning mode.