Dell Drivers no longer able to extract

[Ru66erDucky]

Using 7.0.4 and also tried 7.1.1 Dell driver no longer extract. It seems Dell changed from CAB to EXE and doesn't know how to extract driver now. Models impacted are Latitude 9420 and 9430.

[WhaleOfATimeProductions]

I'm seeing the same issue with the Latitude 7420.

It seems to relate the 2GB .CAB file limit mentioned on this page within Dell's support site: https://www.dell.com/support/kbdoc/en-uk/000197955/file-format-change-of-dell-command-deploy-driver-pack-from-cab-to-dup

Using the command "7420-p5m13_win10_1.0_a09.exe /s /e=d:\LocationToExtractFiles extracts the files usually found within the CAB files. It totals ~3.2GB

I've then gone through the process of creating a custom package for the device using the details that were applied to the package previously created.

Looking at the catalogue there are a number of Dell devices which have now switched to the DUP .exe format so this issue is likely to grow. Here is an image of the 7420 entry within the catalogue, I've also checked online for the latest catalogue driver pack and it is the file listed.

[WhaleOfATimeProductions]

This is the first time I'm using the custom package creation process so I may be doing something wrong, but it doesn't seem to respect the settings we use for the automated driver update import process. Deployment Platform is set as "ConfigMgr".

For example we use .WIM files as containers for the drivers to avoid copying lots of individual files, and have the folder structure within MECM as follows, but instead the custom package is placed in the root Packages folder: Packages -> Driver Packages -> Dell

Is this expected behaviour or is there a way to force the custom packages to conform to the settings enabled in ConfigMgr Settings tab?

[Ru66erDucky]

What I did so far is to extract the files manually place in the catalog folder where it suppose to extract, and re-run the job. That actually moves the files, and created the standardpkg for me. However, the version # is messed up. It is showing the model # now instead of the CAB version. I am not using WIM format - still using just files, and have not validate dynamic driver is working or not. Someone else mention issue with the WIM file created, and they had to mount the WIM and correct versioning. Hope this help - https://github.com/maurice-daly/DriverAutomationTool/issues/351

[WhaleOfATimeProductions]

The trick of putting the files in the source folder is good to know, thanks for sharing. I've tested the manual package I created and can confirm that is working during the imaging process.

Regarding the version number issue you mentioned, I saw that same issue for the 7420 and it looks like Dell have used the model number instead of driver pack version in the catalogue as well as the knowledge page.

I expect if you compare a .cab entry in the catalogue XML file I mentioned above with the .exe entry you could work out which property needs editing to the correct version number to fix this issue. I've successfully modified the XML file in the past when dell mixed up the download links for .cab files.

[TazwellJ]

Seeing the same issues. Both with the .exe packages and the incorrect version naming.

[WhaleOfATimeProductions]

It looks like Maurice has uploaded a new beta version of the tool with fixes for the Dell packages.

Has anyone already tried version 7.1.2?

[TazwellJ]

Not yet but about to download it now.

[TazwellJ]

7.1.2 beta appears to have fixed the issue. It's successfully extracting drivers from exe files now. Also seems to be setting the version correctly when it creates the SCCM package.

[WhaleOfATimeProductions]

Thanks for testing, I'll hopefully get round to updating it in our environment Tuesday/Wednesday. Big thanks to the Devs as always!

[carvius87]

Hi everyone, i also installed 7.1.2 beta and now everything works fine. Modellnumber is Ok and the Packages looking good. A testinstallation was succesful.

BR

[hudyscott]

Hey, I've tried the 7.1.2 but it's still not working for me....I've tried it on Latitude 5530 & 5430. Here's a pic of the log file

What's interesting is that I can download optiplex 3000 drivers & bios just fine.....

Here is the powershell error

[hudyscott]

So I figured it out....Not ALL the dell drivers/bios are converted to DUP....So I used MSEndPointMgr v6.4.9 & was able to download, extract, and package that I needed to.....

[DewayneHyatt]

