aka.ms/enablevirtualization explained

Where the link goes

When we checked on 21 October 2026, aka.ms/enablevirtualization forwarded directly to the Troubleshooting Windows Subsystem for Linux page on learn.microsoft.com, jumping to the section for this error:

Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

So although the short name sounds general, the page it opens is WSL documentation for developers. Microsoft also has a plain-language support article, Enable virtualization on Windows, which the WSL page links to. We use both below. Neither asks you to sign in or download anything.

What the error means

WSL 2 runs Linux inside a lightweight virtual machine. That needs two things: the processor's virtualization feature switched on in the PC's firmware (UEFI or BIOS), and the Windows optional component called Virtual Machine Platform. If either one is missing, Windows cannot start the virtual machine and shows 0x80370102. The same section of Microsoft's troubleshooting page lists error 0x80070003 alongside it during installation.

Microsoft's support article explains the wider purpose: virtualization lets a Windows device emulate a different operating system, such as Android or Linux, which gives you access to more apps. Microsoft notes that many Windows devices already have virtualization enabled, so check before you change firmware settings. Before you begin, Microsoft suggests finding out your device model and manufacturer, because the firmware steps differ from one maker to another.

Fix 1: turn on virtualization in UEFI (or BIOS)

Microsoft's support article recommends opening its instructions on a second device first, because your PC will restart into the firmware. Its steps for Windows 11 are:

1. Open Settings > System > Recovery. On Windows 10 it is Update & Security > Recovery.
2. Next to Advanced startup, select Restart now.
3. Choose Troubleshoot > Advanced options > UEFI Firmware Settings > Restart.
4. Find the virtualization setting and turn it on. Its name and location depend on the PC maker. The manufacturer guides Microsoft links use names such as Intel Virtualization Technology (VT-x) and AMD Virtualization (AMD-V).
5. Save and exit. The PC restarts.

Microsoft's article links to the virtualization instructions of Acer, Asus, Dell, HP and Lenovo, and says virtualization is already enabled on Surface devices. It also warns: only change what you need to in the firmware, because adjusting other settings might stop Windows from starting.

Fix 2: turn on Virtual Machine Platform

1. Select Start, type Windows features and open Turn Windows features on or off.
2. Tick Virtual Machine Platform and select OK.
3. Restart when Windows asks.

Microsoft notes this step matters most on PCs that were upgraded from Windows 10 to Windows 11. If you install WSL with the single wsl --install command described in our aka.ms/wslinstall guide, the command enables the features it needs for you.

Fix 3: check the hypervisor is allowed to start

If virtualization and the Windows feature are both on but the error remains, Microsoft's WSL page suggests checking the boot configuration. In PowerShell opened as administrator, run:

bcdedit /enum | findstr -i hypervisorlaunchtype

If the result says hypervisorlaunchtype Off, the hypervisor is disabled. Microsoft's fix is bcdedit /set hypervisorlaunchtype Auto, followed by a restart. If you or another program set it to Off on purpose in the past, note what it was before you change it, so you can reverse the change if needed.

Command-line alternative

If you prefer a command to the Windows Features window, Microsoft's WSL offline-install instructions turn on the same component from PowerShell opened as administrator:

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Restart afterwards for it to take effect. Note that this only enables the Windows component. It cannot switch on virtualization in the firmware; that part always has to be done in the UEFI or BIOS settings.

Quick checklist

Work through the list in that order. Microsoft notes that you might need to restart after enabling Virtual Machine Platform, and a restart is also needed after any firmware change, so test WSL again only after the PC has fully restarted.

Other causes Microsoft lists

• Older processors. WSL 2 needs a CPU with Second Level Address Translation (SLAT). Microsoft gives Intel Nehalem (first-generation Core) and AMD Opteron as the starting points and says older CPUs such as the Core 2 Duo cannot run WSL 2.
• Other virtualization software. Microsoft says VMware and VirtualBox must be versions that support Hyper-V (VMware 15.5.5 or later, VirtualBox 6 or later), or be turned off.
• Running inside a virtual machine. If Windows itself is a Hyper-V virtual machine, nested virtualization has to be enabled from the host with Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true.
• Azure virtual machines. Microsoft notes nested virtualization is not supported on Azure VMs that use Trusted Launch.

Related errors with their own short links

WSL uses several aka.ms links in its messages. Error 0x1bc (WSL 2 requires an update to its kernel component) points to aka.ms/wsl2kernel, which we cover in the WSL install guide. Error 0x8007019e means the Windows Subsystem for Linux optional component itself is not enabled.

Checking whether the same PC can run Windows 11? Firmware settings such as TPM and Secure Boot live in the same menus; see aka.ms/windowssysreq. More links are in our aka.ms links directory.

Sources

• Microsoft Learn: Troubleshooting Windows Subsystem for Linux
• Microsoft Support: Enable virtualization on Windows