Windows 10: memory integrity and kernel-mode hardware-enforced stack protection getting off...

So I installed Valorant and there was a file named "vgk.sys" in Riot Vanguard which was showing incompatible and caused memory integrity and kernel-mode hardware-enforced stack protection off. To enable those, I uninstalled Valorant and turned those two on. It asked to restart my pc to enable these two options. But during restart it is showing an error message "Your pc ran into a problem and it needs to restart". It restarts on its own but after the restart, the memory integrity and kernel-mode hardware-enforced stack protection gets turned off automatically.I did sfc /scannow but it did not f

:)

 

Device security Kernel=mode hardware-enforced stack protection is off

Hi, and thanks for reaching out. My name is Bernard a Windows fan like you. I'll be happy to help you out today.

I understand the issue you have, there is nothing to worry I am here to help, this issue occurs when the processor is not compatible or not supporting Kernel-mode Hardware-enforced Stack Protection (KSHSP), in addition, I suggest updating your BIOS first then checking it again.

If the issue persists, kindly follow the steps from Cristiano, here's the link: https://answers.microsoft.com/en-us/windows/for...

Let me know how it goes and I hope that helps.

Bernard

 

No option for Kernel-mode Hardware-enforced Stack Protection in Core Isolation

Which list are you referring to?

According to this list, the processor is compatible.

Windows processor requirements Windows 11 supported Intel processors

According to this, "Kernel mode hardware enforced protection requires an 11th Gen or higher CPU. (Intel CET or AMD shadow stack support)"

https://www.reddit.com/r/Windows11/comments/12qkdj8/windows_security_app_update/

Rocket Lake is 11th Gen.

 

LiveKernelEvent BSOD "Kernel-Mode Hardware-Enforced Stack Protection" games

Hi Yitzhak,

Your minidump files all indicate a virtual driver named HoYoKProtect.sys that is usually associated to Genshin Impact as the cause of the system crashes, it seems that driver is incompatible with Kernel-Mode Hardware-Enforced Stack Protection

However, Microsoft released a patch for a bug in Defender last month involving LSA and that new patch has caused errors in Kernel-Mode Hardware-Enforced Stack Protection, so that update fixed one thing and broke another.

So the best option is to leave that disabled until Microsoft provide a patch for this new bug in the latest update.