Menu
Dec 24, 2018 PCI VEN 8086 DEV 1039 DRIVER - Installation Manager Success Stats: Intel r AA Controller reserved Drivers. Reserved — 2D13 Drivers. Memory Controller 0c — 2B13 Drivers. Reserved — 2D13.
Any other Dell shops having issues with the new Optiplex 5060 family's ethernet drivers in WinPE with the Dell PE Driver packs? I tend to only update my PE drivers when we hit an issue, which we recently did with the 5060s we received.Since I suspected our PE drivers were just out of date, I revved our WinPE drivers up to Dell's Rev A08 of the WinPE 10.0 driver pack, still no joy on getting the network hardware registered inside PE. PCI-ID on the device is VEN8086 DEV15BC SUBSYS085B1028 REV10 - definitely looks like one of the Intel I2xx family NICs by the ID, but for some reason it's just not picking up.
I did a full boot media rebuild after bumping up to A08, but it was also released back in April of this year. I'm going to go spelunking through the full 5060 Win10 CAB and see if there's a more up-to-date driver there, just curious to see if anyone else that's running primarily Dell hardware has had a similar issue on the 5060 series. Was finally able to confirm my suspicions, the model-specific driver pack contains newer versions of the Intel drivers than what is found in the most recent A08 WinPE release. Up until this point, I had been using a specific driver selection profile that consisted EXACTLY of the Rev A08 WinPE drivers. I dug through the INF files from both WinPE + Model-Specific CABs, and determined that the E1D65x64 was newer in the model-specific driver, and had explicit references for the Hardware IDs of the newer Intel ethernet chipset.
Now working like a charm after finding the appropriate driver and re-importing into my WinPE Driver Selection Profile. At this point, all of the A08 drivers seem to be working except for some ethernet, no issues with Storage or USB. Does anyone know if Dell has abandoned their WinPE driver packaging strategy, or are they just running behind releasing A09?.
Here's the best I can offer, it did the job for us, your actual process may vary depending on the specific chipsets in your system as well as your MDT environment. Pinging for this one as well. This all assumes you try to keep your OOB Drivers as skinny as possible like us, since we're a near-exclusive Dell shop.The current 5060 Win10 Driver Pack is available here:You will need to download and extract contents, then start digging through the.inf files until you find one that has the Hardware ID of the device that is failing (In my case, VEN8086 DEV15BC SUBSYS085B1028 REV10 ).
For me, the driver set that had my hardware was E1D65x64. Grab anything that shares that name (inf, sys, etc.) and drop them into a new subfolder- reason for this is that you can't pick just a specific file to import in MDT, you have to select an entire directory.Now, if you have a specific directory that you're using for WinPE Driver Selection Profile, import the drivers into there and recreate your boot media.
Note that like I said earlier, you COULD import the whole mass of the 5060 drivers, but to keep things simple, I like to trim as much as I can for the WinPE stuff- call it superstition, but fewer drivers equals less chance of conflict, fewer ways things can go terribly wrong.Hopefully this gets y'all up and running too!.
SM Bus Controller PCIVEN 8086&DEV 9C22&SUBSYS139D1043&REV09&0&FB The drivers for this device are not installed.Sorted by: Device IDVendor IdVendor Name0x9C22Intel Chipset0x8086Reinstalling the 'Chipset' driver would be the correct course of action, but since this is the Windows 10 Technical preview, I cannot say that.