STTub30.sys stmicroelectronics incompatible driver causing Mempry integrity off

i used the link given earlier by Sumit (Volunteer Moderator)")

https://www.yourwindowsguide.com/2022/09/fix-memory-integrity-due-to-incompatible-drivers-cannot-be-enabled.html#.YxDaYnZBy3A

I opened cmd from start menu as an admin

used the suggested cmd line

• dism /online /get-drivers /format:table i found the oem that was problem it was an USB deriver; oem33.inf ; that was from STElectronics for embedded development so i uninstalled by using suggest command line;
• pnputil /delete-driver oem33.inf /uninstall /force it and restarted ; it is gone
• you can see the problem oem from Windows Security warning when you click on the arrow it will show you the problem one

Thank you

Use the PNPUtil Tool or Autoruns:

[FIX] Memory integrity due to Incompatible drivers cannot be enabled - Your Windows Guide

That solution only sees to work if the driver is listed as "oem___.inf, but as you can see in the screenshot, this sttub30.sys driver is listed without such reference. What to do in that case?

I was able to find a replacement at this location: https://github.com/qmk/qmk_dfuse/blob/master/Driver/Win8.1/x86/x86/STTub30.sys

Friendly warning; that is most absolutely NOT an official location nor is that an official account of ST. If you prefer to get the official file, don't download from that link.

With that warning in mind, I checked the date of that file and verified it was dated after the same date of the file that Patrick deMan got from ST. So I took a shot.

I went to C:\Windows\System32\drivers\ using Explorer, copied STTub30.sys to a backup location for in case I had to go into safe mode and undo the change. Once it was backed up, I then deleted STTub30.sys from C:\Windows\System32\drivers. I then copied the file from the Github link into C:\Windows\System32\drivers. It warned me that it'd require admin permission. I granted it. It completed the copy operation. After that, I rebooted.

Once done rebooting. I went to Windows Security -> Device Security -> Core Isolation -> Core Isolation Details and turned on Memory Integrity. This time, unlike before, it turned on with no problems. Windows warned me it'd need to reboot. I told it to go ahead.

After that, I went back to Windows Security and was able to confirm Memory Integrity protection was fully operational. My gamble paid off.

I did get another error -- but that was from Windows warning me that ene.sys was vulnerable (integrity protection kicked in and blocked it, awesome to know it's working!). I was able to update that by going to MSI Center and having it update Mystic Light to latest version then rebooting. All was well after that, no further issues.

I contacted ST Microelectronics, and they provided me with an updated version of that driver file STTub30.sys (which originates from 2015).

See here: https://answers.microsoft.com/en-us/windows/forum/all/memory-integrity-forced-off-incompatible-driver/5512e9ca-2984-44fc-8ba1-3b88bfd69600