This solution worked for me. Memory integrity is now turned on.
Memory integrity forced off "incompatible driver" STTub30.sys (STmicroelectronics)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Recently my memory integrity has been forced off due to an "incompatible driver" preventing the service from running. The incompatible driver in question is from STmicroelectronics driver "STTub30.sys" In my attempt to fix this, I uninstalled this driver and tried windows update to see if my PC would automatically reinstall this driver but no luck. Now when I turn Memory integrity on and restart my PC (as it prompts me to do so) my computer is stuck on the loading up screen, and I must force shutdown my pc and turn it on again in order to use it. I tried finding the specific driver online from the STmicroelectronics website to manually reinstall it but no luck
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.
54 answers
Sort by: Newest
-
Anonymous
2022-10-22T21:13:29+00:00 -
Anonymous
2022-10-22T15:51:09+00:00 I followed this to the letter. When i restart my pc it gets stuck at the MSI emblem. No loading or anything happens. I can hard reset and it brings back up windows with the memory integration option off. What do now.
-
Anonymous
2022-10-20T04:52:02+00:00 an you post your official from them on github for us?? or something and make it known where you do??? i have a BRAND NEW LAPTOP fresh out of the box {1week} and has win11 pre installed and it had this issue right from the 1st!!!!! start up of the laptop! sad that Microsoft preaches security yet they fail to provide updates to fix this OLD .sys file
-
Anonymous
2022-10-19T19:55:16+00:00 Sorry if you did not find the files on the ST Microelectronics support/forum website. Since my original case with them was closed, I opened another one asking what is the publicly accessible URL to download this file. I'll post here when I hear back from them.
Cheers,
Patrick.
-
Anonymous
2022-10-19T19:46:57+00:00 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.