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:
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
- Anonymous
January 01, 2003
Thank you Mr. Gregg - Anonymous
January 01, 2003
Thanks. - Anonymous
January 01, 2003
My clocks are on time is there any other possible cause? - Anonymous
January 01, 2003
Lesson learned for the millionth time today - check the simple things first! Thanks for posting this! - Anonymous
January 01, 2003
The comment has been removed- Anonymous
July 19, 2017
The comment has been removed
- Anonymous
- Anonymous
February 12, 2014
It Worked!! - Anonymous
February 15, 2014
Checked the Bios, time is right, still getting this error. - Anonymous
February 16, 2014
Ah biscuits... ran into this fairly recently. The solution is so simple its right up there with checking the power cord... - Anonymous
February 28, 2014
Thanks! fixed my issue - Anonymous
March 09, 2014
It Worked - Anonymous
April 08, 2014
thanks.... worked for me - Anonymous
April 09, 2014
Thanks big time! I was on verge of changing out the mobo on this Lenovo Thinkpad E430. A very simple fix thanks again. - Anonymous
May 23, 2014
Got this when the Security chip was set to the wrong mode or deactivated. - Anonymous
June 13, 2014
our issue was to suspend TPM. Once that was suspended all worked fine - Anonymous
July 23, 2014
It worked. Thanks! - Anonymous
August 11, 2014
Who'd THUNK it was the bios! Wow...it works. Thanks for the post - Anonymous
October 16, 2014
Lesson learned. Thank you! - Anonymous
November 21, 2014
its working Sir, thanks you so much. - Anonymous
January 12, 2015
It works, before i changed clock, always failed lots of times, thanks very much! - Anonymous
January 20, 2015
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. - Anonymous
February 05, 2015
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. - Anonymous
February 05, 2015
Ours was the server ran out of disk space - Anonymous
February 09, 2015
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. - Anonymous
February 23, 2015
That problem has been causing our IT lots of grief!! This tip fixed it!! THANK YOU !!!!!!!!!! - Anonymous
February 24, 2015
worked.. you're a hero...
time was only out by 2 mins... - Anonymous
March 12, 2015
The comment has been removed - Anonymous
March 20, 2015
The comment has been removed - Anonymous
March 31, 2015
Thanks!!!!!!!11 - Anonymous
April 26, 2015
The comment has been removed - Anonymous
June 14, 2016
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. - Anonymous
June 30, 2016
For me it was the system center server and the computer were on the same subnet. - Anonymous
July 04, 2016
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. - Anonymous
August 29, 2016
please Mr Gregg Outside the BIOS can I get any futher lead as I have corrected my BIOS and I am still here - Anonymous
September 15, 2016
Oh Yehhhh thanks it worked x - Anonymous
September 21, 2016
I changed bios clock with sccm server time and date but bios time will keep on changing to 3 hrs ahead, but if put same host name using other computer it worked. I tried fixed the computer. Can anyone help me fixed the problem - Anonymous
December 16, 2016
You can also get this error if the boot image you are using in the OSD process does not match what is set in the collection you are using to deploy from. - Anonymous
January 05, 2017
Hi sir,Thank you very much for this solution, it fixed my problem in task sequence error.. I glad that it worked for me.-Salute - Anonymous
January 26, 2017
Make sure the hard disk has enough space on it! - Anonymous
March 02, 2017
The comment has been removed- Anonymous
April 28, 2017
I'm exactly having the second part of your statement. I get the error right after a enter pw! But I checked my time in the bios, and it's fine... Mismatch in time?
- Anonymous
- Anonymous
May 15, 2017
I had success by changing to a different hard drive when this error occurred with a laptop today. Issue did not persist. Time was already set properly, so I'd say look at your logs if you can and don't just think changing the clock is the solution to this generic error.- Anonymous
October 24, 2017
In my case HDD was defect so Task Sequence failed by searching for disk
- Anonymous
- Anonymous
May 29, 2017
Thanks, it fixed. :-) - Anonymous
May 31, 2017
One other thing...if you make any modifications to your task sequence, make sure you deploy it to the proper device collection. - Anonymous
July 19, 2017
The comment has been removed - Anonymous
August 14, 2017
Thank you, Sir! The BIOS time was the problem! - Anonymous
September 19, 2017
Thanks for posting this tip. If this helps anyone, I loaded BIOS defaults with no change, but swapped out the HDD and success!