Virtualisation Extensions do not work on 3rd party hypervisors

Question

Synonyms Legend:

VM = Virtual Machine

VBS = Virtualisation Based Security

Hyper-V = (the) Windows Hypervisor

---

Basic system information:

• CPU: Intel i5 (10th gen)
• dGPU: Nvidia GeForce GTX 1650
• RAM: 32GB (DDR4)
• Storage: 1TB (SSD, 99% healthy, TRIM-enabled)
• PC made year: 2020s (>4 yr. old)
• BIOS: up-to-date
• OS: up-to-date
• OS Edition: Windows 11 Pro N
• OS Version: 24H2 (release channel)
• OS Build: 26100.3775

WINDOWS WAS INSTALLED FROM PHYSICAL MEDIA. I USED MEDIA CREATION TOOL, NOT CUSTOM IMAGES. THIS IS A FRESH INSTALL (not a reinstall or reset) WITH EVERYTHING LEFT WITH THE DEFAULTS.

I never enabled HYPER-V or WSL!

Checking for corruption was done using this logic:

dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /restorehealth

-- "Reboot"

sfc /scannow

-- "Reboot"

chkdsk

-- "Reboot"

I scanned my PC using Microsoft Defender to check if there are any viruses: there are none.

---

Background context:

"VBS" is a security feature that isolates processes from one another using Hyper-V.

Running a VM strains the PC components's IO, making the use of Windows laggier.

By design, x86 allows only ONE hypervisor to use those virtualisation extensions.

I use VMWare Workstation Pro instead of Hyper-V as hypervisor because:

• Hyper-V doesn't support GPU Paravirtualisation (unlike Windows Sandbox and WSL)
• ease of use (unlike the other's skeleton UI)

Since Windows 11 comes with hardened defaults unlike Windows 10:

• nested virtualisation (Intel VT-x / AMD-v )
• and I/O virtualisation (Intel VT-d / AMD-vi)

became unavailable.

I require VBS for some of my apps, hence I cannot afford to disable it, nor to go to Windows 10.

I cannot move to linux/mac/other because I have apps that depend on having a HOST Windows running, not a VM Windows.

---

Clarifications:

I made this thicc block of text so that there are as little confusion as possible. Please tell me if I misinformed somewhere.

I would also like to have a fruitful discussion instead of an exchange of "dry words". That was already done several times by the Microsoft technical support.
(I don't blame them for that. It's just that the problem is so complex I'd rather not use Windows anymore at how bad it had become)

For your information, I am NOT a business person. I use my PC for personal use, even if my questions can be... "technical-ish". (I am a gamer)

I do NOT pay for support. I consider that if my apps used to work in the past and are being updated, there is no such thing as "it doesn't work". Windows is known for its broad compatibility with apps, not for being "just an ebook tablet".

I tried to manually enable virtualisation extensions on virtualbox and vmware, run one at a time, but still with no effect.

---

The question:

1. How can I make "nested virtulisation" and "io virtualisation" work with VirtualBox/VMWare Workstation?
2. If it's not possible, then how can I pass the dGPU to a Hyper-V VM? (I don't run Windows inside it)
3. Why "Windows Hypervisor" feature exists if VMWare can't make use of it? Isn't that Windows feature supposed to give hypervisors like VMWare hyper-v-like access to the virtulisation extensions?

---

Post Scriptum:

Thank you in advance.