Latitude E7450 missing drivers after win 10 upgrade

I still have a problem with the Intel® Wireless Gigabit User Mode Driver, it keeps giving me an error:

Windows has stopped this device because it has reported problems. (Code 43)

It disappears after I disable and enable the device but after a restart it returns.

@Hsalen,

I've sent you a PM regarding the code 43 concern.

@Community,

I finally got my hands on a 17265 WIGIG card. Once installed into my E7450 with WIN10, the not- installed network controller listed normally and to my surprise, so did the 3420 device.

I was able to run the Windows 8.1 version of the 17265 WiGig Application package on my E7450 with WIN10. Once done, the 3420 device and the WIGIG device both installed normally.

Here's a progression of what my device manager looked like as I installed various drivers:

Before any drivers:

Below will show that I have not yet installed WIGIG, AMT and Intel Bluetooth.

Note: The PCI Simple Communications controller is the AMT device. 

New items that showed up after I installed WIGIG:

We can now safely conclude that the Intel Power Sharing Manager = DEV_3420 and is installed as part of the WIGIG installer.

My Device Manager after all drivers installed:

We are having a similar issue with the Dell Latitude E7250 laptop.  We use SCCM to deploy our OS.  We've been literally trying to get this laptop deployed into our environment for 3 weeks now with no success.  We figured out the WiGiG Manager resolves the memory leak so we've packaged it, because installing the drivers alone does not quiet the memory leak.  However, we are still getting the MSVCR100 and 120.dll error just after the drivers install in Windows Device Setup portion of the Task Sequence.  We've tried to strip the drivers down, eliminate anything extraneous.  The dll error relates to Setup.exe, but we've been diligent in making sure there is no Setup.exe in the driver pack because that's where the error points.  Even so, the dll error [100 or 120] continually popup at the end of the Windows Device Setup step in the Task Sequence.  We have had no other issues like this with either the E7440 or E7240 or M4800 models in our OSD.  For the life of us we cannot zero in on why Configuration Manager needs this dll for just this model of laptop.  It stops the Task Sequence dead until we click OK thru the dll error.  It shouldn't be this hard to get a laptop into our environment.

And just an aside, why can't Dell create a stripped down driver pack with out all the frivolous and extraneous components so that we engineers can get to the bottom of things like this without having to pick thru a pile of exe's and dll's that don't even get used in the OSD?

Any help we can get on this would be much appreciated.  Thanks in advance!

@Wafflebox306,

I know I'm a little late here but I spoke with some more-knowledgeable-than-me imaging professionals on your behalf and they found this:

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/8031.dell-command-deploy-faq

Scroll down to item 5. Does that help you out?

This works for me;

en.community.dell.com/.../11554.latitude-e74507450-windows-10-driver-pack

Sorry to come back to you but I'm having problems again.

I installed the windows 10 fall update and suddenly my bluetooth driver keeps crashing, I have the latest intel driver 17.1.1532.1814 installed, I tried to remove it, reinstall it, nothing seems to work, it keeps crashing.

Why is it always trouble when microsoft releases a big update???

Dear Community,

I've done some more research for you regarding the WIGIG card. The following document contains a potential reason why you might see the WIGIG card shown as 'not install' in device manager, after imaging with the Dell CABs included: http://www.dell.com/support/article/us/en/19/SLN300271