Forum Discussion
How to remove OEM drivers Causing Memory Integrity Problems.
I had a situation where my Core Isolation was Disabled by Samsung Drivers that were causing Memory Integrity Problems. This prevented me from being able to Reenable the Core Isolation In Defender.
I found a simple solution to the problem by removing the Problematic Drivers by using PowerShell and the PNPUTIL command.
The first step is to identify the drivers OEM Number.
Open PowerShell as Administrator.
Do this by Typing pnputil /enum-drivers then hit Enter.
Now Find the Driver that is causing the Problem and Identify the OEM#.INF
Now we can Force Delete the Problematic Driver causing you Problems.
Type pnputil /delete-driver oem#.inf /uninstall /force.
Do this for each Driver causing an Issue.
Now you can Reenable Defender Core Isolation.
# is the number identified in the OEM listing.
Be aware that removing Drivers can have unforeseen consequences so use this with Caution.
12 Replies
Thanks, it worked!
Awesome, thank you so much...it worked 😉
Here’s a quick and straightforward way to fix Memory Integrity problems caused by problematic OEM drivers:
- Identify the Problematic Driver:
- Open PowerShell as Administrator.
- Run: pnputil /enum-drivers
- Look for the driver causing the issue and note its OEM#.INF (e.g., oem12.inf).
- Remove the Problematic Driver:
- Run: pnputil /delete-driver oem#.inf /uninstall /force
- Replace # with the actual OEM number you found.
- Repeat this for all problematic drivers.
- Reenable Core Isolation:
- Go to Windows Security > Device Security > Core Isolation, and toggle Memory Integrity back on.
⚠️ Important: Removing drivers might cause device issues, so ensure the drivers aren’t critical or have alternatives before deleting them. Always proceed with caution!
Thanks, it worked and Memory Integrity is back on.
- Identify the Problematic Driver:
u can also use cmd as administrator to remove the driver, just type pnputil /enum-drivers , and them use pnputil /delete-driver oem#.inf , thats all.
worked perfect to repair issues with logiteck rudder pedals and keyboard! thanks SargeAlabamatom1963
- Thanks for this. For anyone out there with problems removing Touptek driver, this solution works ...
Alabamatom1963
The result I received...PS C:\Windows\system32> pnputil /enum-drivers
pnputil : The term 'pnputil' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ pnputil /enum-drivers
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (pnputil:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundExceptionYou need to use the correct version of PoweShell and must run it as administrator. I found the correct version and launched it with run as administrator and it works.
Hi Dave Similarly I received pnputil as an unknown script. I am using Windows 11 and the Memory Integrity is unable to be turned on as oem60.inf recorded as driver ew_usbenumfilter.sys is the driver blocking memory integrity. The driver is shown as Huwawei.
Regards Neil
You must have c:\windows\system32 in your system path.
