PENDING Windows 10 Upgrade Task Sequence Failure

[Sokoban]

Hi I have got same error on several machines when I have done Task Sequences Windows 10 22H2 Upgrade from Windows 10 1903

The error message SMST.log show that:

"Windows Setup failed with hexadecimal exit code 0x80070652 (decimal 2147944018). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online.    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
Failing this task sequence step    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
upgrade.Run(), HRESULT=80004005 (K:\dbs\sh\cmgm\1125_114522\cmd\1w\src\client\OsDeployment\UpgradeWindows\upgradewindows.cpp,1881)    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
Exiting with code 0x80004005    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
Process completed with exit code 2147500037    TSManager    04-09-2023 16:10:29    42592 (0xA660)
TSManager    04-09-2023 16:10:29    42592 (0xA660)
Failed to run the action: Upgrade Operating System. Error -2147467259    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Not in SSL.    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Set a global environment variable _SMSTSLastActionName=Upgrade Operating System    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Clear local default environment    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Let the parent group (Upgrade the Operating System) decides whether to continue execution    TSManager    04-09-2023 16:10:29    42592 (0xA660)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed. Error 0x80004004    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Failed to run the last action: Upgrade Operating System. Result -2147467259. Execution of task sequence failed.    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Not in SSL.    TSManager    04-09-2023 16:10:30    42592 (0xA660)
Showing task sequence error message after failure in task sequence step of type 'SMS_TaskSequence_UpgradeOperatingSystemAction'    TSManager    04-09-2023 16:10:30    42592 (0xA660)
Task Sequence Engine failed! Code: enExecutionFail    TSManager    04-09-2023 16:25:37    42592 (0xA660)
TSManager    04-09-2023 16:25:37    42592 (0xA660)
Task sequence execution failed with error code 80004005    TSManager    04-09-2023 16:25:37    42592 (0xA660)"

Any ideas ?

 

[Garth]

What troubleshooting have you done? Have you reviewed the error messages?

 

[Sokoban]

What troubleshooting have you done? Have you reviewed the error messages?

The task sequence manager could not successfully complete execution of the task sequence Error Messages 11170...

I have done that :

1. Check the SMSTS.log file for more information about the error. Look for any error messages that may provide more details about the issue. See below
2. Verify that the computer has sufficient disk space to perform the upgrade. Ensure that there is enough free space on the system drive to accommodate the upgrade. 33 GB in C Free
3. Check the network connectivity between the client computer and the Configuration Manager server. Ensure that the client computer can communicate with the server and that there are no network issues. The client can ping the SCCM Server
4. Verify that the user account running the task sequence has the necessary permissions to perform the upgrade. Ensure that the account has administrative privileges on the client computer. Missing Network Access Account in SCCM ( it is needed ? )
5. Check if any antivirus or firewall software is blocking the upgrade process. Disable any antivirus or firewall software temporarily and try running the task sequence again. The clients is running Windows Defender
6. Ensure that the necessary files and drivers are available on the client computer. Verify that the required drivers and files are present on the client computer and that they are accessible. How will I checked that ? Remotely ??

Please help me ,

// Sokoban

 

[Sokoban]

Hi Find it ( if anyone is interestered )
Windows Setup failed with hexadecimal exit code 0x80070652 (decimal 2147944018). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online. =

Another installation is already in progress. Complete that installation before proceeding with this install.

 

[supriyo91]

Hi I have got same error on several machines when I have done Task Sequences Windows 10 22H2 Upgrade from Windows 10 1903

The error message SMST.log show that:

"Windows Setup failed with hexadecimal exit code 0x80070652 (decimal 2147944018). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online.    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
Failing this task sequence step    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
upgrade.Run(), HRESULT=80004005 (K:\dbs\sh\cmgm\1125_114522\cmd\1w\src\client\OsDeployment\UpgradeWindows\upgradewindows.cpp,1881)    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
Exiting with code 0x80004005    OSDUpgradeWindows    04-09-2023 16:10:29    39084 (0x98AC)
Process completed with exit code 2147500037    TSManager    04-09-2023 16:10:29    42592 (0xA660)
TSManager    04-09-2023 16:10:29    42592 (0xA660)
Failed to run the action: Upgrade Operating System. Error -2147467259    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Not in SSL.    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Set a global environment variable _SMSTSLastActionRetCode=-2147467259    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Set a global environment variable _SMSTSLastActionName=Upgrade Operating System    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Clear local default environment    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Let the parent group (Upgrade the Operating System) decides whether to continue execution    TSManager    04-09-2023 16:10:29    42592 (0xA660)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed. Error 0x80004004    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Failed to run the last action: Upgrade Operating System. Result -2147467259. Execution of task sequence failed.    TSManager    04-09-2023 16:10:29    42592 (0xA660)
Not in SSL.    TSManager    04-09-2023 16:10:30    42592 (0xA660)
Showing task sequence error message after failure in task sequence step of type 'SMS_TaskSequence_UpgradeOperatingSystemAction'    TSManager    04-09-2023 16:10:30    42592 (0xA660)
Task Sequence Engine failed! Code: enExecutionFail    TSManager    04-09-2023 16:25:37    42592 (0xA660)
TSManager    04-09-2023 16:25:37    42592 (0xA660)
Task sequence execution failed with error code 80004005    TSManager    04-09-2023 16:25:37    42592 (0xA660)"

Any ideas ?

Hello recently I upgraded all windows 10 versions starting from 1607,1709,1809,1909,20H2,21H2 to 22H2.. I observed that the upgrade tasksequence was failing to upgrade the devices.. The error code posted in the logs are generic stating that there might be corrupted update/system files.
1. After searching for a long time I found an update in console called Enablement Package(Windows10.0-KB5015684-x64.cab).
2. I created a separate package and deployed it with a .cmd script(dism /Online /Add-Package /PackagePath:"Windows10.0-KB5015684-x64.cab" /NoRestart). Since SCCM shows already compliant, so deploying the update didn't work.
3. After the installation of the package, reboot and run the upgrade task sequence.. It should work.
4. Create a very basic upgrade task sequence and test.. If this works then you do the customizations later on.
5. Setupact & setuperror logs under the C:\Windows\Panther should also give a good idea why its failing..
6. Conixent audio driver is also another culprit keep an eye for that as well incase the upgrade gets stuck at 44%.