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


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

Comments (32)

  1. Recep YUKSEL - TAT says:

    Thank you Mr. Gregg

  2. Ed (DareDevil57) says:

    Thanks.

  3. Kenton Falana says:

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

  4. Anonymous says:

    Lesson learned for the millionth time today – check the simple things first! Thanks for posting this!

  5. amergerm35 says:

    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.

  6. Holden Caulfield says:

    It Worked!!

  7. Eric says:

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

  8. Battle Angel says:

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

  9. Mur says:

    Thanks! fixed my issue

  10. mohamed hassan says:

    It Worked

  11. Jeff25 says:

    thanks…. worked for me

  12. Bruce Aderhold says:

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

  13. Glenn says:

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

  14. Chad says:

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

  15. Jason says:

    It worked. Thanks!

  16. Suddenlink Communications says:

    Who’d THUNK it was the bios! Wow…it works. Thanks for the post

  17. VNedeianu says:

    Lesson learned. Thank you!

  18. Harender Singh says:

    its working Sir, thanks you so much.

  19. Leo Zhou says:

    It works, before i changed clock, always failed lots of times, thanks very much!

  20. Billy says:

    My 2 cents. I got this same error and I found out that my OU structure had changed and my task sequence was trying to join the computer to a nonexistent OU in AD. I fixed that and I didn’t get the error anymore.

  21. Ron says:

    My 2 cents is why the heck we have the same error code for a billion different problems. Time isn’t my issue or my OU being wrong not an issue.

  22. james says:

    Ours was the server ran out of disk space

  23. Valerie says:

    This error can also be thrown if there is faulty connectivity to the network caused by anything from a loose lan cable, a non-working port on the computer, or a non-working jack in the wall. So, Besides date and time, check connectivity in general.

  24. Edward Walker says:

    That problem has been causing our IT lots of grief!! This tip fixed it!! THANK YOU !!!!!!!!!!

  25. Anonymous says:

    worked.. you’re a hero…
    time was only out by 2 mins…

  26. Sharaf says:

    Been having the error message for about a now building some enterprise WS, considering I am using a brand new USb stick for the depolyment it never crossed my mind to try another stick until this vry moment and Boom, it was the flash drive all along.

  27. jesse says:

    The fix I found was to plug in a hard line(ethernet cable)

  28. Evgeni says:

    Thanks!!!!!!!11

  29. Zlodey says:

    I had this issue. The solution was creating new usb-flash boot. PC load winpe normaly but can’t read boot partition after this wizard

  30. John Henry says:

    This error was resolved by our admins replacing the files that we copy to our USB Boot device. I tried formatting and rebuilding the drive a couple of times, then suggested the admins update the source files and that finally worked.

  31. Anton says:

    For me it was the system center server and the computer were on the same subnet.

  32. Maarten says:

    At thirst I thought my BIOS time setting was fine, but then I noticed the date was set 07-04-2016 in stead of 04-07-2016.
    So for the people who think the clocks are fine, check it again! It has to be EXACTLY the same as the forest.