Memory integrity forced off "incompatible driver" STTub30.sys (STmicroelectronics)

This issue is caused by the steelseries app. update or reinstall the application.

I contacted ST Microelectronics, and they provided me with an updated version of that driver file STTub30.sys (which originates from 2015). I just saved it to the folder where this driver is found on your C:\Windows... folder (just search for the file to find the exact folder). The original file needs to be overwritten. I rebooted, then turned on the Core Isolation (which required another reboot to be effective).

This updated driver file should be available on the website of ST Microelectronics, as I requested to publish it after it worked for me.

I have the same issue + usb2ser.sys driver. Both of those drivers are causing my laptop, besides the memory integrity turned off issue, stuttering and lagging. I downloaded a driver identifier but didnt found those drivers, and tried manually with no success. At this point I dont know what else to do and seems that Microsoft support doesnt even care.

My attempt to enable the Memory Integrity security feature also failed:

Memory integrity forced off "incompatible driver" STTub30.sys (STmicroelectronics)

Note that for my system the problem driver was STTub30.sys which was published via oem0.inf. Your details will probably be different so be careful to target the correct driver when uninstalling. Keep in mind that Microsoft does not recommend removing installed drivers. They do recommend that you update them but in my case I don't know where STTub30.sys came from and STmicroelectronics doesn't have an updated driver that I can find and install.

Enumerating and Removing Incompatible Drivers (Command Prompt)

I found a helpful video online by Britec09 (below for reference). Note that I didn't need to add any additional Windows features (Virtual Machine Platform and Windows Hypervisor Platform) to fix my problem.

How to Fix Core Isolation Incompatible Driver Issues

Command Prompt Attempt Using pnputil:

Open a command prompt as admin. Locate the provider name and verify the *.inf information matches the detail from the original attempt error message to enable memory integrity.

pnputil /enum-drivers

Attempt to delete the problem driver:

pnputil /delete-driver oem0.inf

My pnputil command failed above so I next tried Device Manager (Win-X, Device Manager):

1. From the View menu enable the "Show hidden devices" feature then "Devices by driver."
2. Right-click on the *.inf corresponding to your issue and select remove.
3. Reboot
4. Type "Core isolation" in the Windows search box to bring up the control panel.
5. Turn on the "Memory integrity" option.
6. If you were successful the next step is to reboot to enable.

Good luck!

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.