KB: Software Updates That Require Multiple Reboots may Cause Task Sequence Failure
If a task sequence is not continuing after the Install update step it is probably due to component based servicing.
You can easily find it by searching this text in the relevent log. The update will be mentioned 5 lines above.
Look in %windir%logsCBS
CBS has signaled TrustedInstaller that a reboot is required.
http://support.microsoft.com/kb/2894518 list some of the updates that do this.
The latest one I have found is KB2973351. To work around this problem I created a deployment group called Multiple Reboots that the capture machine isn't in.
I will update below any more:
kb2984976 - Thanks Jörgen Nilsson
3 Comments
Trackbacks for this post
-
[…] to HappySCCM for pointing in the right direction to troubleshoot https://happysccm.com//kb-software-updates-that-require-multiple-reboots-may-cause-task-sequence-failu… […]
Please expand more on this. You state you created another deployment group, how does the task sequence know which update group to pull from?
Hi,
Updates groups get deployed to collections.
Task sequence will get all the updates from collections that the machine is in. I added an exclude collection (A collection with my capture VM in it) rule so that my capture vm's aren't in the multiple update collection.