The 5430 is working for me now (7.5.1 beta) however the 5530 still appears to be broken in the catalog provided by Dell. It's also interesting to note that the Dell catalog is .exe yet the actual driver is a .cab. This sort of thing basically aligns with the quality of service we've been getting from Dell recently so not surprised.

URL in catalog: https://downloads.dell.com/FOLDER08578384M/1/Latitude-5530-JX5TP_Win11_1.0_A01.exe

Actual URL: https://downloads.dell.com/FOLDER08282229M/1/Latitude%205530-win11-A00-XW1KG.CAB

[DewayneHyatt]

Dell corrected the error in their xml regarding the 5530. I was able to use DAT to download and extract (still running 7.5.1 beta). The updated catalog is back to cab files for the 5530 rather than exe.

[hudyscott]

Great, thx

Hudy Scott PC Technician CURO Financial Technologies Corp t. 316.425.1330 c. 316.706.7187

From: Dewayne Hyatt @.> Sent: Thursday, July 7, 2022 7:29 AM To: maurice-daly/DriverAutomationTool @.> Cc: Hudy Scott @.>; Comment @.> Subject: Re: [maurice-daly/DriverAutomationTool] Dell Drivers no longer able to extract (Issue #353)

CAUTION: This email was sent from outside the organization @.**@.>). Do not click links or open attachments unless you recognize the sender and know the content is safe.

Dell corrected the error in their xml regarding the 5530. I was able to use DAT to download and extract (still running 7.5.1 beta). The updated catalog is back to cab files for the 5530 rather than exe.

- Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaurice-daly%2FDriverAutomationTool%2Fissues%2F353%23issuecomment-1177533383&data=05%7C01%7CHudyScott%40curo.com%7C0604527f3ebf418d68aa08da6014530b%7C2dc14abb79414377a7d259f436e42867%7C1%7C0%7C637927937661954476%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YDlGeMrDuG9Nol8BW9Ebi4wROeO%2BPD9bYKqiKO7xTI0%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP3I2S7NOYPDOIZ2Q2YBGC3VS3ESBANCNFSM5YLZRFRQ&data=05%7C01%7CHudyScott%40curo.com%7C0604527f3ebf418d68aa08da6014530b%7C2dc14abb79414377a7d259f436e42867%7C1%7C0%7C637927937661954476%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uMROjQtK12jKkAmgVU9xwG1daU04qm5S4fQWTzuUOW4%3D&reserved=0. You are receiving this because you commented.Message ID: @.**@.>>

[MiketheMaker18]

Still having this issue in 7.1.7. @maurice-daly are you going to wait on Dell to fix this or plan to figure out some sort of if-then for cab vs exe? Thank you!

[hudyscott]

What I figured out was that Dell had the wrong folder listed in their XML....You can actually paste the path into a Browser & see if the file exists....So when I did that I found out the folder doesn't even exist.....

So this has multiple issues......

First check to see if the file even exists & verify the extension....

To answer your question.....I haven't had time to look into trying to fix this.....

Hudy Scott IT Technician | Community Choice Financial Direct: 316-425-1330 @.**@.> PLEASE NOTE: Speedy Cash, Rapid Cash and Avio are now part of the Community Choice Financial family of companies [cid:11671b43-a302-4a02-9c46-54475278bfcd]

---

From: Mike Pluff @.> Sent: Thursday, September 1, 2022 11:41 AM To: maurice-daly/DriverAutomationTool @.> Cc: hudyscott @.>; Comment @.> Subject: [External]Re: [maurice-daly/DriverAutomationTool] Dell Drivers no longer able to extract (Issue #353)

CAUTION: External Email This email has originated from outside of the organization. Do not click any links or open any attachments unless you have verified the sender and know the content is safe.

CAUTION: This email was sent from outside the organization @.***). Do not click links or open attachments unless you recognize the sender and know the content is safe.

