Windows Defender Memory Integrity - incompatible drivers

[Flashbin]

Hi,

 

I want to enable the memory integrity feature of Windows Defender. For that, you need compatible drivers. I only have one which is preventing me from turning the feature on - ssudcdf.sys:

 

It's from 2014, so already not great. My biggest issue: I don't know what that driver is for. After a bit of googling, I found out that it's some form of mobile phone driver.

I had installed the Samsung phone driver because I own a Galaxy S10 - but I deinstalled that one, so it can't be the issue. 

Also, I can't find any device in the Device Manager which uses that driver. My S10 apparently uses a generic Microsoft driver.

 

My best guess is that it's from when I was flashing /e/ OS on my Galaxy S7 - because somewhere it also said that this driver is a "SAMSUNG Android ADB Interface Driver". In that case, I definitely don't need it anymore.

 

So my conclusion is that I don't need this driver. But I couldn't find out how to remove it safely without it appearing in the Device Manager.

 

Does someone know how I would go about doing that?

 

Thanks!

[Kilrah]

Use "show hidden devices" in device manager and remove the Samsung phone entries, ticking "Remove driver".

[Flashbin]

25 minutes ago, Kilrah said:

Use "show hidden devices" in device manager and remove the Samsung phone entries, ticking "Remove driver".

I don't have any phones listed in the Device Manager (hidden devices turned on) since I deinstalled the Samsung mobile phone driver.

 

[Kilrah]

You can use Driver Store Explorer to wipe old drivers:

https://github.com/lostindark/DriverStoreExplorer

 

If you enable the "OEM INF" column it'll show you the file name so you should be able to locate oem64.inf and remove it too.

[Flashbin]

9 minutes ago, Kilrah said:

You can use Driver Store Explorer to wipe old drivers:

https://github.com/lostindark/DriverStoreExplorer

 

If you enable the "OEM INF" column it'll show you the file name so you should be able to locate oem64.inf and remove it too.

Thanks for the tip, with the Driver Store Explorer I managed to delete that driver!