System requirements
Intel 12th gen or newer, with VT-x, VT-d and VT-rp. How to check each one.
What you need #
| Processor | Intel Core, 12th generation (Alder Lake) or newer | Required. 11th gen and older cannot run our stack. |
|---|---|---|
| VT-x | Enabled in the BIOS | Listed as Intel Virtualization Technology. |
| VT-d | Enabled in the BIOS | Listed as VT-d, Intel VT for Directed I/O or IOMMU. |
| VT-rp | Enabled in the BIOS | Redirect Protection. Only exists on 12th gen and newer, which is why they are the floor. |
| Secure Boot | Enabled, with empty key databases | Enabled in the BIOS, but with its keys cleared so ours can be enrolled. |
| Memory Integrity | On | Windows Security, then Device security, then Core isolation. |
| Boot mode | UEFI with CSM disabled | Legacy or CSM boot is not supported. |
| Windows | Windows 10 build 18363 or newer, or Windows 11 | Windows 11 is recommended. |
| Access | Administrator account | The loader needs to elevate on first launch. |
Why the CPU matters #
VT-rp, Intel's redirect protection, is the feature our stack is built on, and Intel only shipped it starting with 12th generation processors. Without it there is nothing for us to run inside, so an 11th gen chip, a Xeon from the same era or any AMD processor simply will not work.
This is a hardware limit, not a licensing one. Support cannot enable it for you, and there is no compatibility mode. If your processor is older, the honest answer is that you should not buy yet.
Check your processor #
The generation is the first one or two digits of the model number after the dash. A Core i7-12700K is 12th generation; a Core i7-11700K is 11th and will not work. Newer naming such as Core Ultra 7 265K is well past the floor and is fine.
-
1.
Open Settings, then System, then About.
-
2.
Read the Processor line under Device specifications.
Or from PowerShell:
Get-CimInstance Win32_Processor | Select-Object Name
Check virtualization #
Windows will tell you whether virtualization is on, though it will not name VT-d or VT-rp specifically. Those you confirm in the BIOS itself.
-
1.
Open Task Manager and go to the Performance tab, then CPU.
-
2.
Look for Virtualization near the bottom right. It should say Enabled.
-
3.
Press Windows + R, type msinfo32 and press Enter.
-
4.
In System Summary, check that BIOS Mode says UEFI and Secure Boot State says On.
If Virtualization says Disabled, or BIOS Mode says Legacy, go to the BIOS page next.
Secure Boot State will read Off later, and that is expected
What is not supported #
- AMD processors of any generation.
- Intel processors older than 12th generation.
- Machines booting in Legacy or CSM mode.
- Virtual machines, cloud gaming boxes and remote desktop hosts.
- Locked OEM firmware that does not expose Secure Boot key management.
Not sure which side of the line you are on? Post your processor model and motherboard on Discord before you buy and we will tell you straight.
This page did not solve it? Ask our staff on Discord.