Still having this issue in 7.1.7. @maurice-dalyhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaurice-daly&data=05%7C01%7Chscott%40ccfi.com%7Cf57369c6fcda4698fd5308da8c38e6ab%7C1773e9f4954c4747a4534bd6405b5a14%7C0%7C0%7C637976474204316240%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=LTd%2BcqDYf197tRwEjpqhRZyNqHnrlYHm0iYcWpQQeIU%3D&reserved=0 are you going to wait on Dell to fix this or plan to figure out some sort of if-then for cab vs exe? Thank you!

— Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaurice-daly%2FDriverAutomationTool%2Fissues%2F353%23issuecomment-1234526882&data=05%7C01%7Chscott%40ccfi.com%7Cf57369c6fcda4698fd5308da8c38e6ab%7C1773e9f4954c4747a4534bd6405b5a14%7C0%7C0%7C637976474204316240%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=im7eDuRZcXNM7In35Hd3Npg2PqbXK1pn6laYtGZBL2E%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP3I2SYVVJNXTOJTICT2BTLV4DME5ANCNFSM5YLZRFRQ&data=05%7C01%7Chscott%40ccfi.com%7Cf57369c6fcda4698fd5308da8c38e6ab%7C1773e9f4954c4747a4534bd6405b5a14%7C0%7C0%7C637976474204472509%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=oVrcK%2FFUDERs8qFYItbXw52HW9WjWxwk0oMHDc%2FuZvk%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>

[MiketheMaker18]

It's just the extraction process. If DAT doesn't see a CAB file after the download and before extraction, run exe extraction command before the ps import step. Shouldn't be too hard to program that in, but with that said I haven't had time either.

[hudyscott]

I agree but there was no file.....at least on the one I was working on....

Hudy Scott IT Technician | Community Choice Financial Direct: 316-425-1330 @.**@.> PLEASE NOTE: Speedy Cash, Rapid Cash and Avio are now part of the Community Choice Financial family of companies [cid:43b11ffc-1508-4545-989f-dc7b1936575c]

---

From: Mike Pluff @.> Sent: Wednesday, September 7, 2022 10:56 AM To: maurice-daly/DriverAutomationTool @.> Cc: hudyscott @.>; Comment @.> Subject: [External]Re: [maurice-daly/DriverAutomationTool] Dell Drivers no longer able to extract (Issue #353)

CAUTION: External Email This email has originated from outside of the organization. Do not click any links or open any attachments unless you have verified the sender and know the content is safe.

CAUTION: This email was sent from outside the organization @.***). Do not click links or open attachments unless you recognize the sender and know the content is safe.

It's just the extraction process. If DAT doesn't see a CAB file after the download and before extraction, run exe extraction command before the ps import step. Shouldn't be too hard to program that in, but with that said I haven't had time either.

— Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaurice-daly%2FDriverAutomationTool%2Fissues%2F353%23issuecomment-1239582869&data=05%7C01%7Chscott%40ccfi.com%7C8f6598fa2d3f4065783108da90e99925%7C1773e9f4954c4747a4534bd6405b5a14%7C0%7C0%7C637981631103677341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9TE3gQ%2FtVCN36CMbvTO4xl6GpqL2J3IzUEry5WOT3r8%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP3I2SYATCVNH4OQT6Y4JBDV5C3MBANCNFSM5YLZRFRQ&data=05%7C01%7Chscott%40ccfi.com%7C8f6598fa2d3f4065783108da90e99925%7C1773e9f4954c4747a4534bd6405b5a14%7C0%7C0%7C637981631103677341%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=sZ6%2BYQseXCiLIskayuhmkKdivz8l%2BzECBvmZMAA8Fvo%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>

[MiketheMaker18]

Hmm that's odd. Using 7.1.7 (issue started for me i think 7.1.2), it's either downloading the CAB or EXE (Dell models), but when it extracts the EXE to the extraction folder, it just copies the EXE instead of actually extracting it. It shows success when importing into MDT, but obviously MDT won't import an exe as drivers. I've just been manually extracting the EXE's and importing them.

