Core Isolation/Memory Integrity slider keeps turning off.

FrancoDT said:

Duh, just remembered you told me that on an older memory integrity thread.

Click to expand...

No problem, appreciate the feedback. I think I'm stumped anyhow and maybe in over my limited abilities.

This file:
HmseUsb.sys
driver 1.1.9.0 6/30/2010
pub name: oem89.inf
Renesas Electronics Corp

is also listed a blocking Core Iso. I can't find anything on my system that correlates to. Appears it may be related to USB 3.0, but mine are all Intel, Intel drivers. It might be related to something called DIFX . I have DPinst.exe file but I don't think its ever been installed, and have no idea what it is, likely more 'bloatware' when I bought this HP.

Thanks again, hate to be a bother.

TheVisitor said:

No problem, appreciate the feedback. I think I'm stumped anyhow and maybe in over my limited abilities.

Click to expand...

One of the expert super geeks on here like Bree or others may recognize it and be able to help you. Whole reason I follow this site is all the mystery problems Windows brings and the experts here that like to tackle them.

TheVisitor said:

This file:
HmseUsb.sys
driver 1.1.9.0 6/30/2010
pub name: oem89.inf
Renesas Electronics Corp

I can't find anything on my system that correlates to.

Click to expand...

Open Device Manager. Click on View > Show hidden devices. This will show all devices that were ever connected, the ones no longer connected having grey icons. You should find it there. If so, you can uninstall it there too. That's how I removed my wdcsam64_prewin8.sys driver.

This may help you identify the device concerned.

Please open eventvwr and look at

Applications and Service Logs\Microsoft\Windows\CodeIntegrity\Operational
->Anything useful in there?

Thanks for the tips/hints guys. I think I have fianlly rooted out the source of the Renasas , oem89.inf driver issues.
This site:
describes the HmseUsb removal information, which points to the DiFX I found earlier that contains the DPInst.exe

This page: DIFx Guidelines - Windows drivers describes the DPInst.exe among others that are now deprecated.

So I think by running the long-string command on the Renasas page, followed up if needed by using PnPUtil to remove the oem89.inf should get me in shape to turn on Core/Isolation.

The only remaining question would be the oem89.PNF file that is associated with the .inf file not sure if removing the .inf will also take out the .PNF

Thanks again.

Mine actually shows as having 0 incompatible drivers, Lets me turn it on, Then after a reboot its off again. Ah meh who cares.

So, if my drivers are fine, maybe it's my incompatible CPU for Win 11?

mecanicogolf said:

So, if my drivers are fine, maybe it's my incompatible CPU for Win 11?

Click to expand...

If I remember it should state, you have incompatible driver and show which ones. I'll have to check this later to confirm, but I think you can check it yourself as you try to enable it

Yeah it should tell you - Core isolation. The other thing if on...

Note: If you try to install a device with an incompatible driver after turning on memory integrity, you may see the same message. If so, the same advice applies - check with the device manufacturer to see if they have an updated driver you can download, or don’t install that particular device until a compatible driver is available.

Click to expand...

TheVisitor said:

Thanks for the tips/hints guys. I think I have fianlly rooted out the source of the Renasas , oem89.inf driver issues.
This site:

Pacchetto driver Windows - Renesas Electronics Corporation (HmseUsb) RenesasUSB (07/01/2010 1.1.9.0) version 070120101.1.9.0 by Renesas Electronics Corporation - How to uninstall it

