Cannot enable Core Isolation in Windows 11 due to incompatible drivers

Anonymous
2022-08-30T20:52:47+00:00

Core isolation on Windows 11 not possible, in my case, because of these drivers

I tried to find them in Windows/Sys32/drivers (as suggested in other forums) and deleting them but with no success so how can I solve the problem allowing the activation of core isolation?

Original title:

Core isolation not allowed for driver incompatibility

Windows for home | Windows 11 | Security and privacy

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Sumit 44,316 Reputation points Volunteer Moderator
2022-09-01T13:17:52+00:00

Hi,

Here is what typically works for most of the users who know the driver name as it is mentioned in Windows Security. Apparently, Microsoft changed/updated the incompatible driver list recently, which has ended up this issue for most of the users.

Method 1:

You can get the list of drivers by running this command in the elevated command prompt:

dism /online /get-drivers /format:table

After that, Make note of the Published Name (ex: "oem13.inf") of the driver that is shown as problematic.

Then use the pnputil command to delete the driver from the device:

pnputil /delete-driver <Published Name> /uninstall /force​

Please note that running this command would remove the device driver and the next time you use the device, it would not work. Reinstalling the driver might help.

Method 2:

Another alternative is using Autoruns to delete the driver. Download it from here:

https://live.sysinternals.com/autoruns.exe

Run it as administrator.

Go to the Driver tab, locate the driver and delete the same.

[FIX] Memory integrity due to Incompatible drivers cannot be enabled - Your Windows Guide

Was this answer helpful?

100+ people found this answer helpful.
0 comments

116 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-07-24T22:40:20+00:00

    Reviving this discussion. I, too, am unable to turn on core isolation in Microsoft 11. In this case, the drivers are EMVSCARD. sys (Published name: oem63.inf) It appears there are two of them but only one has the info and published name listed. I reached out to the manufacturer and got the updated driver, but it is still incompatible. I don't want to remove the driver, since it's for a piece of hardware I still need. Is there a way to solve this problem that would allow me to both use this hardware and enable core isolation? Is it simply a matter of me needing a new hardware device?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-07-14T03:30:58+00:00

    With the recent discovery of over 100 drivers with forged credentials, who knows what else has been affected. I do believe that Windows is doing all it can, back checking a near impossible amount of code. Unfortunately politics has been "proven" to be also involved making things even more difficult. My particular version of the problem (no identification of affected driver(s) ) seems to be in the repair process and a fix is to come "very soon". I can only hope that yours' and others are addressed / patched soon as well.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-07-14T03:15:28+00:00

    As you said Bruce,

    "New question, how do I shop for new encryption software without knowing the same thing will come up."

    Not trying to be funny, but you are talking about Windows. Apple systems are more stable......but only because Apple decided from its' very beginning that it was going to be the one and only source for software and hardware compatible with its' OS. That is how they stayed in business (and were able to charge ridiculously high prices for accessories, monitors etc (if you ran their OS then you had no choice but to pony-up for anything with their logo attached). Windows, on the other hand, decided to take advantage of the ideas and ingenuity of those outside of its' direct control and invited new ideas and inspiration in to help speed up innovation within the industry. I believe that Windows has really tried over the decades to ensure that the code written by these outside developers both conformed to and offered future expansion to the "new" computerized world. Over the past decades and billions of lines of code created for and used by Windows, errors have sprung up and had to be addressed. Apple has not been immune but with its limited use on third party peripherals, the negative effect has been minimal. Windows third party peripherals, on the other hand, truly encompass the globe by comparison making keeping up with code error checking more and more difficult. Add to the problem hackers are getting smarter and smarter as time progresses. This "recent" discovery of over 100 deliberately infected drivers having forged / phoney credentials, the code checkers at Windows are probably working 25 hours a day right now. This present Memory Integrity bug has been identified by Windows and, according to the tech I spoke with, is to be corrected in a (hopefully) soon-to-be released patch / update. I am not employed by Windows (I'm a 71 year old retired airline employee) and have had my share of OS problems and crashes over the years and , on several occasions, have had some "choice" words about Windows but this present flood of problems is being for the most part caused deliberately and being cleverly hidden. Windows has its' work cut out for it right now and I think we have to cut them a bit of of slack.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-07-14T00:41:38+00:00

    Image

    Image

    Hi Edward;

    Here are a couple of screen grabs. There were originally two drivers, i used Autorun to delete one of them (unfortunately not the problematic one).

    *For info, I'm running Norton AV and VPN. Nothing else that I think of that can cause the driver problem.

    The one that is causing my problems is "WinVDEdrv6.sys" as reported by Windows memory integrity. I use a NewSoftwares LLC

    for encryption software. They have been aware of the problem for almost a year now and seem to have no intention to fix it.

    I have noticed from watching this thread there are several drivers out there causing problems, so maybe it is a MS Windows problem?

    So I'm looking to replace my encryption software, as I can't mess around this anymore. New question, how do I shop for new encryption software without knowing the same thing will come up.

    Thanks for your help.

    Bruce

    PPI-Casper

    Was this answer helpful?

    0 comments