Solved Offending drivers DriveStore Explorer can’t find

Windows Security → Device Security → Core Isolation lists several drivers that are incompatible with allowing Core Isolation to be turned on. This is after an upgrade of a really old system (> 12 years) from Windows 10 to Windows 11. @glasskuter had suggested in a separate thread that I use the DriveStore Explorer utility to remove drivers. Unfortunately, there are still incompatible drivers DriveStore Explorer cannot find. How do I find them and remove them, also?

Baeolophus said:

Core Isolation lists several drivers that are incompatible with allowing Core Isolation to be turned on

Click to expand...

Does it actually give you a list of drivers? If so, could you post a screenshot of what it is showing you?

You could try the Memory integrity scan tool,

hsehestedt said:

Does it actually give you a list of drivers? If so, could you post a screenshot of what it is showing you?

Click to expand...

So, pretty much all of those drivers should be easy to identify. Vbox - that's obvious. Gear software - I believe that they make CD burning software that are often incorporated into other products to give those products burning capabilities (backup software is a prime example of this). Creative and Logitech, again easy. Brother should also be obvious. AsIO64.sys is part of ASUS software suite.

I would suggest starting by seeing if each of these packages has any updates available.

But be aware that this cannot be solved on every system. For some systems there simply is no getting around that some drivers may be incompatible with memory integrity.

I suppose that this is one of the many reasons that MS is pushing people toward newer hardware with Windows 11 whether we all like it or not

I know that all of those drivers are old and no longer relevant. The hardware that this is running on does not have a disc drive. I know for a fact that the ASIO64 driver is very old. I have installed the latest driver package for the new Asus hardware, and it has not replaced or updated it. I would just like to know how to remove those drivers manually. Where would they be located?

By the way, a couple of drivers were associated with apps I was able to uninstall from Settings → Apps. This is what I am down to now:



Virtualbox could not be uninstalled or updated, because it made reference to an H: drive, which is not attached to the new hardware.

Removing the file AsIO64.sys alone from the system does not take it off that list. Obviously, there are other components elsewhere, which I have not found.

Baeolophus said:

I know that all of those drivers are old and no longer relevant. The hardware that this is running on does not have a disc drive. I know for a fact that the ASIO64 driver is very old. I have installed the latest driver package for the new Asus hardware, and it has not replaced or updated it. I would just like to know how to remove those drivers manually. Where would they be located?

Click to expand...

This is the way I handled it when switching from Asus motherboard to Asrock and it had those ASIO virtual drivers.

Fairly easy to identify that lot. I'm using educated guesswork but you can nail it with a simple Google search.

Some maybe drivers for things you are using, or have used in the past, that's for you to check.

The Creative one is a sound driver, possibly in Windows\system32 folder.

The 2 Logitech ones seem to be a camera, again possibly in Windows\system32 folder.

Brother maybe a USB printer.

The Gear one some burning app driver that maybe part of an App, possibly in Windows\system32\drivers folder.

The last some virtual box driver from Oracle.

The first some ASUS utility driver.

If they are essential Apps you can update the respective App and hope for a more compatible driver.

If they are old residual sys drivers just delete them.

On my 11 year old machine I was never able to reduce that list to zero.

might as well just sit in system32 and use the search feature in explorer to find them

or DIR filename.ext /s from cmd prompt

as @Helmut said most of them are likely in c:\windows\system32\drivers

I use Microsoft SysInternals tool "AutoRuns64" to identify all drivers. You can disable starting them at boot with that tool. Be careful they are not required by Windows for it to boot and run. The tool can identify and classify all software started up on your system.