Unsolved

This post is more than 5 years old

1 Rookie

 • 

13 Posts

33162

July 26th, 2011 10:00

Latitude E6420 error message during sysprep

We created an image for the E6420 back in May successfully. Now in July we tried to use the same image but it fails with this error message. "Windows setup could not configure Windows to run on this computers hardware"
I compared the packing slips with another E6420 that came in the first of July. I did not see any different hardware.
I started to run on board diagnostics and immediately see a different ePSA Pre Boot Assessment that comes up. So maybe this E6420 has a different chipset and BIOS.
Anyone know what the difference would be and how to resolve this? 

Update July 27: I thought I would add in some more details. This is a 32 bit Windows 7 Professional. The E6420 has the A05 bios. If I switch to ahci instead of Raid in the bios options, it will work. I guess something changed with the raid drivers. does anyone know about an update for this?

1 Message

July 26th, 2011 13:00

I too am having the exact same problem... Any help would be much appreciated! We had some E6420's shipped in June that would image perfectly, now the new shipment in July will not image. I get the same error as above!

What give?!?! :P

1 Message

July 27th, 2011 02:00

Same here.

I'm deploying a 64bit Win7 Enterprise image via SCCM 2007 OSD and I get this error. I took out all drivers from the package and still got the error. Deploying 32bit images via SCCM 2007 OSD work just fine. If I install from the 7 Enterprise DVD, it works just fine.

I've tested with 2 different E6420's so far - an i7 and an i5. The i7 is the one with the error on the 64bit image. The i5 images just fine with the 64bit image :S

I also got this error with an i7 Precision M4500, when again installing from the DVD worked fine but SCCM 2007 OSD would not. I tried the latest BIOS on the M4500 - no difference.

2 Posts

August 24th, 2011 07:00

what is the solution to this case? i have exactly the same problem

1 Rookie

 • 

13 Posts

September 13th, 2011 08:00

Same thing happening on the E6220. Any one out there from Dell? Can you acknowledge this or confirm this behavior?

2 Posts

September 13th, 2011 09:00

The solution is create a ne base image with sp1

1.1K Posts

September 13th, 2011 10:00

I haven't seen this issue and the only known sysprep issue is related to using "extendOEMpartition=1" in the sysprep.inf.

0 events found

No Events found!

Top