WSL: Can't update from WSL to WSL2 on x86-64, error message "The Parameter is Incorrect." (Partial solution)

Environment

Windows build number: Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Your Distribution version: Ubuntu 20.04 (problem affects all distributions on the Microsoft store)
WSL 2

Steps to reproduce

Disable/Enable Windows Subsystem for Linux in Optional Windows Features. Disable/Enable Virtual Machine Platform in Optional Windows Features (also tried Hyper-V and Windows Hypervisor Platform, as well as combinations of the three). Reboot. Enable SVM option in BIOS (motherboard MSI B350m PRO VDH, latest BIOS version, CPU supports virtualization). Install the WSL 2 kernel update. Reboot. Run the command ‘wsl --set-version Ubuntu 2’.

WSL logs:

Expected behavior

Running the command “wsl --set-version Ubuntu 2” should convert the current installation of Ubuntu to WSL2.

Actual behavior

PS C:\Users\<username> wsl --set-version Ubuntu 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The parameter is incorrect.

Additional Information

I have made sure I’m using the latest BIOS supported on my motherboard, and that my CPU (AMD Ryzen 5 1500x) supports virtualization. SVM is enabled. I found no issues on GitHub that were identical to mine. Some were similar, but the solutions to those issues did not solve my problem. I have uninstalled and reinstalled the WSL 2 kernel update several times.

From what I can gather, error message “The parameter is incorrect” is often associated with a problem in the Hypervisor/Virtual Machine Platform.

UPDATE

To see how I fixed my specific problem (network issue, not ARM64-based, so your mileage may vary), see https://github.com/microsoft/WSL/issues/6085#issuecomment-708858336

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 33 (3 by maintainers)

Most upvoted comments

We’ve identified the bug that introduced this regression and will work on servicing this ASAP. In the meantime I’d suggest reverting this update (and pausing future updates until this is fixed).

Thanks - I’m assuming this ticket will now track the different issue with the same result that we’re seeing on intel chipsets?

Hi @falloutphil @Alovchin91 - it is fixed now for arm64 - see #6090 (comment)

I’m not a moderator or involved with Microsoft - but yes - https://github.com/microsoft/WSL/issues/6090 is arm64+KB4579311 related and this ticket is for x86/x64.

Same problem here after installing KB4579311 on Surface Pro X (SQ1).

Can confirm that uninstalling KB4579311 through the Control Panel fixes the issue on the Surface Pro X (arm64), have paused updates for now.

These were the three updates:

image

Any workarounds would be appreciated.