Driver Injection sometimes not recognizing computer model

Good Morning,

I think you maybe using the incorrect driver pack. I would suggest going to the DIA site and download it from the site provided.

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11438.dell-family-driver-packs

search by 5250 seems it is under E6 Latitude Family search for the one for your OS.

Sorry, but this driver pack is not valid as well.

The correct model is 5250AIO and for this model, no CAB is available for WIN10, only for WIN7

Restore_Tool.log:

09.05.2017 17:29:04: ===============ssid check begin===============
09.05.2017 17:29:04: REVISION_AND_ID_TYPE_D0
09.05.2017 17:29:04:  DELL System ID:0xfe
09.05.2017 17:29:04:  DELL System ID Extension:0x079d
09.05.2017 17:29:04: BIOS_INFO_TYPE_0
09.05.2017 17:29:04:  vendor:Dell Inc.
09.05.2017 17:29:04:  version string:1.2.0
09.05.2017 17:29:04:  release date:12/26/2016
09.05.2017 17:29:04: ===============ssid check end=================
09.05.2017 17:29:04: ssidc64.exe: ExitCode: -1
09.05.2017 17:29:04: SystemID = 068F
09.05.2017 17:29:04: SystemID = 0631
09.05.2017 17:29:04: SystemID = 0632
09.05.2017 17:29:04: SystemID = 062A
09.05.2017 17:29:04: SystemID = 0644
09.05.2017 17:29:04: SystemID = 062B
09.05.2017 17:29:04: SystemID = 0645
09.05.2017 17:29:04: SystemID = 062C
09.05.2017 17:29:04: SystemID = 0646
09.05.2017 17:29:04: SystemID = 062D
09.05.2017 17:29:04: SystemID = 0648
09.05.2017 17:29:04: SystemID = 062E
09.05.2017 17:29:04: SystemID = 0649
09.05.2017 17:29:04: SystemID = 0673
09.05.2017 17:29:04: Checking if the model name matches...
09.05.2017 17:29:04: supported systems:
09.05.2017 17:29:04: filereadSupported[1] = 3150,3450,3550,E5250,5250,E5450,5450,E5550,5550,7350,E7250,7250,E7450,7450
09.05.2017 17:29:04: filereadSupportedModels = "3150"
09.05.2017 17:29:04: filereadSupportedModels = "3450"
09.05.2017 17:29:04: filereadSupportedModels = "3550"
09.05.2017 17:29:04: filereadSupportedModels = "E5250"
09.05.2017 17:29:04: filereadSupportedModels = "5250"
09.05.2017 17:29:04: filereadSupportedModels = "E5450"
09.05.2017 17:29:04: filereadSupportedModels = "5450"
09.05.2017 17:29:04: filereadSupportedModels = "E5550"
09.05.2017 17:29:04: filereadSupportedModels = "5550"
09.05.2017 17:29:04: filereadSupportedModels = "7350"
09.05.2017 17:29:04: filereadSupportedModels = "E7250"
09.05.2017 17:29:04: filereadSupportedModels = "7250"
09.05.2017 17:29:04: filereadSupportedModels = "E7450"
09.05.2017 17:29:04: filereadSupportedModels = "7450"
09.05.2017 17:29:04: U:\Dell_Driver_Packs_Local\WIN10_LATITUDEE6_A10.ZIP.ZIP ist nicht gültig für das ausgewählte Modell: 5250AIO.
09.05.2017 17:29:04:
09.05.2017 17:29:04: WIN10
09.05.2017 17:29:04: x64
09.05.2017 17:29:04: 5250AIO
09.05.2017 17:29:19: Checking if there are any Driver Packs to copy... COMPLETED
09.05.2017 17:29:19: Check if DriverCAB_Folder exists if so kick off the driver injection tool...
09.05.2017 17:29:19: Check if DriverCAB_Folder exists if so kick off the driver injection tool... COMPLETED

I am sorry are you using Dell Image Assist if so then the driver link I provided is correct and there is a driver for the 5250 AIO for WIN10. CABs are of the past for Old computers as mentioned before perform a search for 5250 and you will find the right ZIP. If you are not using DIA then I will not be able to assist you,

if needed you can reply to the US_OSImaging@Dell.com mailbox with contact information

thank you,

I am using Dell Image Assist.

1. I'm booting from USB stick.

2. Selector Tool (3.1.01) is starting.

2. I'm selecting recovery tool (5.7.0.7).

3. I'm connecting a network drive (with WIM file).

4. I'm choosing a driver package with "Add Driver Packgage" (e.g. http://downloads.delltechcenter.com/DIA/Drivers/win10_latitudee6_a10.zip)

5. I start recovery.

6. When it comes to driver injection, the error message "Driver Package is not valid for selected model" is displayed.

Imho the id is not the right one. My computer is a 5250AIO, the driver just supports an id 5250 without AIO.

Hi,

Thanks for your feedback and glad to hear this is resolving your issue. In the meantime the typo's on the website regarding this driverpack have been fixed and show the correct supported systems.  

Best regards,

Hendrik Rijkens

Thanks a lot, this is the correct driver package.

Now everything works fine.

Best regards