Windows 11: Unable to enable WSL2 / Virtual Machine Platform - 'Changes are being reverted' loop

Question

when i try to activate "Windows Subsystem for Linux" and "Virtual machine platform" feature and restart, it gives me a "we couldn't complete the features, undoing chances" and boots back normal with the features disabled. my system environment is Windows 11, Virtualization is enabled, core isolation is disabled. i dont want to break the laptop because it is not my primary machine.

Answer 1

Hi nothing,

Has your issue been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

Domic V.

Answer 2

Hi nothing,

To fix the rollback loop when enabling WSL and the Virtual Machine Platform, first repair your system image by running sfc /scannow and dism /online /cleanup-image /restorehealth in an administrative terminal. Next, ensure your boot manager allows the hypervisor to run by executing bcdedit /set hypervisorlaunchtype auto. Finally, bypass the Windows Features graphical interface entirely by installing both features directly via the command line using the dism.exe /online /enable-feature command with the /norestart flag, and manually reboot your computer to apply the changes smoothly.

Domic V.

Answer 3

Use the manual/PowerShell path and verify all WSL2 prerequisites, since the GUI feature toggle is rolling back.

1. Verify virtualization and Hyper-V prerequisites
   • Confirm hardware virtualization is enabled in UEFI/BIOS following the guidance in Enable virtualization on Windows. Only change the virtualization-related setting; other changes can prevent Windows from booting.
   • Ensure the CPU supports SLAT, which is required for WSL2. Older CPUs without SLAT cannot run WSL2 even if the feature installs.
2. Enable required features via PowerShell
   • Open PowerShell as Administrator.
   • Enable Virtual Machine Platform explicitly:

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

   • Enable Windows Subsystem for Linux if not already enabled (per the manual install guidance):

          Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
     

   • Restart the machine after these commands.
3. Check for common WSL/virtualization issues
   • If installation fails with errors like 0x80370102 or 0x80070003, follow the WSL troubleshooting guidance:
     • Make sure virtualization is enabled in BIOS/UEFI (CPU virtualization options).
     • Confirm the system drive (usually C:) is used for WSL distributions.
   • Ensure the Virtual Machine Platform optional component is enabled and the system has the required virtualization capabilities.
4. Validate Hyper-V launch configuration
   • After reboot, open elevated PowerShell and run:

          bcdedit /enum | findstr -i hypervisorlaunchtype
     

   • If the output shows hypervisorlaunchtype Off, enable it:

          bcdedit /set hypervisorlaunchtype Auto
     

   • Restart again.
5. Check for third‑party hypervisors
   • If VMware or VirtualBox is installed, ensure they are on versions that support Hyper-V (e.g., VMware Workstation 15.5.5+ or VirtualBox 6+), or disable/uninstall them, as they can interfere with the Hyper-V subset used by WSL2.
6. Confirm WSL2 availability on Windows 11
   • WSL2 is supported on Windows 11 Home and Pro, provided both Virtual Machine Platform and Windows Subsystem for Linux are enabled. Once the above steps succeed without rollback, WSL2 should be available.

If the feature installation still reverts after using DISM and meeting all prerequisites, the next step is to follow the broader WSL troubleshooting guidance and, if necessary, consider repair options for Windows before attempting again.

---

References:

• Troubleshooting Windows Subsystem for Linux
• Manual installation steps for older versions of WSL
• Enable Virtualization on Windows
• Frequently Asked Questions about Windows Subsystem for Linux