Kernel Isolation and Memory Integrity Windows 11
steph810 Posted messages 1850 Registration date Status Membre Last intervention -
Hello,
I have a DELL XPS 13 9310 laptop.
Recently, I have been receiving the following Windows alert message: "Core isolation: Memory integrity is disabled. Your device may be vulnerable."
When I try to restore memory integrity as Windows requests, messages pop up: "Checking for driver compatibility..." and then it fails with "Resolve any driver incompatibilities and rerun a scan."
Perhaps you have an idea to solve the problem?
Thank you, and I wish you a good evening!
Valentin VIVIER
4 réponses
Hello,
The message will appear as long as there are incompatible drivers, the list of which is provided in the corresponding item of the Windows Security Center.
Either we update these drivers to new, compatible ones, but this is not always possible (in some cases, manufacturers have not released any), or we disable the memory integrity check in the same security center.
Thank you very much for your response
I have performed the technique, but Windows does not mention any incompatible drivers.
Do you have an alternative to identify which driver I need to uninstall?
I reactivated it just to show you, but curiously, I no longer have the list of incompatible drivers.
As far as I'm concerned, if I remember correctly, they are Intel system drivers, and there is no way I'm uninstalling them.
If there are no updates, we can only do that if they are software or hardware drivers that are no longer in use; otherwise, it is urgent to wait.
Kernel integrity is a new feature that virtualizes system drivers to prevent malware from modifying them; it is a very specific type of attack. The average person can very well live with just their usual defense software (and good habits), and we disable kernel integrity to avoid being flooded with notifications.
https://www.malekal.com/impossible-activer-integrite-memoire-isolation-du-noyau-windows-10-11/
Hello,
have you looked in the Windows event log to see what is causing these errors?
Open a PowerShell terminal and copy and paste this command, let me know if you have any feedback?
Get-WinEvent -LogName 'Microsoft-Windows-CodeIntegrity/operational' -FilterXPath '*[System [EventID=3076 ]]' | Measure-Object | Select Count If that doesn't work or there is nothing in return, do the following:
WINDOWS + R
compmgmt.msc
Event Viewer
Application and Services Logs
Microsoft
Windows
CodeIntegrity
right-click properties
You will have the list of events.
please share a screenshot if there is something.
2nd solution to see who or what:
WINDOWS + R
eventvwr
System
right column:
Search for example kernel or kernel isolation 1 of the messages that appeared on your screen and share a screenshot of the problem.
Thank you
It's clearer thank you!
I have a touchpad issue that occurred simultaneously (both clicks no longer work). Do you think it could be related?
If not, I'll leave this kernel alone :)
Have a good evening!
As I said, it is probably necessary to treat it with contempt by disabling kernel integrity.
If, despite everything, one wants to find the cause, as I mentioned earlier, Windows normally identifies the guilty driver(s); the fact that this does not happen even on my machine may be related to the numerous bugs mentioned in the latest monthly Windows update.
If these notifications suddenly appear when they weren't there before, it is either because kernel integrity has been enabled when it wasn't (intentionally, we would remember that, or possibly automatically if there has been a Windows version update, but there hasn’t been a recent one?), or because there has been a modification or installation of a software or hardware driver.
On the software side, the only cause could be the installation of a new virtual driver with new software.
An update of a driver to a new version should have no reason not to comply with kernel integrity while the previous one did; however, the malfunction of an existing driver (check the device manager?) may indeed be responsible for the situation, perhaps by reinstalling the drivers and the possible Touchpad software.