Current Driver CAB Summary
Driver CABs Homepage | Understanding Delta Report
Delta Report for Previous Driver CAB v/s Current Driver CAB
(W6WV9-A19-03/14/2016) v/s (CT5DP-A20-04/12/2016)
Intel(R) Thunderbolt(TM) Controller Driver
ASMedia USB 3.0 Extended Host Controller Driver for Dell Thunderbolt Dock
Intel I2xx/825xx Gigabit Ethernet Network Controller Drivers
Bizlink USB3.0 GBE Dongle Driver
Broadcom 57XX/BACS Combined Package Driver
Intel 10 Gigabit X540 Adapters Driver
Intel 825xx Gigabit Platform LAN Network Device, v.10.0.6.0, A01
Intel USB 3.0 eXtensible Host Controller Driver
Realtek PCIe GBE Family Controller Driver
Intel USB 3.1 eXtensible Host Controller Driver
Intel I2xx/825xx 10/100/1000 Ethernet Network Drivers
Realtek PCI-E Gigabit Ethernet Controller Drivers
Intel 825xx Gigabit Platform LAN Network Device, v.188.8.131.52, A03
Realtek USB GBE Ethernet Controller Driver
Intel Rapid Storage Technology enterprise Driver and Management Console
PERC H730P/H330 Drivers for Win7 x64
Fresco Logic xHCI (USB3.0) Controller Driver
Intel Rapid Storage Technology Driver and Management Console
Intel Rapid Storage Technology Driver
LSI SAS2308 and LSI SAS9217-8i Windows 7 x64 driver
Dell Perc8 H710P/H310 Driver
LSI SAS3008 Windows 7 64 bit driver
LSI 9361 Drivers for Windows 7- 64
Broadcom 57XX Driver/BACS Combined Package Driver
LSI 9361 Drivers for Windows 7- 32
LSI SAS3008 Windows Drivers for Win7-32
Dell PowerEdge RAID Controller Driver
PERC H730P/H330 Drivers for Win7 x86
LSI SAS9271-8i Windows 7 32 bit driver
LSI SAS2308 and LSI SAS9217-8i Windows 7 32-bit driver
I used this CAB for MDT 2012 PE and none of my Optiplex systems were able to detect their internal hard drives. Tried it on 780 and 760, and also on a new Latitude E7440. Not sure why this happened but I had to revert to using the complete driver sets for each model in the PE and that works fine now.
I had issues with this cab as well when updating winpe 3.0 images for the T5610 workstation. It would bluescreen another vendors system (Lenovo X1 carbon) when initiating a Windows 7 x64 installation. I am pretty sure the storage controllers in here were the issue. I reverted to using the specific T5610 storage controller drivers instead of this cab and that resolved the problem.
Latitude E5540 does not have an ethernet connection with this package. This package STINKS.
Really could do with an update that will work properly with the T5810.
What's up with the T5810 drivers? I have WinPE 3 PXE boot media working in MDT/SCCM 2007 with the A12 driver CAB and all the older models 3020, 3010, 7010, 9010, 9020, 980, 790, e7440, e7420, e5440,e6430,.... Took the working WIM and updated to A15, now the T5810 will build but models like the 3020 and 7440 won't get an IP address after the Windows image and model specific drivers are loaded which makes no sense because after the reboot it should no longer be using the PE drivers but the Windows drivers which I never changed. The builds fail but when I logon to Windows it shows no network connection, 10 minutes later it gets an IP and I get prompted to pick if its on a Home, Work, or Public network. If I switch back to my A12 WinPE boot media all the older models work, but of course not the new T5810???
When does the hurting stop :)