To be clear, yes the WD SES Driver is incompatible with Memory Integrity but that is a separate and unrelated issue to the one discussed herein.
The issue causing the problem discussed in this thread seems to be that the newest Defender Platform Network Inspection Driver, WdNisDrv.sys (Wd here is Windows Defender, not Western Digital), is also incompatible with Memory Integrity even though it doesn't report as such when enabling Memory Integrity or anywhere else that an average user would see. It is only reported in Event Viewer and, if you happen to notice, by virtue of the fact that the service isn't running in Services.msc when Core Isolation/Memory Integrity is enabled.
I have verified that this issue also occurs on systems which have never had external storage, or any Western Digital storage for that matter, attached to them.
Hi, pntless,
Thanks for your continued troubleshooting.
Hard drive info: perhaps anecdotal, but wanted to get it out of the way:
SSD with my OS on it, a main data drive where most things are mapped to (Docs, Downloads, etc etc), and then a Media drive. I don't think any of these are WD drives, and while I do have WD external removable drives, I haven't plugged any in since the system rebuild. I went into device drivers, and didn't see any WD drivers in there.
Bit locker:
Not using drive encryption.
Core Isolation issues:
I do NOT have any additional information underneath the toggle telling me why it failed. I kept searching on the internet and found... Microsoft's Device Guard and Credential Guard Readiness Tool. Took a while to be able to find information on how to use it. Used it.
To the best of my knowledge it was working FINE at the outset of my system rebuild process. I have info in device security of something being stopped from writing to memory on Aug 7 during my system rebuild. (Happens from time to time as you know, with things that could even be trusted.)
Here is information on why it is not working (Not going to include all the things that passed):
Incompatible HVCI Kernel Driver Modules found
Module: xtuacpidriver.sys
Reason: execute pool type count: 12
Module: iocbios2.sys
Reason: execute pool type count: 5
HSTIStatus: False
HSTI validation failed
HyperVisorPresent False
(But
VMMonitorModeExtensions True
VirtualizationFirmwareEnabled True
Virtualization firmware check passed)
====================== Summary ======================
Device Guard / Credential Guard can be enabled on this machine.
Looks like xtuacpidriver.sys has to do with the intel Extreme Tuning Utility. The iocbios2.sys is a windows driver but searching for it brings up results on the previous driver. When I am willing to fight with this MESS more, I can see if this needs to be updated. Or maybe it was updated in 1903/1909 and is messed up. I don't know.
And of course because this update just had to ruin everything, my poking around to try to figure out THIS found the following:
In Process Explorer (yes, running as administrator), Registry and Memory Compression are displaying "The system cannot find the specified file." I have never seen this before. I ran sfc /scannow, it found some problems and fixed them. I reran it until it found no problems. This didn't change what I am seeing in process explorer.
After the machine reset, I did -3- full virus scans with -3- different products. Of course, with how messed up some of the operating system components are, this may not mean anything :P
Really don't know what to do with my machine at this point. Kicking it does not seem productive.