Intel Virtualization and TS in 24H2?

[ProgUn1corn]

Hi, a strange thing I've found recently. After updating to 24H2, TS no longer works when Intel VT is enabled in BIOS, but it worked before.

I have some pretty light virtual machine use, I just need it to run some programs with direct IO access. VT-D is enabled in BIOS, but Intel Virtualization Technology is disabled now in order to use TS.

Will this affect me using the VM? Thanks.

 

[unclewebb]

After updating to 24H2, TS no longer works when Intel VT is enabled in BIOS, but it worked before.

I have not installed 24H2 and I have not done any virtualization testing.

Will this affect me using the VM?

It probably will. Do some testing to find out. ThrottleStop needs direct access to the voltage control register which is not possible when virtualization is enabled.

 

[ProgUn1corn]

Edit: After some searching I've found that 24H2 tries to enable VBS in boot partition, checks if VBS is enabled and do this every boot. You need to disable Secure Boot, Credential Guard and VBS check in the partition.

Windows 11 24h2 hsot - how to disable Virtual Based Security | VMware Workstation

Trying to switch from a Windows 2025 host to Windows 11 24h2 host. AMD 8840U hardware. Done registery changes. Done Security Core setting change. Done

community.broadcom.com

GitHub - kozarevr/disableVBSandCredentialGuard: Virtualization-based security and Credential Guard

Virtualization-based security and Credential Guard - kozarevr/disableVBSandCredentialGuard

github.com

I used the Github one and it worked now. I can turn on VT-X and use my VM while using TS 9.7.2 normally.

Unfortunately disabling VT-X prevented me from running VM.

But this shouldn't be the case, I have used with VT-X enabled without problem for months. Maybe now Windows is default on VM even some VBS settings and hyper-V are off.

I have not installed 24H2 and I have not done any virtualization testing.


It probably will. Do some testing to find out. ThrottleStop needs direct access to the voltage control register which is not possible when virtualization is enabled.

I've found that VBS is still on even core isolation or that crap is disabled. Maybe need group policy or registry editing to make it work.

After reading the instructions in your signature, turned off core isolation (which it's off by it's own), turned off hypervisor platform and VM platform (which is not on by default), changed group policy, in msinfo32 still it says VBS is running. I even checked the registry where enbaleVBS is set to 0. Damn that MS crap.

I have not installed 24H2 and I have not done any virtualization testing.


It probably will. Do some testing to find out. ThrottleStop needs direct access to the voltage control register which is not possible when virtualization is enabled.

Probably it's time to update your signature