Core Isolation turned off due to WDCSAM64_PREWIN8.SYS incompatibility

Anonymous

I have been running Windows 11 successfully on my Microsoft Surface for some time now with no problems.

Within the last day or so, I all of a sudden got a notification that Core Isolation has been disabled due to an incompatible driver, WDCSAM64_PREWIN8.SYS.

From what I can see, this driver is related to Western Digital. However, I do not have any Western Digital devices attached to my Surface, nor have I recently added/installed anything from Western Digital.

I have tried searching for this driver but have come up empty.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Select the Startbutton and type “Core isolation”.
Select the Core Isolation system settings from the search results to open the Windows security app.

On the Core isolation page, you’ll find Memory integrity along with the toggle to turn it on

If you receive a notification / message says that the memory integrity can't be turn on follow the below steps.

Try to scan and fix.
If it is not solved, please click on "Review any driver incompatibilities".

3.We can see a driver or more.

Please note the published name here is "oem46.inf"
Select the Start button and type “Device Manager" and follow as shown below.

Select the right driver from Device manager"oem46.inf" and right click and select remove driver.

Example :-

7. System needs to be restarted after removal of the driver.

Hopefully this will solve your issues no need to install any software for this.

0 comments

168 additional answers

Anonymous

2022-09-29T22:11:18+00:00

I tried all the solutions that LurkingZombie_ provided and they still didn't work, so I used this site:

https://windowsreport.com/administrator-permission-delete-folder/

I was able to change permissions to 'Everyone' and that worked.

I can not provide a play by play, but a mix of all the solutions worked in some way. Good luck!

Thanks buddy!

I don't want to mess around too much. With the risk braking something I might even realize until later down the road.

I think the best thing really (as someone else mentioned) is to wait for MS and the various companies behind these incompatible drivers to sort their own mess and make sure we have up-to-date drivers which won't cause this issue in the first place. It's not really our job as end users.

Think I'll spend my time on more fun stuff...such as enjoying myself in VR in MSFS :-)
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Monkey57 3,535 Reputation points

2022-09-13T12:48:47+00:00

Is there a space after the 49, that should not be there?

Is your internal 'Disk drive' as shown by device manager a WD hard drive ?

(although this may not matter, as an internal drive should have it's own oemxx.inf and not be depending on an obsolite driver-> system required/detected Microsoft drivers will generally be automaticly reinstalled by windows, if needed; except in some OEM/Manufacturer and/or user very customized computers). ****

If not, did you 'show hidden devices', and delete from Device Manager the external hard drive, before running the Windows Terminal command, after safely removing the external drive?

Note: my described device was an Asus with WDCSAM64_PREWIN8.SYS incompatibility .
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-09-13T12:08:41+00:00

Same thing with my Surface Pro 6. So far Microsoft customer service hasn't been able to resolve this.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-09-12T13:50:46+00:00

this solved it perfectly

thank you
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments