How to resolve WDCSAM64 (Western Digital) driver incompatibility to enable memory integrity and core isolation?

Anonymous
2024-08-05T12:07:04+00:00

I have tried:

1 windows/WD driver updates

2 Western digital guidance on updates

3 Western digital hardware, software, and driver removal

4 Western digital admin manual deletion most recently which resulted in an error "Failed to delete driver package: the system could not find the path specified."

5 Continuing dialogue with WD but its not working so far

The diver details, as MS identified are below:

wdcsam64.sys

WesternDigitalTechnologies

Device: WD SES Device

Import Date: 3/2/2023

Driver date: 1/18/2011

Driver version 1.0.9.0

Published name: oem0.inf

Any guidance appreciated.

Windows for home | Windows 11 | Devices and drivers

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 No comments

16 answers

Sort by: Newest
  1. Anonymous
    2024-12-02T17:53:32+00:00

    Head to the Western Digital web site and download and install the WD Drive utility. The installation loads the correct software. This has worked on my Lenovo desktop and my MSI laptop

    Was this answer helpful?

    80+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-11-23T20:45:45+00:00

    Hello,

    I also have this issue and I use an external WD EasyStore hard rive. It is not clear to me from these responses if this driver error can be resolved so that the WD EasyStore external drive continues to function and is not impaired or impacted?

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-11-16T21:40:03+00:00

    Hi Dave:

    I had the same problem on Windows 11 and your step here did not help at first.

    I had to do more search and got to Fix: Wdcsam64.sys Memory Integrity Error on Windows 11. Followed the whole steps and went through to the end, but that did not turn on the Memory Integration as well. However, it seemed there were 2 of the wdcsam64, and the last one was the wdcsam64.sys oem0.inf file that was listed. Even though the result stated that I had deleted all and no WD Discover or wdcsam64 could be found.

    So, I followed this step right here by you, DaveM121. The result stated that the file was deleted. After restarting the file, went back to Core Isolation and go to Memory Integration and turned it on. Voila, it did. You'll need to restart the computer again.

    Note: pnputil /delete-driver oem0.inf /uninstall /force

    • Space: When you type the above on Command Prompt as Administrator, note that there is a space after each of the following: pnputil, oem0.inf, uninstall
    • Zero: in the word oem0 - the last is the number zero (not letter O)

    Thank you, Dave!

    MM 11/16/2024

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-11-16T18:17:57+00:00

    I have the same issue...did you ever get this resolved?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-11-01T03:06:43+00:00

    Your suggestion did not work. The term 'pnputil/delete-driver' is not recognized as the name of a cmdlet, function, script file, or operable program.

    I tried using:

    The Published Name: oem175.inf

    but that didn't work either.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments