Windows 11 will not show incompatible drivers

Anonymous
2023-03-23T21:22:01+00:00

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.

Windows for home | Windows 11 | Devices and drivers

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.

0 comments

164 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-03-10T01:58:54+00:00

    Hi Zadee C:

    I did everything you mentioned here and it worked! I'm fascinated by it! Thank you so very much!

    Sincerely,

    Aida Camacho

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-12-14T18:56:49+00:00

    Fingers crossed - 24H2 update finally fixed Memory Integrity on my 3 year old Dell XPS8940 (with an eligble Win 11 upgrade). I was able to just slide the button to on without having to delete any drivers. Back in March '23 I had deleted an indicated driver which I beleive was associated with a "free" program Dell installed on my pc, but MI would not enable after this deletion.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-12-12T08:48:18+00:00

    Hi Glenn, I was able to get Scott Hansleman's attention through sheer luck (details omitted) as he is a very busy person. He said he would get the developers to look at it. This was around a week ago and I'm sure it will take a bit of time. As for the odd or inexplicable behavior you saw, it's (of course) impossible to guess what changed by Dell or Microsoft (or both) to prevent the issue from re-occurring. If it was done by someone less experienced, their fix may cause system instability. Example: imagine someone deciding not to run the hvciscan_amd64.exe tool but just set or clear the HypervisorEnforcedCodeIntegrity registry value without listing **any** of the drivers in violation that normally would have been shown by running the hvciscan_amd64.exe utility (since Microsoft was intending to deprecate the hvciscan_amd64.exe tool (and perhaps MSFT finally did so). There are many possibilities and I can't worry about it since the ideal people to explain it would be a combination of Microsoft collaborating with Dell. Stay tuned. :-)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-12-11T22:17:52+00:00

    Yep, the 24h2 update fixed the problem for me too, I only had an issue with the wifi card wih this update... but... It was an VMware issue... It would not get an DHCP IP address, found that it was the bridge adapter created by VMware (because I need an bridged adapter for some tests... without the default NAT...), I've deleted the bridge and for now it seems that this update are ok to use, and it really fix the core isolation problems, no need to use the regedit fix anymore.

    Was this answer helpful?

    0 comments