Start a Conversation

Unsolved

1 Rookie

 • 

41 Posts

23

July 10th, 2025 21:09

Dell Command Integration Failing to import Win10 PE Driver Packs after A35

**Importing Model based driver packs directly from the web still works**

Did the Dell team responsible for the WinPE Driver packs change after A35? We are not able to import either A36 or A37. (A37 was not even signed by Dell. Download it yourself to see.) Both of these trigger the "This is not a valid Dell library" warning in the wizard. (Yes - the file hashes match the website). If you force the wizard to continue anyway, most all the drivers fail to import.

IKU-GMD29: GetMatchingDriver: Unable to get memberID from object. Resetting the object so a new one will be created.
IKU-IID14: Exception occured in ImportInfDriver().
The following parameter or variable was invalid:
Parameter name: objectName

Error (System.ArgumentException) at IKU-IID14:
The following parameter or variable was invalid:
Parameter name: objectName

SOI-PD12: Import Driver returned a null value!
SOI-PDDPIXN05: returned an error. Cannot continue.
OSDMLIB-ISF11: Failed to import Driver into Config Manager: \winpe\x64\storage\1FC6K_A00-00\RAID_cfg\rccfg.inf 
DLMUI-GCSL01: An exception occurred: The process cannot access the file 'C:\ProgramData\Dell\CommandIntegrationSuite\Logs\OSDProcessDetails.xml' because it is being used by another process.

No Responses!
No Events found!

Top