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

[nhobson99]

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 #6085 (comment)

[licanhua]

possible dup of #6031. Can you try create a network manually to see if there is error from Hyper-V

[nhobson99]

licanhua, would you mind elaborating? What network am I creating with Hyper-V? I'd be happy to give it a shot.

[licanhua]

You can create a external network, then delete it.
If you didn't see any error, please collect wsl log, then share the log link, and I can help to see where the error is coming from.
If you see an error, it's definitely something wrong with Hyper-V , and you may get better support from community

[joshkerr]

I'm also having this error. I'm using a Microsoft Surface Pro X with the new SQ2 chip. There are no options to install Hyper-V. I also don't have the Hyper-V manager. I had no problem upgrading my WSL 1 to 2 distros on my Surface Pro X with the SQ1 chip. Could this issue be related to the new hardware?

[licanhua]

I received this comment From: nhobson99, but I don't know why I can't see it in this thread
Sent: Tuesday, October 13, 2020 6:27 PM
Subject: Re: [microsoft/WSL] Can't update from WSL to WSL2, error message "The Parameter is Incorrect." (#6085)

Well, I created the virtual network switch in Hyper-V Manager with all default settings, then I had an idea. I unplugged my USB WIFI adapter that I typically use for my home network, then ran the conversion again, and it worked! Not sure actually if it was the virtual network switch itself that fixed it, or not being on a USB-WIFI connection, but thank you for putting me on the right path.

[licanhua]

@joshkerr If you are with Windows Home edition, there is no Hyper-V manger, but you should still see Virtual Machine Platform feature.
Hyper-V manager is not a must have for WSL 2, so it's OK to only have Virtual Machine Platform enabled.
You can collect wsl log, then I can help you to investigate if it's hyper-v network issue or not.

[tamoanxx]

I two am having the same issue on my new surface pro x SQ 2

[joaomoreno]

Yup this just broke on my Surface Pro X as well. It was working just fine yesterday. I have tried many things including restarting, uninstalling all distros, removing WSL. Nothing seems to fix it.

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

Press any key to continue...

[licanhua]

@joaomoreno Can you check the windows update history to see if there is new Windows update yesterday?

[tamoanxx]

I am on an Surface Pro X with SQ2 I have uninstall several of the updates that installed and I even tried on the Insider Channels. Also I have included the feedback logs.

[joshkerr]

I did the same. I’m currently on Insider Beta and still getting the same error.

[joaomoreno]

These were the three updates:

Any workarounds would be appreciated.

[benhillis]

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).

[tamoanxx]

@benhillis Do you have any specific way that we can uninstall KB4579311. I am getting this error:

[nhobson99]

I successfully upgraded to WSL2 on both my laptop and my desktop now, and the problem ended up being networking related. The conversion would sometimes partially work when I unplugged my USB WIFI adapter, but then the OS hung when plugging it back in. I tried creating a Hyper-V network, but got a "generic error" when trying to do so (which is why I deleted my original comment saying I'd fixed it, since that was actually misleading information.)

What eventually worked permanently was uninstalling WSL, Hyper-V, Windows Hypervisor and Virtual Machine Platform all from optional windows features, uninstalling network drivers from device manager, rebooting, reinstalling all hypervisor and WSL features, and rebooting again. Finally the changes stuck, and I can use WSL2 on my desktop again. Will update if the change is no longer permanent.

What made this error unique was that there was no actual error number, just a generic-looking error message. The error message itself is from Hyper-V, which really needs a better error message than "The Parameter is Incorrect."

[licanhua]

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).

This only applies to KB4579311 + ARM64(like Surface Pro X). "The Parameter is Incorrect." is a different issue if you are not with Surface Pro X and this KB

[asampal]

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).

Is the fix specific to addressing the problem on Surface devices or would it also correct the issue I observed in #6091 where I wasn't using a Surface?

[ninuwa]

I assume it's specific to ARM64, my Samsung Qualcomm has the same problem after updating.

[licanhua]

yes. to be exactly, it's ARM64 related