How to uninstall Pacchetto driver Windows - Renesas Electronics Corporation (HmseUsb) RenesasUSB (07/01/2010 1.1.9.0) Version 070120101.1.9.0 by Renesas Electronics Corporation? Learn how to remove Pacchetto driver Windows - Renesas Electronics Corporation (HmseUsb) RenesasUSB (07/01/2010...

www.advanceduninstaller.com

describes the HmseUsb removal information, which points to the DiFX I found earlier that contains the DPInst.exe

This page: DIFx Guidelines - Windows drivers describes the DPInst.exe among others that are now deprecated.

So I think by running the long-string command on the Renasas page, followed up if needed by using PnPUtil to remove the oem89.inf should get me in shape to turn on Core/Isolation.

The only remaining question would be the oem89.PNF file that is associated with the .inf file not sure if removing the .inf will also take out the .PNF

Thanks again.

Click to expand...

Okay, got brave and started removing the bad drivers.
1st: The instructions given on the link from Ranesas did not do anything. (Or I was not running it right)
2nd: I just manually deleted DIFX and sub folders (so far nothing bad happened)
3rd: Initial instructions I found for using PnPUtil did not work, so googled up a page with commands for the PnPUtil and removed the oem89.inf
that had the Renesad driver 1.1.9.0, removed the WD drivers with same method.

I now have Core Isolation enabled - so far so good. Have done 4 restarts and it seems to be staying enabled.

Now new problem:
On reboot I get several Hyper V Hypervisor logs in Event Viewer System and 1 warning:
The hypervisor did not enable mitigations for CVE-2018-3646, CVE-2019-11091, CVE-2018-12126, CVE-2018-12127, and CVE-2018-12130 for virtual machines because HyperThreading is enabled. To enable mitigations for virtual machines, disable HyperThreading.

I have checked system Bios and it does not have any settings for Processor, or any to turn/off Threading.
System is HP Pavilion tp-01-1026 10th generation Intel core 15-10400, 12gig Ram and SSD.

I don't use any Virtual machines, unless windows 11 runs things there. Anything I should worry about with mitigations not enabled ?

What about the log, did you look at it?

Comport Colin said:

Please open eventvwr and look at

Applications and Service Logs\Microsoft\Windows\CodeIntegrity\Operational
->Anything useful in there?

Click to expand...

Comport Colin said:

What about the log, did you look at it?

Click to expand...

Yes I did thanks, there was nothing there but an error during Antivirus (Defender) scan about a .dll for the Intel Graphics Control Console.
I did a 'reset' on the console, and updated it but the error remains. Uninstalled the Intel graphics in Device manager, restarted, the updated the driver and it still persists , I have the Console disabled on 'startup' as I don't need it so just going to ignore that error. Here is the error if your interested :
Code Integrity determined that a process (\Device\HarddiskVolume3\ProgramData\Microsoft\Windows Defender\Platform\4.18.2203.5-0\MsMpEng.exe) attempted to load \Device\HarddiskVolume3\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_e96a5623ed9fa7ca\igd10iumd64.dll that did not meet the Custom 3 / Antimalware signing level requirements.

Thanks again for the help. BTW: I have turned off again Core Isolation because I don't understand the Hyper V logs I stated above about disabled mitigations due to Hyper Threading being enabled for Virtual machines. I don't think Hyper Threading can be turn off on my particular Intel CPU.
Not been able to find anything on the net, and no settings for the CPU in BIOS.

I never got a straight answer, did I?

Neither did I. @mecanicogolf , what about the log?

Comport Colin said:

Neither did I. @mecanicogolf , what about the log?

Click to expand...

No,no. I mean I'm the one who started this thread from the beginning.
Anywho, I have been running Win 11 on the Beta channel now for some months now (now on Build 22621.100) on this supposedly incompatible CPU with the Core Isolation slider "ON" and it's been holding now for about a month.
No more problems. Maybe it was the older builds?
By the way, I've got SecureBoot and TPM, just don't have the CPU. But it's running like a champ!

I had the same problem and the reason was behind 'Virtualization Based Security' setting being disabled in group policy by a software or maybe an old/incomaptible driver in the past.

Enable core isolation memory integrity and reboot, check to see if it's on.

run Local Group Policy Editor (gpedit.msc).

goto:
Computer Configuration > Administrative Templates > System > Device Guard
Set 'Turn On Virtualization Based Security' policy to Enabled and reboot your device.

omidgl said:

I had the same problem and the reason was behind 'Virtualization Based Security' setting being disabled in group policy by a software or maybe an old/incomaptible driver in the past.

Enable core isolation memory integrity and reboot, check to see if it's on.

run Local Group Policy Editor (gpedit.msc).

goto:
Computer Configuration > Administrative Templates > System > Device Guard
Set 'Turn On Virtualization Based Security' policy to Enabled and reboot your device.

Click to expand...

That was 3 years ago but thanks for the info. I've never had a problem since.