Dell Latitude E6410 - Similar computers will not boot after an image download

[Omanimous]

The computer specifications we are using for our upload:

System Manufacturer 	  Dell Inc.
System Product	          Latitude E6410
System Version	          0001
System Serial Number      
System Type	          Type: Laptop
BIOS Vendor	          Dell Inc.
BIOS Version	          A16
BIOS Date	          12/05/2013
Motherboard Manufacturer  Dell Inc.
Motherboard Product Name  0667CC
Motherboard Version	  A00
Motherboard Serial Number 
Motherboard Asset Tag	
CPU Manufacturer	  Intel
CPU Version	          Intel(R) Core(TM) i5 CPU M 520 @ 2.40GH
CPU Normal Speed	  Current Speed: 2399 MHz
CPU Max Speed             Max Speed: 4000 MHz
Memory	                  3.72 GB
Hard Disk Model           ST9250410AS
Hard Disk Firmware        D005SDM1
Hard Disk Serial Number   5VGBJ2CC
Chassis Manufacturer      Dell Inc.
Chassis Version	
Chassis Serial	         
Chassis Asset	          Not Specified

The computer specifications we are using for our download:

System Manufacturer        Dell Inc.
System Product             Latitude E6410
System Version             0001
System Serial Number       
System Type                Type: Laptop
BIOS Vendor                Dell Inc.
BIOS Version               A16
BIOS Date                  12/05/2013
Motherboard Manufacturer   Dell Inc.
Motherboard Product Name   0667CC
Motherboard Version        A00
Motherboard Serial Number  
Motherboard Asset Tag	
CPU Manufacturer           Intel
CPU Version                Intel(R) Core(TM) i5 CPU M 520 @ 2.40GH
CPU Normal Speed           Current Speed: 2399 MHz
CPU Max Speed              Max Speed: 4000 MHz
Memory                     3.72 GB
Hard Disk Model            TOSHIBA MK2561GSYN
Hard Disk Firmware         MH000D
Hard Disk Serial Number    231RTPJZT
Chassis Manufacturer       Dell Inc.
Chassis Version	
Chassis Serial          
Chassis Asset              Not Specified

General Gist:
We recently built an image; we have successfully managed to push this out to two clients, but the rest seem to just throw it away. I even recently uploaded the image again, and still will not boot. It will accept and download the image, but not boot from it.

I do not know if posting the inventory differences will mean anything, but I am assuming it is hardware related.

---

Also, I know I had a post recently about HDD-to-SSD imaging trouble. This is not related at all - entirely different issue.

[ITSolutions]

If you try to re-image the computer that you pulled the image from does it boot? If so that indicates the image is good. I would compare the BIOS settings on the machines, especially the HDD settings. I know that I have had issues that if you build the image on a machine set to ACHI and deploy to an ATA machine it will fail. Dell is really bad at have that setting being somewhat randomly assigned from the factory.

[JJ Fullmer]

Most likely @ITSolutions is right and it is a bios setting that is different. The storage options/Sata emulation setting of AHCI, IDE, and or RAID needs to match on all the computers. Just like if you change that setting after installing an operating system it won’t boot then either.

Some other possibilties…

Do you do any form or shape of sysprep? I imagine you don’t since you’re going on the same hardware and you shouldn’t need to in that case, just checking.

Have you tried booting straight to the hard drive (i.e. skipping the network pxe boot)?

Assuming this is windows, Can you boot to a windows install disk and see if the installation shows up in the repair options?
Also in a windows install disk, if this is a bios/mbr image (not efi, this doesn’t work on efi/gpt) you can try these commands in a command prompt.

#shift+F10 to bring up command prompt anytime in windows install disk
bcdboot C:\Windows
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot

Also in a windows 10 install disk you can check if the disk for some reason is not active

diskpart
list disk
#select your proper disk
select disk 0
select partition 1
detail partition
#look for active details

If these type of commands work then that’s a weird issue, but I figure why not give you all the options. I haven’t had to utilize that kind of stuff in a long time because fog takes care of mbr problems during the imaging process.

[Omanimous]

@ITSolutions That was it; I’m normally better at catching that, or leaving it set to AHCI (which most of our computers come in as) but it just never crossed my mind.

@Arrowhead-IT

1. I do not sysprep. (yet - I want to try it out)
2. I have.
3. Did not check that as @ITSolutions idea fixed it when I tried it.