[agbrint]

Using >7.1.7 I am able to pull down the newer EXE files and successfully extract them, however we (multiple groups running independent CM/DAT installs) are seeing a pop-up security dialog relating to the extraction of the files on Windows Server 2019 systems. Selecting OK at the prompt will successfully extract the files as expected and continue on with the process, successfully creating a driver package. Selecting Cancel at the prompt will not extract the files and attempt to create a 0k package (which fails to distribute or install drivers). My best guess without digging into the code myself is that it's running in a separate process which is not inherently "elevated" such as the DAT exe is on our systems. Options such as lowering or disabling UAC not an option in our environments.

[maurice-daly]

Unfortunately this is due to a change in the way Dell provides the driver packages. Today they are delivered in priority EXE format. The new version of the tool can extract these however.

[hudyscott]

Thanks for the info & you hit the nail on the head about dell. I'm looking for the win10 drivers & not the Win11 drivers..... How did you get/find the correct Win11 driver path?

Hudy Scott PC Technician CURO Financial Technologies Corp t. 316.425.1330 c. 316.706.7187

From: Dewayne Hyatt @.> Sent: Monday, June 27, 2022 3:30 PM To: maurice-daly/DriverAutomationTool @.> Cc: Hudy Scott @.>; Comment @.> Subject: Re: [maurice-daly/DriverAutomationTool] Dell Drivers no longer able to extract (Issue #353)

CAUTION: This email was sent from outside the organization @.**@.>). Do not click links or open attachments unless you recognize the sender and know the content is safe.

The 5430 is working for me now (7.5.1 beta) however the 5530 still appears to be broken in the catalog provided by Dell. It's also interesting to note that the Dell catalog is .exe yet the actual driver is a .cab. This sort of thing basically aligns with the quality of service we've been getting from Dell recently so not surprised.

URL in catalog: https://downloads.dell.com/FOLDER08578384M/1/Latitude-5530-JX5TP_Win11_1.0_A01.exehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownloads.dell.com%2FFOLDER08578384M%2F1%2FLatitude-5530-JX5TP_Win11_1.0_A01.exe&data=05%7C01%7CHudyScott%40curo.com%7C51694c43f285454c662308da587bf4e2%7C2dc14abb79414377a7d259f436e42867%7C1%7C0%7C637919587270537042%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YkHEbgKH%2BVJkHtxUmxzc7YEYShGsPrRe9qYwTr%2FnBsM%3D&reserved=0

Actual URL: https://downloads.dell.com/FOLDER08282229M/1/Latitude%205530-win11-A00-XW1KG.CABhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownloads.dell.com%2FFOLDER08282229M%2F1%2FLatitude%25205530-win11-A00-XW1KG.CAB&data=05%7C01%7CHudyScott%40curo.com%7C51694c43f285454c662308da587bf4e2%7C2dc14abb79414377a7d259f436e42867%7C1%7C0%7C637919587270537042%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DmT%2F1Kt7ox2igYqlMTzNNFTfnvm6f9gZORVfeWSGHK8%3D&reserved=0

- Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmaurice-daly%2FDriverAutomationTool%2Fissues%2F353%23issuecomment-1167854334&data=05%7C01%7CHudyScott%40curo.com%7C51694c43f285454c662308da587bf4e2%7C2dc14abb79414377a7d259f436e42867%7C1%7C0%7C637919587270537042%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Dul5j%2Bze8KObSuLbH6DKXfkAC97zfr08QsgvAauYs9E%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAP3I2S6DTACPOV3UAU5CRO3VRIFOFANCNFSM5YLZRFRQ&data=05%7C01%7CHudyScott%40curo.com%7C51694c43f285454c662308da587bf4e2%7C2dc14abb79414377a7d259f436e42867%7C1%7C0%7C637919587270537042%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ljamjsf7swOPAW8nnqz79CkiiJZZqjMESJcNu9hTQqg%3D&reserved=0. You are receiving this because you commented.Message ID: @.**@.>>