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 No 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 No comments

116 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-03-31T03:46:57+00:00

    hi Ramesh. If the drivers and services are part of the Rapport firewall protection then

    I’ve just left web pages unprotected lol. So the browser extensions may merely be an interface function with no real teeth.

    I hope someone familiar with Rapport internals is reading this thread and will comment on it. But there was a post very early about Rapport working with IBM to resolve the incompatibility, and nothing has been resolved. That’s not surprising.

    Rapport was always an optional add-on. I hope the anti malware I have will protect the websites I visit.

    Thanks again, and regards

    Was this answer helpful?

    0 comments No comments
  2. Ramesh 181.2K Reputation points Volunteer Moderator
    2023-03-31T01:54:37+00:00

    Hi Tom,

    Thanks for the update.

    I haven't used Rapport and don't know what the driver is about. Maybe it's a firewall component, I'm not sure.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-03-30T20:29:01+00:00

    Thanks, I will follow up on this.

    Bruce at

    PPI-Casper

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-03-30T14:29:11+00:00

    I want to report success with the command line operations suggested in the post I'm replying to.

    My environment:

    Windows: 2023-03 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5023706)

    pc: Lenovo IdeaPad 3 15IML05

    I've deleted all the Rapport drivers and services. Core isolation is enabled.

    I'm thinking that the services which all showed as "Stopped" in the wmic command must have

    been used only during installation of the Rapport software updates?

    Because even with the problematic drivers and services deleted, the browser extensions in

    Chrome, Firefox and Edge still appear to be working. Or maybe I'm reading it wrong.

    Anyway, thank you to Ramesh Srinivasan.

    Regards,

    Tom

    Was this answer helpful?

    0 comments No comments