Pro Max Slim FCS1250, Dell Command drivers fail to extract

Question

I am attempting to download the Dell Command Drivers for the Dell Pro Max Slim FCS1250 (Windows 10).

The File (FCS1250-81FC2_Win10_1.0_A02.exe) Is detected as an Unrecognized App by Windows Defender. Bypassing this, I can access the extractor. However, the Extractor Crashes after 4 seconds. Then Gives an unhelpful "Extraction was not successful". Clicking the "View installation Log" shows it didn't log anything.

I have opened up a ticket with Dell Support, [Case : 217647728] [ thread::BryRowv7J32lWhVlno9AKj0:: ]

However they consistently informed me they would "Check with our resources" and never reply back.

Today they informed me they have closed my ticket without resolution and to not reply to the e-mail.

I've used similar Dell Command extractors just like this one that run perfectly! So I do not understand why this ONE file won't work, and I can't get any help.

ElwinNetworking · Answer

Same issue here. The A02 package seems to have a broken signature which causes SmartScreen to block it and the extractor to fail. Try right-clicking the file, open Properties, click Unblock if shown, then run as Administrator. If it still fails, extract it manually with 7 Zip since it’s just a self-extracting archive. Looks like Dell needs to republish this build.

Jammer2omega · Answer

@ElwinNetworking​ Thank you for the help! I attempted to extract the files, but I get a .rsrc folder, with a manifest inside. It looks like the drivers are still contained inside a file named: [0] ((at 2.8gb)). Attempted to extract that with 7zip leads to a 'Cannot open file as archive' Forgive my ignorance but what can I do from here?

ElwinNetworking · Answer

Hey @Jammer2omega,

You’re right about the [0] file. It isn’t a normal archive but a resource container inside the Dell self-extracting executable. That’s why 7-Zip can’t open it. Try this first. Open Command Prompt as Administrator, go to the folder where the .exe is located, and run

FCS1250-81FC2_Win10_1.0_A02.exe /extract C:\DellDrivers

This command forces the Dell Update Package to unpack its files manually, even if the graphical extractor fails.

If it still doesn’t work, download the equivalent Dell Command Deploy Driver Pack for the same model. These are provided as .cab files that you can open directly with 7-Zip or the expand command.

You can find them here:
https://www.dell.com/support/kbdoc/en-us/000177325/dell-command-deploy-driver-packs

If both methods fail, the A02 package is likely corrupted or has a broken digital signature. Dell will need to re-upload a fixed version of the file.

Jammer2omega · Answer

@ElwinNetworking​  Even command line wasn't working. However, it looks like Dell updated the files between November 6th and today. The file name hasn't changed but extraction is working perfectly now. Thank you for all your help!

CarpenterIT · Answer

Looks like the most recent A03 update is also not signed. What is happening here?

FCS1250-TW19T_Win11_1.0_A03.exe

https://www.dell.com/support/kbdoc/en-tt/000303361/dell-pro-max-desktops-fcs1250-windows-11-driver-pack

```

PS C:\> signtool.exe verify C:\Users\x\Desktop\FCS1250-TW19T_Win11_1.0_A03.exe
File: C:\Users\x\Desktop\FCS1250-TW19T_Win11_1.0_A03.exe
Index Algorithm Timestamp
========================================
SignTool Error: No signature found.

Number of errors: 1

```

Couldn't figure out why my latest OSDCloud deploys were failing.

CarpenterIT · Answer

I opened a support ticket with Premier support and it took a while for them to understand it was a source file issue not an issue with my system. The next day I was contacted and they said it was resolved and they couldn't reproduce. I pulled the new file and the checksums didn't match so Dell definitely updated it with no change to the name or version. It bothers me that this was even publicly distributed unsigned.

Dell Pro Desktops

Pro Max Slim FCS1250, Dell Command drivers fail to extract

Was this post helpful?