Memory Integrity disabled even after resolving driver issues
I had what seemed to be a pretty common issue with incompatible drivers preventing activation of the Memory Integrity feature of Windows Security. This went on for a shamefully long time, probably over a year, until I finally got around to removing/updating* the offending drivers yesterday. The scan for driver compatibility no longer identifies them as a problem, but the incompatible drivers check is somehow still preventing me from activating Memory Integrity, even though it finds nothing wrong. I have tried several other approaches (listed below), and nothing worked.
*I am aware that Microsoft does not recommend removing the incompatible drivers in order to solve this issue; in one case I updated the driver using the distributor's provided tools, and in the other case it was a redundant, old driver that had already been updated (see summary further below).
SYSTEM DETAILS
Dell Precision 5520
Windows 11 Pro
Version 22H2
Installed on 10/5/2022
OS Build 22621.3155
Windows Feature Experience Pack 1000.22684.1000.0
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz 2.90 GHz
Installed RAM: 16.0 GB (15.8 GB usable)
System type: 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points
THE [ALREADY REMOVED] INCOMPATIBLE DRIVERS:
ftdibus.sys
FTDI
Import date: 10/4/2022
Driver date: 8/25/2014
Driver vers: 2.12.0.0
Published name: oem4.inf
ftdibus.sys
FTDI Ltd.
Driver vers: 2.12.0.2
Product name: FTDIChip CDM Drivers
xusb21.sys
Microsoft
Import date: 10/4/2022
Driver date: 8/12/2009
Driver vers: 2.1.0.1349
Published name: oem80.inf
HOW I REMOVED THE INCOMPATIBLE DRIVERS:
I resolved ftdibus.sys using two downloads from FTDI on their website. First, the GUI version of their CDMuninstaller, which was very simple to use. I confirmed that the driver was removed from C:\Windows\System32\drivers. Then I used their CDM212364_Setup.exe which was supposed to install available driver packages. I can't tell if it actually worked though, because after I accepted the terms and conditions and saw the little install animation run for a second, it just sort of blinked and closed without reporting a success. I tried twice. (I'm not super concerned about this driver anyway, and I don't know what USB deviced it was for. I have many that I will probably never use again.)
After trying and failing to use pnputil /delete-driver in Command Prompt, I removed xusb21.sys by simply finding its folder in C:\Windows\System32\DriverStore\FileRepository and noticing that there was also a xusb22.sys, probably the new version. I cut and moved the whole xusb21.sys folder out to a backup location. (This is just for xbox controllers or something, which I don't use.)
So, the incompatible drivers were removed, and they disappeared from the report in Windows Security settings. However, this didn't allow memory integrity to be activated...
THE PROBLEM NOW:
At this point, the Windows Security icon in my system tray and the "Device Security" item in my "Security at a glance" page in Windows Security went from being marked with a warning to a green checkmark. So, looks good. But the option to switch on Memory Integrity is still switched off. When I try to switch it on, it checks for driver incompatibilities, grays-out the switch and then gives the same old message of "Resolve any driver incompatibilities" along with the option to scan again. But if I click the link to review said incompatible drivers, it's empty. Because I already resolved them.
This has not changed at any point since I removed the incompatible drivers and then went on to try all of the below additional methods.
WHAT ELSE I HAVE TRIED:
- Checked for driver updates or issues in Device Manager, saw nothing of note
- Downloaded Autoruns64 from the Microsoft website and ran Autoruns64.exe as an administrator to check for other drivers with problems. I disabled any that were highlighted. There were a few, five or six. I deleted one that gave an error and couldn't be disabled.
- Uninstalled a lot of software that I thought might be related to USB peripherals I no longer use and could be related.
- SFC /scannow in Command Prompt running as administrator; didn't find any issues
- Checked for updates in Windows Update, Dell Support Assist, and my video card updater app. Everything is up to date.
- Reset the Windows Security App
- Used the Registry Editor to add a new DWORD named "HypervisorEnforcedCodeIntegrity" with value set to 1, per some random instructions I found.
- Checked that virtualization technology support was enabled in BIOS; it was already enabled, but "Trusted Execution" was not enabled, so I enabled it.
- Rebooted several times throughout this process
- Eventually thought to try running Autoruns.exe instead of Autoruns64.exe and found that it was showing one additional highlighted driver, BlueStacksDrv_nxt. A moment later the highlight went away, but it still said (Not Verified) under publisher, and I noticed that the description uses the relevant(?) term "Hypervisor," so I went ahead and uninstalled BlueStacks completely and the driver was uninstalled as well.
- Rebooted
Regedit, BIOS, and the last Autoruns change were the last things I did, plus reboots in between. No improvement that I can see in Windows Security.
Any ideas to try would be much appreciated. I am pushing myself here and obviously trying some things already that are inadvisable for an amateur to mess with, because I really want this to work--it sounds like a somewhat critical security feature.
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.
2 answers
Sort by: Most helpful
-
Anonymous
2024-03-06T01:46:09+00:00 -
Anonymous
2024-02-20T19:16:10+00:00 If you have a branded PC, a Dell you only update drivers from Dell update, its ony if you have third party HW that you update from them.
I have 2x Dell (different model) current desktops and a Lenovo laptop all devices use the same software and printers.
On 2x devices I have the 'integrity' issues. MSFT were unable to resolve the issue, so I ignore it