Windows 10: STTub30.sys deleted but memory isolation broken

So I struggled with an earlier situation regarding the driver known as STTub30.sys and ended up deleting it with autorun. Afterwards I thought my solution was fixed and I turned on memory isolation at last just to be stuck at my computer’s loading screen. No blue screen simply being stuck in booting up phase. I can start my computer regularly but just turning it off while it’s in this mode and it’ll immediately just return to normal except memory isolation is turned off again, the option to turn it on works but upon restarting it never fully restarts, failing to get me to the login. As seen in

:)

 

Memory integrity forced off "incompatible driver" STTub30.sys

The solution is easy. Time to be invested, less than a minute. Regards.

All that you guys have to do (in case this file isn't associated with an oemxx.inf published name) is rename (and not delete) the driver from STTub30.sys to STSTub30.sys.old and you'll be able to activate Memory Integrity. In case it's associated with an oemxx.inf published name, just delete it using device manager.

 

STTub30.sys stmicroelectronics incompatible driver causing Mempry integrity off

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?

 

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

I was able to find a replacement at this location:

qmk_dfuse/STTub30.sys at master · qmk/qmk_dfuse

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.