Task Sequence has failed with the error code 0x80220005

Task Sequence has failed with the error code 0x80220005 – Recently I had created a task sequence to deploy Windows 7 Enterprise using SCCM, one of the SCCM engineer reported an OSD issue.

The task sequence failed with an error Task Sequence has failed with the error code 0x80220005. The issue was reported in a remote site which had a distribution point serving that site. All the task sequence content was available on the distribution point.

So far the task sequence was successfully imaging the machines, but this time it failed. The next step was to examine the log files to begin troubleshooting this issue.

I asked the SCCM engineer to check at what step the task sequence failed. I also asked him to send me the SMSTS.log file. Upon examining the SMSTS.log file I found the below error in the smsts.log file –

Error – Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.

Deployment task sequence.
Unknown error Error: 80220005; Source: Unknown
Exiting with return code 0x80220005
Process completed with exit code 2149711877

Task Sequence has failed with the error code 0x80220005

Task Sequence has failed with the error code 0x80220005

Solution – During the initial steps of the task sequence, the engineer was supposed to enter the computer name. This option was configured to make it easy for the engineer to provide a computer name of his choice and to avoid the system to auto generate a random computer name which begins with MININT for the computer.

When asked on what computer name did he enter, he mentioned that he entered BALTRAJMANSOUR01. If you notice the computer name, it’s longer than 15 characters. We know that the 16th character is always reserved to identify the functionality that is installed on the registered network device. Upon entering the computer name of less than 15 characters, the OSD was successful. I hope this post helps you. If you have any questions, let me know in the comments section.

Related Posts
Oldest Most Voted
Inline Feedbacks
View all comments

Hi Prajwal. I’m getting this same error trying to image a VM, only the machine name is 14 characters. Any other ideas?

Kardo Ameen

Thank you so much. Saved alot of time and effort.


Same occurs if you do not have the right access to add or move computers in AD

Greg Dennison

Prajwal saves the day again! Keep up the great work!


Problem solved! Thanks!

Marcin K.

Google > “sccm 0x80220005” > Prajwal’s site > problem solved. Total time 30 sec. Thnx alot 🙂


Sorted my problem. Thank you!


Jacob if you hit F8 you will get a command prompt window and you can copy it to a USB drive. Depending on what stage you are at the log file will be in different places. During OS Deployment Before your hard drive is formatted and partitioned X:\windows\temp\smstslog\ <——————————————(This is where I found it) After your hard drive is partitioned formatted X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\ Within Windows Within Windows before the SCCM agent is installed: C:\_SMSTaskSequence\logs\smstslog\ Within Windows after the SCCM agent installed: C:\windows\system32\ccm\logs\smstslog\ When the Task Sequence completes on a x86 C:\windows\system32\ccm\logs\ For x64 Systems C:\windows\SysWOW64\ccm\logs\ I… Read more »


So, how did you get the SMSTS log, if the image process failed? This is probably well-known in the community. But, I’m new to the SCCM community.


Brandon Lehman

I wish I would have found this a day earlier! I would have saved lots of hours of troubleshooting…

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More