Current Driver CAB Summary
Driver CABs Homepage | Understanding Delta Report
Delta Report for Previous Driver CAB v/s Current Driver CAB
(942XJ-A04-01/05/2017) v/s (5V09N-A05-10/10/2017)
Intel NIC Family Version 18.0.0 Drivers for Windows 64-bit Operating Systems
Intel 10 Gigabit X5x0 Adapter Driver
Broadcom NetXtreme Gigabit Ethernet Driver
ASMedia USB 3.0 Extended Host Controller Driver
Realtek PCI-E Ethernet Controller Driver
Intel I2xx/825xx/10/100/1000 Ethernet Network Driver
ASIX AX88772 Local Area Network Driver
Intel I2xx/825xx Gigabit Ethernet Network Controller Driver
SMSC LAN7500 USB to Ethernet Adapter Driver
Realtek USB GBE Ethernet Controller Driver
Intel(R) Thunderbolt(TM) Controller Driver
Intel Rapid Storage Technology enterprise Driver and Management Console
LSI 9440-8i/9460-16i drivers for Windows 10 - 64 bit
Intel Rapid Storage Technology Driver and Management Console
Intel Rapid Storage Technology Driver
LSI 9361 drivers for Windows 8.1- 64
LSI SAS 2308/9217 Controller Driver
Intel Rapid Storage Technology Enterprise F6 Driver
LSI 3008 Drivers for Windows 8.1 - 64 bit
SMSC LAN7500 driver
LSI 9341-8i Drivers for Windows 7 - 32 bit
LSI SAS3008 Windows Drivers for Win7-32
link 404s ;(
Please fix the DL link! We can't deploy in the moment because of this.
link 404s still... :-(
For some reason when importing this into SCCM it only wants to import the x64 drivers, it fails to import the x86 drivers.
Fixed previous issue, but I am unable to image a Dell 6410 using the WinPE10 driver in a windows 10 ADK boot.wim. Is this possible? We are setting up a x86 boot.wim with the winpe10 drivers for Win7 images and a x64 boot.wim with the winpe10 drivers for Win10 images.
So far I keep getting storage driver errors at the start of the task sequence when trying to image a 6410.
Same issue on an E6430 on both x86 and x64 boot images. Its missing the megasas2.sys driver
Has anyone had an issue where the initial MDT boot screen in WinPE has white horizontal lines across half the screen? It goes away when the wizard launches, but have never had that happen before. Happens across multiple models.
When booting a device off a WinPE image created with the 1703 ADK and the A04 driver pack injected via ConfigMgr, I've observed some erratic behavior:
- E6530 laptops will blue screen within 30 seconds (REFERENCE_BY_POINTER)
- Interestingly enough, Surface Pro 3s will lose their network connectivity after ~5 minutes
When I remove all drivers, both of these devices work as expected. I have not tested any other models.
Touch pad is not working on Latitude 7480 during pxe boot
Did anybody found a solution to solve the error with the bluescreens on those E6430´s?
It seems like the A04 version of this driver pack has broken backwards compatibility with some older systems such as the Precision T3500 and a few older Optiplex models. Rolling back to A03 gets them going again but I'd imagine that as we start getting in a few of the newer models that A03 will not work for them.
I'm seeing the same issue with REFERENCE_BY_POINTER error on winPe10 x64 + A04 drivers pack on latitude e5430, workaround for us was to switch the disk to ATA.
in my opinion, those drivers provided by DELL are buggy as the deployment of a E6430 with no drivers injected (original windowspe) is working fine. As soon as we include this WinPE Dell Drivers, the Deployment is causing a BSOD (reference by pointer).
N6RY0_A00-00 x64 NIC driver is showing as not digitally signed when importing to SCCM.
@luis - did anyone ever figure out why the Latitude 7480 touchpad driver doesn't work in winpe 10 using MDT 2013? i also can't get the touchpad to work in Windows 7. We ordered the 7480s with skylake processors. The touchpad does work in the BIOS and on Windows 10. But doesn't work or is VERY flaky on my 7480, 7280 and 5480.