Disabling core isolation on windows

Question

I configured an Intune policy to disable Memory Integrity (Core Isolation). The policy reports success, but the setting remains enabled on the device.

Additionally, Virtualization-based Security is set to Disabled in the policy, yet it continues to show as running on the device.

Answer 1

If you have configured an Intune policy to disable Memory Integrity (Core Isolation) and it reports success but the setting remains enabled on the device, there could be several reasons for this behavior:

1. Policy Application Delay: Sometimes, it may take a while for the policy changes to propagate to the device. Ensure that the device has synced with Intune and that the policy has been applied correctly.
2. Local Group Policy Settings: If there are local Group Policy settings that enforce Memory Integrity, they may override the Intune policy. Check the local Group Policy settings to ensure they are not conflicting.
3. Registry Settings: Memory Integrity settings can also be controlled via the Windows Registry. If the registry key for Memory Integrity is set to enabled, it may prevent the Intune policy from taking effect. You can check the registry key at HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity.
4. Compatibility Issues: If there are compatibility issues with drivers or applications, they may prevent Memory Integrity from being disabled. Review the Code Integrity logs in Event Viewer to identify any blocked drivers that could be causing this issue.
5. Reboot Requirement: Some changes may require a system reboot to take effect. Ensure that the device has been restarted after applying the policy.

If Virtualization-based Security is still showing as running despite being set to Disabled in the policy, similar checks apply. Ensure that there are no conflicting settings in local Group Policy or the registry, and check for any pending reboots that may be necessary for the changes to take effect.

---

References:

• Enable virtualization-based protection of code integrity
• Memory integrity and VBS enablement