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

:)

 

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 the image it’ll get stuck here until I turn of the computer and turn it on again, though memory isolation will be off when done.

 

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?