Dell, Windows 11, updates all current - all started with old Wd drivers listed as the incompatible drivers which I uninstalled BUT then they stayed showed up still listed in incompatible list despite restarts. I went into Device Mgr, view, and removed. Now it says 'incompatible drivers' but nothing is listed, yet, I still cannot toggle memory integrity. Anyone? I have seen where force removal does not work for multiple people.
I can't turn on memory integrity in Windows 11 even though no incompatible drivers are listed.
I can't turn on memory integrity in Windows 11 even though no incompatible drivers are listed.
Windows for home | Windows 11 | Security and privacy
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.
110 answers
Sort by: Newest
-
Anonymous
2023-10-21T00:40:34+00:00 -
Anonymous
2023-07-18T22:22:14+00:00 Same here. Manually uninstalled the offending drivers (Logitech) via Device Manager, command line pnp util and Autoruns utility.
Its a Dell laptop as well G15 5515.
After a BIOS update it seemed to work, then went on tilt (froze) then reverted back to the original empty list. Seriously a bug.
-
Anonymous
2023-07-17T17:50:30+00:00 Let me know if you get an answer to your question:
How worried should we be about the vulnerability?
I have been asking that question for months and have never gotten an answer.
-
Anonymous
2023-07-17T17:27:58+00:00 I have multiple business Dell Precision 3650, Optiplex 7090, and Optiplex 7000 machines with this same problem. I’ve tried everything to resolve the core isolation memory integrity but the problem still persists. The strange thing is that I have multiple boxes configured identical (except for user accounts), yet some have memory integrity on and some will not turn on. Makes no sense.
-
Anonymous
2023-07-17T15:27:31+00:00 Just to add to the thread I have the same issue. No Drivers listed and yes... it's a Dell G7 17!
Seems to have been an issue for quite some time but I just noticed it recently after resetting my laptop...
how worried should we be about the vulnerability?