Core Isolation/Memory Integrity switches back off AFTER reboot.

[Todd Sdedson]

I recently installed Win11 with the Memory Integrity (Core Isolation) option turned on and working properly. I DOWNGRADED my UEFI/BIOS from 4801 Beta to the previous version of 4701 (with all the previous BIOS settings from 4801 properly re-instituted). Everything works fine, system boots. I noticed however that Core Isolation/Memory Integrity had been switched to the OFF position. Well I turned it back on and Win11 asked me to reboot for the changes to take effect as normal.

AS SOON AS I BOOT BACK INTO THE SYSTEM THE MEMORY ISOLATION OPTION IS AT THE OFF POSITION AGAIN. No "driver issues" or anything like that since Windows allows me to change the option and asks for a reboot. What in the eff is going on? Any idea? It has to be something BIOS related but WHAT? All the options are IDENTICAL to the 4801 UEFI/BIOS I downgraded from. This shouldn't be happening.

Board is an old Asus P9X79 Deluxe.

 

[xrobwx71]

Here is what I found.

Some Core Isolation features are enabled by default on Windows 10 PCs that meet certain hardware and firmware requirements, including having a 64-bit CPU and TPM 2.0 chip. It also requires your PC supports the Intel VT-x or AMD-V virtualization technology, and that it’s enabled in your PC’s UEFI settings.

SOURCE

 

[Todd Sdedson]

Appreciate it, but Virtualization/VT-x is on. I have a version of Windows 11 which removes the TPM2 requirement so that I can have it running on this machine. Still, CI/MI was set to ON and working prior to my UEFI/BIOS downgrade. I just can't figure this out. I'm tempted to re-flash the BIOS back to 4801 just to see if that's what it is...