Current Driver CAB Summary
Driver CABs Homepage | Understanding Delta Report
Delta Report for Previous Driver CAB v/s Current Driver CAB
(8Y9DR-A08-10/10/2017) v/s (24WYX-A09-03/27/2018)
Creative Labs Sound Blaster Recon3D PCIe Audio Card Driver
Realtek High-Definition Audio Driver
Intel USB 3.0 eXtensible Host Controller Driver for C610 series Chipset Family
Intel Chipset Device Software
Intel Turbo Boost Max Technology Driver
Intel(R) Management Engine Components Installer
Dell PCIe Serial Card Driver for Windows
Dell USB Smartcard Keyboard Driver
Thunderbolt(TM) Driver for Windows
Intel 10 Gigabit X540 Adapters Driver
Intel I2xx/825xx 10/100/1000 Ethernet Network Drivers
Dell Data Protection|Encryption v8.5.1
Dell Data Protection | Encryption
Intel Rapid Storage Technology enterprise Driver and Management Console
Intel HHHL PCIe Solid State Drive Driver
Intel PCIe Solid State Drive Driver
Windows 7x64 Drivers for LSI 9341-8I/9361-8I controller
Teradici 1 and 2 PCoIP Host Card Windows 7/8.1 64bit Driver
AMD FirePro Driver 16.40 for Windows 7, Windows 8.1, and Windows 10 (32 and 64 bit).
NVIDIA Quadro Driver 369.39 for Windows 7 (64-bit) and Windows 8.1 (64-bit).
AMD FirePro Driver 16 50 2701 for Windows 7 and Windows 10 64 bit
NVIDIA Quadro Graphics Driver
Windows 7x86 Drivers for LSI 9341-8I/9361-8I controller
Windows 7x86 Driver for LSI 9361-8I Controller
Teradici 1 and 2 PCoIP Host Card Driver
NVIDIA Quadro Driver 369.39 for Windows 7 (32-bit) and Windows 8.1 (32-bit).
The Intel Ethernet Connection I217-LM (Driver Version: 03/13/2014,18.104.22.168 ) for Windows 7 x64 appears to be causing issues during imaging or if you manually install it on a vanilla Windows 7 install.
The connection will randomly stop working and it cannot contact the DHCP server so it assigns a 169.x.x.x IP address.
After downloading the newer version from Intel (Driver Version: 09/29/2014,22.214.171.124) we have been able to image without seeing that IP/DHCP issue.
I concur with Danny. I was having many issues with T5810 not joining the domain via a SCCM 2012 Task Sequence that utilized unattended domain join. The Intel Ethernet Connection I217-LM (Driver Version: 03/13/2014,126.96.36.199 ) that's included in this CAB causes random issues. The driver version directly from Intel (Driver Version: 09/29/2014,188.8.131.52) resolved all my issues. Specifically reference the e1d62x64.inf.
I agree too.
Took help from
Having so much of problem installing Driver Package on Precision T5810 via SCCM on an enterprise level. CAB file from Dell seems to be OK but while installing Driver package it is not picking up from Task Sequence.
Following is what we've found, which finally resolved our issue :-
It seems that Dell has changed their standard for naming client devices, so instead of naming it “Precision T5810”, they have named it “Precision Tower 5810”.
This information can be found by:
1. Open Command Prompt on target system
2. Write "wmic csproduct get name"
The name returned must be used in the SCCM Task Sequence wmi query for identifying the system for driver installation package.
If “true”, driver package is installed, if “false”, driver package is skipped.
In our case since the name did not match, the result was “false” and the driver package was skipped.
I had the same issue with the network driver bundled in this Driver Pack. My PCs were booting up with a 192.168.x.x IP address. Downloading the latest driver from Intel got my OSD process back up and running. Thanks to Danny and jgaryj for posting specifics.
Anybody experiencing what seems like poor hard drive performance after re imaging one of these systems using the latest Windows 7 Driver Pack? We just got a batch of these in and I loaded our standard Windows 7 Enterprise x64 image onto it via MDT using this driver pack (A03). The systems have two hard drives connected via the Intel controller but the system aren't configured for RAID, just two independent disks. It took over 5 hours to lay the image down on these systems (a process which takes only an hour or two on others) and software installations after the fact are incredibly slow (such as a simple install or Premiere Pro CS6 taking over an hour to do what is usually accomplished in 15 minutes). The hard drive light on the system stays on constantly during installation.
I've checked with both Dell and Intel and there is no newer version of the Intel RST-e drivers available. I am trying the normal RST drivers to see if there is any improvement. There doesn't appear to be any previous versions of the RST-e drivers available on the download page for these systems either.
I was just troubleshooting an imaging issue where the drive wasn't showing up in WinPE fast enough after the first reboot and the task sequence would time out. I tracked it down to being an issue with the SATA OPERATION, everything worked when I set it to AHCI.
Have you tried setting the SATA OPERATION to AHCI to see if system performance is back to normal?
Yes, the first thing I tried was setting the drives to AHCI mode instead of RAID on to see if that made any difference and it did not. I installed the latest version of the Intel RST drivers direct from Intel which seems to have sped things up again. I want to confirm that though, so I am laying my image out onto the machine with the original settings back in place (RAID on) and then I will install the RST drivers without making any other changes and test again.
After about 1.5 hours or so I stopped the process as it was still only at pass 1 of applying updates before installing our applications. I've added the latest consumer Intel RST drivers to my MDT server and changed the drive operation in the BIOS to AHCI and I've started the imaging process once more.
I also notice that BIOS version A08 was recently released so I tried it on one of the other machines, but still no improvement of speed there.
So what I ended up doing was setting the drive mode to AHCI in the BIOS and then loading the latest Intel RST f6flpy driver (downloadcenter.intel.com/.../Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver) into the driver list for the Precision T5810. I then ran my deployment on the machine again and now HDD operations are working at an expected pace. The addition of that driver and the change to AHCI did allow the system to detect a new Drive Controller in the Device Manager to which the HDDs are attached.
I looked at one of the machines which still had the factory Windows 7 Pro install from Dell on it and all of our driver versions matched up to what I had before adding the f6flpy driver. There must be something else at play here preventing this from working with my Windows 7 Enterprise build. Perhaps one of the bundled pieces of Dell software on the factory build is missing in the Enterprise build? I don't know and I don't have alot of time to investigate either.
One other interesting behavior with this driver pack is that the Audio driver for the Realtek HD is newer that what is provided on the Dell download page for the system. With this newer driver installed, every time the machine goes to sleep you get a message when resuming that the BIOS configuration has changed and you need to restart.
Removing the Realtek driver installed from the A03 from the system and then installing the older version of the Realtek drivers fixes this issue.
I ran into an issue with the T5810 driver cab after A00, when an SSD is installed in place of the standard HDD. The issue is that the device would not reboot during the deployment phase (using MDT) or even after the image is fully installed. It will shutdown and start back up properly but if a system restart is initiated, it just sits in a perpetual wait state.
I found out that after A00, the Intel PCIe SSD driver, version 184.108.40.2063 was added. If I use A00 or if I remove/disable this driver, the system reboots properly.
I found this behavior with either a Hynix 256 GB SSD or a Crucial 512 GB SSD. The BIOS drive operation setting was left as is, which is RAID ON. FYI, I tried both ATA and AHCI and neither solved this issue.
I am installing W7 in MDT environment, loaded A05 cab. after the first restart of windows computer stops with a black window "windows failed to load because a critical system driver is missing, or corrupted."
I am using A07 and received the same error as artoaper. I have tried removing all the drivers from MDT for this model and reimporting. I have tried deleting the megasys2 drivers but nothing is working. It just keeps giving us the same error right after the OS install reboot.