Solved Can't turn on Memory Integrity PxHlpa64.sys incompatible driver

Haydon · Dec 16, 2023

x BlueRobot said:
Yes it is safe to use, I've used it dozens of times, and the syntax they've suggested is the older style which is compatible with earlier operating systems. It does the same what @trumpy81 mentioned: -d means /delete-driver and -f means /force.

I would personally disable the associated service first, reboot and then delete the driver package. You might want to use the /uninstall option as well.

The discussion has progressed beyond that point, it's now at
--------------------------
With

or

Without

quote...unquote
--------------------------

and

why the particular offending driver does not appear in the list of offending driver packages of pnputil

Read the whole thread.

Haydon · Dec 16, 2023

I tried running Autoruns again, but this time, I disabled the offending driver (unchecked the tick mark) before trying to delete it, but it still failed to delete it. When I restarted the machine, the offending driver was enabled again (the tick mark was present again)

LOL, if it was not a weekend, I would not have tried to have so much fun.

Haydon · Dec 17, 2023

I tried running Autoruns again, and lo and behold, this time the disablement of the incompatible driver PxHlpa64.sys remained so after a restart and I was able to delete the darn thing! A couple of restarts later, Memory Integrity was turned on and Core Isolation was all fixed, see screenshot below

I will mark this thread 'Solved'

Thanks to all who responded and special thanks to @Brink

Brink · Dec 17, 2023

Great news. :party:

Haydon · Dec 17, 2023

I ran a sfc /scannow and corrupted files were found that were successfully repaired. I ran sfc /scannow again and no violations found.

I'm not sure if the sfc /scannow thingie has anything to do with the issue at hand, but it was the most stubborn deletion of a file. Just let you all know, if you search the issue then there are many, many other stories out there, so here's another story