[nhobson99]

I believe another issue should be created for ARM-based systems, since that was not in the initial scope of my issue. The problem should get more attention that way, and should help with taking attention away from the problem I was having initially. licanhua or benhillis, could you change the "bug" and "fixinbound" tags for this issue? As I don't believe the original issue was actually solved, which was about Hyper-V parameters and the vague error message. Thanks.

[licanhua]

Agreed, I re-opened #6090 to track the ARM64 issue

[dennisameling]

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

[Alovchin91]

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

[ac1982]

I have the same problem here. pause the update right now KB4579311 on Surface Pro X

[nhobson99]

Changed the title of this issue to dissuade people commenting with different issues. If you are on x86 and not ARM, see #6085 (comment). Otherwise, see #6085 (comment).

[Alovchin91]

@nhobson99 Maybe also reopen #6090 then?

[nhobson99]

More @licanhua or @benhillis, I'm not a dev so I don't actually have the authority to reopen a closed issue. Either way, these issues are used internally to track regressions, but there is a bug fix already inbound for ARM based devices, so I don't believe it needs to be reopened (as it is aptly labeled "fix inbound"). Just trying to get attention for ARM devices into the right place.

[Alovchin91]

More @licanhua or @benhillis, I'm not a dev so I don't actually have the authority to reopen a closed issue. Either way, these issues are used internally to track regressions, but there is a bug fix already inbound for ARM based devices, so I don't believe it needs to be reopened (as it is aptly labeled "fix inbound"). Just trying to get attention for ARM devices into the right place.

Oh, sorry, I thought you were a moderator 😅 The ARM issue is not fixed for the end users (us) yet, so it's strange to me that it's closed.

[falloutphil]

Confirmed issue seen on Intel Core i9-9900K @ 3.60GHz - an identical clean Windows roll-out (2004.19041.264) and import of the same WSL tar was done across several machines - I didn't see this issues on Intel Xenon CPUE E4-1225 v5 @ 3.30 GHz, or Intel Core i7-6700 @ 3.40GHz. As I only have one i9 I can't conclusively say that this is the factor by testing on a second alas. It's definitely not (just) an ARM issue tho.

[mirogl]

More @licanhua or @benhillis, I'm not a dev so I don't actually have the authority to reopen a closed issue. Either way, these issues are used internally to track regressions, but there is a bug fix already inbound for ARM based devices, so I don't believe it needs to be reopened (as it is aptly labeled "fix inbound"). Just trying to get attention for ARM devices into the right place.

Oh, sorry, I thought you were a moderator 😅 The ARM issue is not fixed for the end users (us) yet, so it's strange to me that it's closed.

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

[falloutphil]

Thanks - I'm assuming this ticket will now track the different issue with the same result that we're seeing on intel chipsets? From the comments - there hasn't been conclusive resolution in all these cases.

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

[mirogl]

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 - #6090 is arm64+KB4579311 related and this ticket is for x86/x64.

[ChristianBauerEng]

I successfully upgraded to WSL2 on both my laptop and my desktop now, and the problem ended up being networking related. The conversion would sometimes partially work when I unplugged my USB WIFI adapter, but then the OS hung when plugging it back in. I tried creating a Hyper-V network, but got a "generic error" when trying to do so (which is why I deleted my original comment saying I'd fixed it, since that was actually misleading information.)

What eventually worked permanently was uninstalling WSL, Hyper-V, Windows Hypervisor and Virtual Machine Platform all from optional windows features, uninstalling network drivers from device manager, rebooting, reinstalling all hypervisor and WSL features, and rebooting again. Finally the changes stuck, and I can use WSL2 on my desktop again. Will update if the change is no longer permanent.

What made this error unique was that there was no actual error number, just a generic-looking error message. The error message itself is from Hyper-V, which really needs a better error message than "The Parameter is Incorrect."

Can confirm this. After disabling the builtin WiFi network adapter in device manager Hyper-V automatically created new network adapters. After this I could upgrade the distro and re-enable the WiFi adapter afterwards.