Comments on: Build and Capture Task Sequence Failure http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/ Jarvis's Ramblings Sun, 20 May 2012 08:02:58 +0000 hourly 1 http://wordpress.com/ By: Neonteepee http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1358 Tue, 18 May 2010 09:25:48 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1358 You rock – this was driving me nuts – especially seeing as I am running all this on a laptop at a clients site

]]> By: Mark http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1354 Fri, 14 May 2010 11:01:29 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1354 Thanks, i had the same error! Solved

]]> By: Dale http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1186 Fri, 08 Jan 2010 23:35:08 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1186 THANK YOU JARVIS!!! SOLVED

]]> By: Jarvis http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1109 Mon, 23 Nov 2009 13:23:32 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1109 I haven’t seen drivers cause this problem, however this post is about the build and capture task sequence which you use to create the image that will be used with the deploy task sequence. There shouldn’t be any reference to hardware models for driver management in this task sequence. The image should always be built on a virtual machine to eliminate the extraneous drivers from the image.

]]> By: Jay Connor http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1101 Sat, 21 Nov 2009 05:11:00 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-1101 It can be drivers causing this problem. In the apply drivers task limit to the model.

]]> By: Tubs http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-964 Tue, 25 Aug 2009 13:46:52 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-964 Holy moly. What a bloody waste of 3 days. Grrrrrrrrr. Having tracked down the hidden logs files in x:\windows\temp\smstslog\windowssetuplogs\, this basically confirms my hunch. Thanks for the post.

PS: Why can’t the error messages be more thoughtful? Or at least give us trace32.exe for x64 in WinPE! Oh, and how about putting the logs altogether Microsoft!

]]> By: W. Wolting http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-960 Wed, 19 Aug 2009 10:02:09 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-960 leaving the licence code field empty worked for me. I’ve had this problem with windows 7 x64

]]> By: Joachim http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-925 Mon, 29 Jun 2009 09:51:49 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-925 Hi Jarvis

brilliant. I took me a couple of day to solve all the other issues I had and only a blink for this fault due this blog.

Thanks
Joachim

]]> By: a.kamman http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-623 Wed, 21 Jan 2009 15:10:51 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-623 hello everybody,

i love this post. we added to much drivers to our TS. i deleted them and the Build and Capture Task Sequence Failure was gone. the 0×80004005 error wasn’t there anymore. now i can test the rest of the setup proces.

]]> By: Daniel http://verbalprocessor.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-525 Fri, 03 Oct 2008 02:28:14 +0000 http://verbalprocess.wordpress.com/2008/02/27/build-and-capture-task-sequence-failure/#comment-525 Thankyou very much! This has been driving me nuts for days :)

]]>