Often I see the following issue, updates are installed during a Task Sequence, then the Task Sequence doesn’t continue after a reboot. In the smsts.log are errors like these:
!sVolumeID.empty(), HRESULT=80004005
!sTSMDataPath.empty(), HRESULT=80070002
TS::Utility::GetTSMDataPath( sDataDir ), HRESULT=80070002
Failed to set log directory. Some execution history may be lost.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Executing task sequence
!sVolumeID.empty(), HRESULT=80004005
!sTSMDataPath.empty(), HRESULT=80070002
Task Sequence environment not found
Then you should check, if some updates require a second reboot and are listed in KB2894518. Because this second restart is not controlled by the task sequence, no execution state is saved before the restart. And when the task sequence resumes after the restart, no state is available to continue successfully.
- Exploring Baden, Switzerland: An Evening Guide for Workplace Ninjas Conference Attendees - August 15, 2023
- Unveiling a new version of M365Documentation PowerShell Module: Creating Markdown Documentation with Ease - July 22, 2023
- Microsoft Purview Information protect predefined permission groups demystified - February 28, 2023
1 Comment
Update: Multireboot issue with Windows Updates is solved - Workplace Management Blog · February 12, 2016 at 13:19
[…] and a half year ago I posted an article about a problem which every OSD Enginer should know. Some Windows Updates make multiple reboots and this behaviour breaks a ConfigMgr Task Sequence as […]