Windows 10: Memory integrity forced off "incompatible driver" STTub30.sys STmicroelectronics

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

:)

 

Windows 10 - Memory Integrity - Incompatible Drivers

Good day all,

Please could someone advise how I might identify and safely remove/disable/update the following incompatible drivers, so that memory integrity can be re-enabled.

The incompatible drivers are as follows;
- ftdibus.sys
- wdcsam64_prewin8.sys
- PxHIpa64.sys
- SaiH0C2D.sys
- tib.sys

Autoruns lists nearly all of these files however I have not used this utility before, so thought it's best I ask first.

Any and all suggestions are very much appreciated!

Windows Ver.: Windows 10 20H2 Build 19042.870

Many thanks,
Koray

- - - Updated - - -

Bump!

 

incompatible drivers

Hi kspak,

None of those drivers are stored in the Driver folder in System32, that is very strange.

Okay then the associated software will need to be re-installed.

1

hidusbf.sys is

Some USB Mouse Rate Adjuster by SweetLow

2

sttub30.sys is

Generic STM USB Driver by STMicroelectronics

3

xhunter1.sys is

XIGNCODE3 System Guard by Wellbia.com Co.

 

unable to enable memory integrity windows 10 PRO 2004

(BUMP) 6/23/20

the two drivers (included with windows) xusb21.sys (Microsoft) and STTub30.sys (STMicroelectronics) are still interfering with my enabling Core Isolation. Nothing is using the two drivers, and deleting the drivers and their .inf files (oem18.inf, oem18.pnf
and oem130.inf and oem130.pnf) but the files keep getting put back by windows. I have already determined that the files are not being used at anytime during my windows sessions, and deleting the files does not cause windows to complain that it can't find a
driver.

Why is a driver not being used by windows blocking my attempts to activate memory integrity?