If you are trying to tighten up your security by adding Virtualization-Based Security (aka VBS) to your Windows 11 you might find this error:
Core Isolation Memory Integrity
Incompatible Drivers WDCSAM64_PREWIN8.SYS
Driver date: 11/29/2017Driver version: 1.2.0.0Published name: oem26.inf
This is an old driver that ships with both Windows 10 and Windows 11 and very few people need it. In fact we have never run into a situation of any machine using WDCSAM64_PREWIN8.SYS .
Fortunately, it is very easy to remove:
You do NOT need a reboot so you can immediately retry to enable CORE ISOLATION and you should see a prompt to reboot once Core Isolation > Memory Integrity is turned ON.
This website uses cookies.
View Comments
Thanks a lot. it worked.
it's telling me one or more devices are presently installed using the specified INF.
deleted all WD software... any fix for this?
Thanks!
I tried to use the above fix to remove wdcsam64.sys, but got this message. Any suggestions? I didn't attempt to change the path. Should I?
Failed to delete driver package: The system cannot find the path specified.
PS C:\Users\gjmcc>
Thanks
Hi, I like to know how the fix this issue, mine is caused by oem28.inf associated with wdcsam64.sys . Do you got any sensible suggestions or solutions?
Thank in advance.
Henry, it should work for your oem28.inf associated with wdcsam64.sys. It doesn't matter which oem number it is assigned to. Mine is oem84.inf (driver date is 10/8/2015 and install date is 3/1/2021 version 1.1.0.0) I had no problem.
there were 2 .inf files with the wdcsam drivers, should I delete them in sucession?
Thanks a lot it worked =)
Brilliant! That pesky driver pops up more than it should, even when using certain brands of pen drive/memory stick. Previously, I had to reinstall Windows 11 to be rid of it. Now it can be removed in seconds.
Thanks so much for publishing this simple fix which worked perfectly!
OH THANK YOU! I am screaming it from the top of my lungs. That incompatible message was driving me nuts. Thanks so much for the correct way to fix the problem. Please have a great day!
Great fix, the offending INF file was oem34.inf on my wife's laptop.
thank you much, mine was oem30.inf and your cure worked beautifully, even for an old lady!