FIX: SCCM Task sequence failed with error code 0x80220005

In this post, you will learn to FIX SCCM Task sequence failed with error code 0x80220005. The task sequence error prompt during operating system deployment with Configuration Manager when it’s failed to execute step added to rename the device. The error 0x80220005 Translate SCCM Error Codes to Error Messages No result in CMTrace Error lookup.

This task sequence failed with error code 0x80220005 often seen when automating the computer name by defining variables inside the task sequence, scripts, or prompting the wizard to specify the computer name to users at the time of deployment, and the computer exceeds the 15 characters limit. In case you’re auto-generating the computer name, You may experience deployment failure in the virtual machines as the serial number of the VM is too long.

Let’s learn how to display SCCM OSD Computer Name Prompt in Task Sequence Deployment. To change the computer name in the new OS, we will use the OSDComputerName variable during deployment SCCM OSD Computer Name Prompt In Task Sequence Deployment ConfigMgr

Issue Summary

This error appears at the initial stage when you have started the deployment. For example, if you’re providing a prompt to the user to enter the computer name, after providing the custom computer name with more than 15 characters in the Value text box, click OK to allow the task sequence to run.

Patch My PC
Edit Task Sequence Variable- FIX: SCCM Task sequence failed with error code 0x80220005
FIX: SCCM Task sequence failed with error code 0x80220005

Task Sequence fails with the following error message – Task Sequence: Deploy Windows 10 has failed with the error code (0x80220005). For more information, please contact your system administrator or help-desk operator.

FIX: SCCM Task sequence failed with error code 0x80220005
FIX: SCCM Task sequence failed with error code 0x80220005

In this scenario, Task Sequence terminated after the installation of the operating system. You will collect the logs at WinPE X:\Windows\temp\smstslog\smsts.log. To get the command prompt window, you have to press the F8 key and locate the location to Open the log.

 Here’s the highlight from the SMSTS.log –

1E Nomad
Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.
Exiting with return Code Unknown error 0x80220005
Process completed with exit code 2149711877
Failed to run the action: Apply Windows Settings, Unknown error (Error: 80220005; Source: Unknown) Task sequence failed with error code 0x80220005

FIX – SCCM Task sequence failed with error code 0x80220005

Let’s check the solution to fix this task sequence error code 0x80220005

When renaming a device, the new name must be 15 characters or less. If you’re taking inputs from the user, Make sure the computer name does not exceed the characters limit. Based on the above scenario, we asked the user to appropriate the device name and perform the deployment. If you had automated with scripts, do some modification, especially if you defined the serial number and prefix.

Task Sequence Progress Bar - Deploy Windows 10 21H1 Using SCCM | ConfigMgr | Step by Step
Guide
Installation Progress – Task Sequence Deployment

Let us know your experience with the issue and steps taken to resolve it in Comment Section.

About Author -> Jitesh has over 5 years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.

Resources

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.