Build and Capture Windows 7 64-bit SP1

[Vallaqan]

I've been scouring these forums and the Internet for a solution to my problem. I have a 32-bit Win7 SP1 task sequence which runs perfectly. It builds the machine, install 3 applications, installs all Windows/Office updates and captures the machine as shown.

 

The same configuration works for the 32-bit but here's the info on the "Setup Windows and Configuration Manager" step:

 

I've tried to create another task sequence to create a 64-bit image but it drops me to the Administrator login screen after the first round of updates. It installs around 150 updates first and then it reboots and goes to the black "Applying update operations" screen. It then starts back up and continues with the "Install Updates I" step. Then it appears to randomly reboot and drops me at the Administrator login screen.

 

I've attached my smsts logs and my WindowsUpdate log in case either of them are helpful. I've also run the task sequence completely by removing the software updates and then it completes successfully. Again, the 32-bit version of the task sequence also runs perfectly and I just copied that one to create the 64-bit one.

 

smsts.logsmsts-20140423-181549.logWindowsUpdate.log

 

I found this Microsoft article (http://support.microsoft.com/kb/2894518/en-us) and removed these updates from my software update groups in case that was the problem. My Windows 7 box is definitely still in Provisioning mode when it drops to the login screen. I just don't see any obviously errors by looking at this. Any help anyone can provide would be awesome.

[Vallaqan]

I noticed it is using the x86 boot image. Does that matter?

[anyweb]

if you want to build and capture windows 7 X64 then you need a 64 bit boot wim,

 

for deploying either OS (unless UEFI) you can use an x86 boot wim.

[Vallaqan]

Strangely, my last test run as I was heading home last night I just copied the x86 task sequence again and made a couple changes to create a 64 bit image and it went through flawlessly. The new task sequence is using the x86 boot wim too. Both 64 bit task sequences look identical so that's confusing. I'm deploying it to a test machine right now so I'll report back how that turns out.

 

Side note: All your guides have been tremendously helpful in getting me this far so thank you. We actually just started our client migration from 07 to 2012 since everything is basically set up including old packages as well as new applications, driver packs and the main 32-bit B&C image we'll be using. We'd been using Ghost up til now including about 7 different images for the various computer models.

[Vallaqan]

The 64-bit B&C image seems to have worked fine. It's got all the updates aside from the few I removed based on the MS link.

 

Really strange. I took another look at both task sequences and they appear identical.