Cannot enable Core Isolation in Windows 11 due to incompatible drivers

Anonymous

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

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 Volunteer Moderator

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

0 comments

116 additional answers

Anonymous

2022-09-07T00:38:44+00:00

Removed old device drivers = Success this afternoon.

WD and MediaTek

9/6/22:

4:07 pm Device Manager Sys.Devices -> removed oem34 (Western Digital SES)

4:09 pm Device Manager Sys.Devices -> removed oem16 (MediaTek CDC)

4:12 pm Win 11 Settings -> Security : Core Isloation "ON", Restart

4:15 pm WD 4 TB EasyStore installed, functional, Ejected

4:18 pm Surface App wants to "Update" with OEM34 vers. 1.2.0.0 11/30/2017 (I deferred WD Update)

The Surface App warned about old device drivers re: "Core Isolation" a few days ago

Why did the Microsoft Surface Application want to install a back revision Driver after removing it?

The Surface App now appears on screen automatically, but not in "Startup"

{surprise, looking to auto.minimize Surface Application }

SG1024

The driver removal result was checked w/command prompt : dism /online /get-drivers /format:table

Surface Studio 2

========================

Removed

========================

Western Digital

Device: WD SES Device

Import Date: 2/14/2022

Driver Date: 11/29/2017

Driver vers: 1.2.0.0

Published Name oem34.inf

wdcsam64_prewin8.sys

MediaTek Inc

Import date: 2/14/2022

Driver date: 1/21/2015

Driver vers: 3.0.1504.0

Published name: oem16.inf

usb2ser.sys

========================

OS Name Microsoft Windows 11 Pro

Version 10.0.22000 Build 22000

System SKU Surface_Studio_2_1707_Consumer

Processor Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz, 2904 Mhz

BIOS Mode UEFI

Secure

Boot State On

Total

Memory 32.0 GB
Was this answer helpful?

0 comments No comments

Anonymous

Similar problem with Memory integrity off. Won't turn on due to "Rapport" driver incompatibility.

Reported to IBM/Trusteer support and received the following response. IBM/Trusteer is working with Microsoft to resolve. Currently can't turn memory integrity on if you are using IBM/Trusteer security.

Thank you for contacting IBM Trusteer Technical support. IBM Trusteer Rapport is a powerful fraud prevention tool for detecting and removing financial malware. For more than ten years, IBM Trusteer Rapport has been protecting tens of millions of endpoints for some of the largest banks in the world. The IBM R&D and Security teams invest a lot of effort to ensure a safe and smooth online banking experience while maximizing the defense against sophisticated financial malware. As part of that effort, Rapport's functionality is constantly being optimized to ensure a conflict-free operation. Memory integrity is a feature of core isolation. Memory integrity runs a container that checks that the software code has not changed while it is running by using a signature. This mechanism makes this feature incompatible with Rapport. At this time, the memory integrity feature is disabled by default and will not allow the end-user to enable it once it detects installed software that is not compatible with it. As a result, it is currently not possible to run Rapport with the memory integrity feature enabled. We are currently working with Microsoft to make Rapport compatible with this feature in the future. Sincerely,

Alona Sermiagin
Tier 1 Support Engineer
Trusteer, IBM Security Systems

0 comments

Anonymous

2022-09-17T11:53:03+00:00

I just received a Windows 11 update. Before the update I couldn't enable "core isolation" due to a driver problem. I followed all the directions given to remove the incompatible driver and still could not enable "core isolation", and the computer would not restart. If I performed a hard shutdown, and then restarted the computer it would work with the "core isolation" not enabled. After the windows update, same thing. I use Malwarebytes and Windows Defender. Is my computer unsafe without "core isolation" since I don't seem able to make it work?
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2022-09-17T11:54:47+00:00

Success with Autoruns deleting this menacing PUP having wasted way too much time trying other methods already. Thank you for the fix, core isolation now back up and running using Windows 11.
Was this answer helpful?

0 comments No comments