-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.Windows 11 Support Center.
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.Windows 11 Support Center.
- HP Community
- Gaming
- Gaming Notebooks
- Who Me Too'd this topic

Create an account on the HP Community to personalize your profile and ask a question
05-03-2022 03:06 AM - edited 05-04-2022 08:52 PM
Background:
Microsoft Virtualization-based Security, or VBS, uses hardware virtualization features to create a secure environment which can host a number of security features. One area of vital system resources that VBS must protect from malicious use is processor model-specific registers, or MSRs. In order to provide a robust security platform, MSRs must be protected from misuse from malicious kernel mode code. To enforce this, VBS monitors/controls access to all MSRs and only allow kernel mode code to access MSRs. But MSR access control will cause Intel Extreme Tuning Utility (XTU) not work since it cannot access MSR to set/get processor parameter.
Symptom:
In latest Omen Gaming Hub (v1101.2204.3.0), Undervolting/Overclocking/Performance Control will be blocked if Microsoft VBS (Virtualization-Based Security) is enabled.
TS Steps/Workaround:
- From Search -> msinfo32 and open
- From System Information, identify Virtualization-Based Security Status is enable (Running) or not
- If Virtualization-based security is Running, follow steps as below to disable
- From Settings -> Privacy & security -> Windows security -> Device security -> Core isolation -> Core isolation details -> Switch Memory Integrity Off
- From Control Panel -> Programs -> Click “Windows features on or off” -> Locate and uncheck Hyper-V, Microsoft Defender Application Guard, Virtual Machine Platform, and Windows Hypervisor Platform -> Click OK
- Reboot system, and check Omen Gaming Hub feature.
- From Settings -> Privacy & security -> Windows security -> Device security -> Core isolation -> Core isolation details -> Switch Memory Integrity Off
Reference: