Force Driver Install Windows 10

So here's the thing. I had to reformat my computer and reset everything. My Network Adapter Driver is currently 15.6.1.3, which Windows 10 says is the correct driver.

Hi, I have a MDT distribution that I have configured to use OOB Drivers base on OS then Model. Hasp Aladdin Driver Windows 10 there. I have a new Windows 10 WIM and it works on every model of machine but one, the OptiPlex 790. In this case, there are no drivers provided to it from MDT.

It doesn't need them. All of the drivers it needs are provided in the Windows 10 distribution. Firstly, I understand that Dell does not support the Optiplex 790 on Windows 10. The driver that won't install is for: Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C2D/1C26 These devices will show up after MDT (or manual) installation of Windows 10, 'splatted' as 'Universal Serial Bus (USB) Controller's. If I attempt to update and search automatically it will fail.

But if I choose 'Browse' then 'Let me pick.' Then select the built in MS driver below.

It works fine! Is there a way to automate this somehow? Thanks, -Matt There's no place like 127.0.0.1. How are you doing your drivers? Are you letting MDT automatically detect (Total Chaos)? If so you might be able to get around this by doing Total Control as per the link to Johan's blog post.

Most important details are logs. If you are unsure how to post logs or where to find them then reference No. The way I have OOB Drivers setup, no drivers are available to the Optiplex 790 from the MDT Windows 10 Task Sequence. The drivers it needs are already contained in the Windows install.wim. There's no place like 127.0.0.1. I don't know of any way to influence Windows driver ranking. It might be worthwhile to look and see if any third party drivers are installed.

From an elevated Powershell window: Get-WindowsDriver -Online Most important details are logs. If you are unsure how to post logs or where to find them then reference No, no 3rd party drivers. This is the same behavior from a Windows VLS ISO. I'm wondering if I can write / edit an INF to force this.

I'll have to look into it. Unless someone has a better idea? There's no place like 127.0.0.1. Any edited inf will end up a lower rank because it will no longer be signed. You might try and post a similar question to the Windows 10 setup forum. Most important details are logs.

Display Driver Failed Windows 10 there. If you are unsure how to post logs or where to find them then reference Thanks, I'll do that. Yeah that dawned on me the minute I began refreshing myself on driver ranking. In the mean time if anyone has had to do something like this with MDT before, please chime in.:D -Matt There's no place like 127.0.0.1.