Windows Update Issue which every SCCM OSD/OSI Engineer should know! (KB2894518)

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.

Thomas Kurth
Follow me

Thomas Kurth

Principal Workplace Consultant at baseVISION AG
I’m a consultant, trainer and architect for workplace management and enterprise mobility projects with Microsoft Technologies in the past eight years. I love to push and design the modern workplace based on Windows 10, EM&S and O365 for my customers which is the only answer for the current security threats, agile world and the fast-changing business requirements of my customers. Important for me is to simplify and automate the operational processes, because there are the highest costs.

MCSEMCTCMCE
Thomas Kurth
Follow me