NEW Task Sequence OS Upgrade - In Progress 11142

[jv_sccm]

Hello,

I'm experiencing a high percentage of Task Sequence OS upgrade Stuck "In Progress".
Message ID 11142 ( This Task Sequence execution engine performed a system reboot initiated by an action).

Below is a partial of where the smsts.log stopped, looks like the upgrade stopped completely after the reboot request. I've checked Maintenance windows, execmgr.log, and policyevalator.log. Not seeing logs that helps me identify the caused. This is not a driver or feature issues. Check the folder C:\$WINDOWS.~BT\Sources\Panther

Upgrading to 1809 from 1709, 1803,

A few machines in the same Device Collection did Upgrade successfully so I know the Task sequence works. Any idea on what I can check? Thanks!

Windows Upgrade Setup progress: 89% OSDUpgradeWindows 8/28/2019 8:24:10 PM 12868 (0x3244) Windows Upgrade Setup progress: 96% OSDUpgradeWindows 8/28/2019 8:24:20 PM 12868 (0x3244) Waiting for Windows Upgrade Setup process to return ... OSDUpgradeWindows 8/28/2019 8:24:30 PM 12868 (0x3244) Process completed with exit code 0 OSDUpgradeWindows 8/28/2019 8:24:39 PM 14428 (0x385C) ExecuteWithTimeout returned Windows Setup process hexadecimal exit code 0x00000000 (decimal 0) OSDUpgradeWindows 8/28/2019 8:24:39 PM 14428 (0x385C) Wait for event returned 0 OSDUpgradeWindows 8/28/2019 8:24:39 PM 12868 (0x3244) Windows Setup completed with exit code hexadecimal 0x00000000 (decimal 0) OSDUpgradeWindows 8/28/2019 8:24:39 PM 12868 (0x3244) Saving exit code of Windows upgrade - hexadecimal 0x00000000 (decimal 0) - to Task sequence environment variable '_SMSTSOSUpgradeActionReturnCode', as decimal string OSDUpgradeWindows 8/28/2019 8:24:39 PM 12868 (0x3244) Windows Setup completed successfully! OSDUpgradeWindows 8/28/2019 8:24:39 PM 12868 (0x3244) Exiting with code 0x00000000 OSDUpgradeWindows 8/28/2019 8:24:39 PM 12868 (0x3244) Process completed with exit code 0 TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) !--------------------------------------------------------------------------------------------! TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Successfully completed the action (Upgrade Operating System) with the exit win32 code 0 TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Not in SSL. TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Set a global environment variable _SMSTSLastActionName=Upgrade Operating System TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Clear local default environment TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) The action (Upgrade Operating System) requested a retry TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Created volatile registry entry for pending reboot initiated by this task sequence TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Executing command line: "bcdedit.exe" with options (0, 0) TSManager 8/28/2019 8:24:39 PM 5228 (0x146C) Process completed with exit code 0 TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) TSUEFIDrive: TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Updated security on object C:\_SMSTSVolumeID.7159644d-f741-xxxxxxxxxx TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Updated security on object D:\_SMSTSVolumeID.7159644d-f741-xxxxxxxxxx. TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Updated security on object E:\_SMSTSVolumeID.7159644d-f741-xxxxxxxxxx. TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Updated security on object D:\_SMSTaskSequence. TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Set a global environment variable _SMSTSNextInstructionPointer=22 TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Set a TS execution environment variable _SMSTSNextInstructionPointer=22 TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Set a global environment variable _SMSTSInstructionStackString=18 TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Set a TS execution environment variable _SMSTSInstructionStackString=18 TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Save the current environment block TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) Expand a string: %_SMSTSMDataPath%\Logs TSManager 8/28/2019 8:24:40 PM 5228 (0x146C) _SMSTSReturnToGINA variable set to: TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) SMSTSUninstallCCMClient variable set to false TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) _SMSTSCaptureMedia variable set to false TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) The action (Upgrade Operating System) initiated a reboot request TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) Not in SSL. TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) **************************************************************************** TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) Execution engine result code: Reboot (2) TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) Task Sequence Manager ServiceMain finished execution. TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) Task Sequence Manager execution terminated as system shutdown is in progress. Code 0x00000000 TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) GetTsRegValue() is unsuccessful. 0x80070002. TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) End program: TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) Stopping Task Sequence Manager service TSManager 8/28/2019 8:25:10 PM 5228 (0x146C) RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 8/28/2019 8:25:10 PM 13484 (0x34AC) GetTsRegValue() is unsuccessful. 0x80070002. TSManager 8/28/2019 8:25:10 PM 13484 (0x34AC) End program: TSManager 8/28/2019 8:25:10 PM 13484 (0x34AC)

 

[Edy]

am seeing exit code 0 which is successful and the TS initiated a reboot request. is the device not upgraded?

 

[Markosss]

I have the same problem. Several clients stop at status "This Task Sequence execution engine performed a system reboot initiated by an action" The system on these clients is updated only the status is bad. What can i do? Systems have been upgraded to Windows 10 20H2. The client version is up-to-date on these systems.