System Center Configuration Manager 2012 – OS Deployment Fails with Error 0x80004005

System Center Configuration Manager 2012 – OS Deployment Fails with Error 0x80004005

  • Comments 29
  • Likes

Some administrators may experience an error when trying to deploy an OS image using System Center Configuration Manager. Upon attempting to deploy the OS, a generic error is returned that does not indicate a specific cause, simply “Failed to Run Task Sequence – An error occurred while starting the task sequence. 0x80004005”. Similar to this:

error 0x80004005 with OS deployment in SCCM

This error will be thrown before any portions of the task sequence begin at all.

Though there may be many reasons for this error, a quick tip is to check the clock in the BIOS of the affected machine and ensure that it is set to match the time in the forest where the SCCM server is located. Once this is changed, the deployment should continue successfully.

Tip provided by Gregg O’Brien; posted by MSPFE editor Arvind Shyamsundar

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Lesson learned for the millionth time today - check the simple things first! Thanks for posting this!

  • It Worked!!

  • Checked the Bios, time is right, still getting this error.

  • Ah biscuits... ran into this fairly recently. The solution is so simple its right up there with checking the power cord...

  • Thanks! fixed my issue

  • It Worked

  • My clock is within a few seconds of the DC and SCCM, so that's not it. Gets through the 1st part, moves onto the second, bombs out somewhere after 85% finished. Any help would be appreciated.

  • thanks.... worked for me

  • Thank you Mr. Gregg

  • Thanks big time! I was on verge of changing out the mobo on this Lenovo Thinkpad E430. A very simple fix thanks again.

  • My clocks are on time is there any other possible cause?

  • Got this when the Security chip was set to the wrong mode or deactivated.

  • our issue was to suspend TPM. Once that was suspended all worked fine

  • It worked. Thanks!

  • Who'd THUNK it was the bios! works. Thanks for the post