Knowledge Base

Verifying Driver Signatures in Dell CAB Files



Users have reported issues with unsigned driver errors when using CAB files downloaded from Support.Dell.com. This will happen most often with customers attempting to use the CAB files for sysprep or System Center Configuration Manager (SCCM).




Unsigned driver messages will halt installation during sysprep, or SCCM deployment if unsigned driver warnings are enabled in either program. In most cases, these errors are related to sysprep or SCCM, as all the drivers in the Support.Dell.com CAB files are signed. If a user requests the signature status of a driver in the CAB files needs to be verified, it can be accomplished with the CAB file and an archive tool that can open CAB files, such as the freeware program 7-Zip.

The process below will be detailed using a CAB file downloaded from Support.Dell.com site, and assumes 7-Zip is installed.

  1. Right click the CAB, highlight the 7-Zip option, and click "Extract to". This creates a folder with all the files from the CAB.
  2. In the extracted folder, navigate to the driver that needs to be verified, and locate the INF file for that driver and Operating System.
  3. Move the driver files to a compatible system with the required hardware and operating system for a test installation.
  4. Manually install the driver by going to device manager, entering the properties of the device the driver is for, and selecting "Update Driver".
  5. Manually select the .inf file to force the driver update.
  6. If the driver is unsigned, a warning from Windows will appear (The unsigned driver warning is enabled in Windows by default). If this message does not appear, the driver has been signed.

*** HELPFUL LINK ***

7-Zip



Article ID: SLN80328

Last Date Modified: 08/14/2017 11:01 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Feedback shows invalid character, not accepted special characters are <> () &#92;
Sorry, our feedback system is currently down. Please try again later.

Thank you. Your feedback has been sent.