I am in the same boat. I have no driver as being incompatible. I tried all the fixes everyone is talking about on this forum.
This happened recently, so MICROSOFT where are you?
PLEASE PLEASE put in a fix.
Thanks.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In new windows 11 up to date as of writing this. Core isolation memory integrity does not work and will not turn on. Every time I scan for incompatible drivers, none are listed. Checked the windows update, the system is up to date, and no errors in device drivers were found. All drivers appear up to date. BIOS most recent available (the same driver that was installed prior to this error occurring. None of the threads seem to address this, only ones where the driver is known. The DG readiness tool is not user-friendly for everyday users. Need a solution that can be done at home without having to be an IT guru or MSCE certified. It will not let me upload the screenshot or picture, keep getting errors in that as well.
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.
I am in the same boat. I have no driver as being incompatible. I tried all the fixes everyone is talking about on this forum.
This happened recently, so MICROSOFT where are you?
PLEASE PLEASE put in a fix.
Thanks.
hello, I dont see the folder "HypervisorEnforcedCodeIntegrity" and when I tried to create one it is showing error cannot create a key
Same, I do not have one either. This started with the last patch to windows from microsoft.
I have exactly the same issue on a Dell XPS 9510 laptop. Microsoft really needs to get its act together and fix this!
I have spent hours and hours looking for a solution to no avail. It states that there is an incompatible driver but doesn't list the offending driver and the link to further information just takes you to a useless page of non information.
I'm just leaving it turned off until Microsoft comes up with a solution rolled out in an update, probably in 2025!
My Dell computer run with Windows Pro, not home, and I have the same issue.
I had to create "HypervisorEnforcedCodeIntegrity" and set it to 1. Rebooted and got the same problem as you. Even though it is turned on and grayed out, the Windows shield icon in the system tray still shows the yellow exclamation warning. I'm going to delete the key I had to create and wait for MicroSoft to fix this before I really break something and make matters even worse!