Force Windows 11 to Install a Device Driver

We manufacture training equipment for industry that runs our proprietary software. Our equipment requires the installation of a driver that Windows 11 does not recognize when our software is installed on a laptop. When we try and install manually through Device Manager, right-click on the 'unknown device', select Update Driver from the dialog box, and navigate to our installed Drivers folder on the Desktop. When we click 'Okay', Windows 11 pops a dialog telling us the driver cannot be installed with no other options presented. We know this is incorrect because we ran into this problem a year or two ago and aa Microsoft tech gave us a simple workaround that was successful but that we failed to document. Now a customer has run into the same issue again. HELP!

hello and welcome to forums,
do you have link to that driver?

jjenco said:

Our equipment requires the installation of a driver that Windows 11 does not recognize when our software is installed on a laptop.

Click to expand...

Therefore it should work to install the driver prior your software is installed (if it doesn't work after it's installed)

I assume that your driver must include among the files a file with a ".INF" extension. Try navigating to the location where you have the driver files using File Explorer, right-click on the .INF file, the select "Install".

At the very least, even if it does not install, I am hoping that it might give you some better error message, but the hope is that this will actually install the driver.

It's one of these

Hmm maybe the "Driver Enforcement" can help LINK

We tried directly installing the .INF file and that did not work either.

So, the answer appears to be that you have to turn off Windows Core Isolation Memory Integrity in order to install the driver. The problem, now, is that when you turn it back on after successfully installing the driver, it flags the driver as an error.

jjenco said:

So, the answer appears to be that you have to turn off Windows Core Isolation Memory Integrity in order to install the driver. The problem, now, is that when you turn it back on after successfully installing the driver, it flags the driver as an error.

Click to expand...

Ahh, I guess it's a poorly written driver, or unsigned, or has some other sort of "issue".

jjenco said:

So, the answer appears to be that you have to turn off Windows Core Isolation Memory Integrity in order to install the driver. The problem, now, is that when you turn it back on after successfully installing the driver, it flags the driver as an error.

Click to expand...

Core isolation isn't mandatory in a supported Windows 11 installation. It is required for "enhanced hardware security". If your customers demand it, that's a problem.

(The same issue existed under Windows 10, but many installations didn't try to enable Core Isolation.)

The fun part is that once a conflicting driver is installed, it may remain in the Driver Store even after the application that included it has been uninstalled. It will still prevent enabling Core Isolation, even though the driver is not active. MS may not make it easy to get rid of drivers in the Driver Store.

bobkn said:

Core isolation isn't mandatory in a supported Windows 11 installation. It is required for "enhanced hardware security". If your customers demand it, that's a problem.

(The same issue existed under Windows 10, but many installations didn't try to enable Core Isolation.)

The fun part is that once a conflicting driver is installed, it may remain in the Driver Store even after the application that included it has been uninstalled. It will still prevent enabling Core Isolation, even though the driver is not active. MS may not make it easy to get rid of drivers in the Driver Store.

Click to expand...

Thanks for the insights. I reached out to the guy that wrote the driver for us some years ago, to enable our software to run on 64-bit machines, to see if he has any ideas. Thanks again for taking the time to reply.