This is the way that worked for me. It follows reliable procedure and Windows commands, ensuring success.
[A] First, open Windows Powershell with the needed privileges:
- Use the Start menu search to find "powershell".
- It appears in the list of results.
- Run it as an administrator:
- On Windows 11, it shows a list of 4 options to the right of the Windows Powershell entry.
- Choose the second option, "Run as Administrator".
- If you are on some version that does not show these 4 options, instead right-click the Windows Powershell entry.
- Then choose "Run as administrator" from the dropdown.
- On Windows 11, it shows a list of 4 options to the right of the Windows Powershell entry.
[B] Next, use Powershell to find your Western Digital driver information:
- Enter the following command in the Powershell terminal window: pnputil /enum-drivers
- The terminal displays a long list of drivers and their details.
- Use the terminal search function to find your driver. This is typically done by pressing Ctrl + Shift + F
- You may also do this in older versions by right-clicking the terminal window and selecting Find.
- Enter "Western Digital" in the search.
- The terminal scrolls down to find the matching text.
- At the top of the driver entry, copy the value to the right of "Published Name", something like "oem23.inf".
- You can select the driver name with the mouse, and then either: right-click to copy, or press Ctrl + C
[C] Next, remove the conflicting drivers:
- Delete the driver by entering pnputil /delete-driver with your driver's Published Name.
- For the example in step B.4, this becomes pnputil /delete-driver oem23.inf
- Return to step B.2 and repeat until there are no more search matches.
- The driver removal is complete.
[D] Lastly, recheck and finish:
- Return to the Windows Security app's Device security tab, where it shows Core isolation. Run the Memory integrity check again.
- When you have successfully removed all Western Digital drivers, the check will pass.
- It will still tell you the memory integrity is off, and this is normal.
- Restart Windows to complete the process.
Best regards,
Niko