Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2 - Windows 19041.264 - WslRegisterDistribution fails with error 0x80070057 - Incorrect parameter #5293

Open
devsuitup opened this issue May 29, 2020 · 32 comments
Labels
failure-to-launch failure to launch

Comments

@devsuitup
Copy link

devsuitup commented May 29, 2020

  • Microsoft Windows [version 10.0.19041.264]

  • What you're doing and what's happening:
    I updated to this version of Windows.
    I already have docker on this machine, that detected WSL2 possibility.
    I followed https://docs.microsoft.com/fr-fr/windows/wsl/install-win10 to the letter, with an apparent success.

  • What's wrong / what should be happening instead:
    When installing Debian, then ubuntu I get the same result at the initial lauch
    image

Also docker is having a similar issue when trying to register its distribution :

[Engines ][Error] Start failed with Failed to deploy distro docker-desktop to [...]\AppData\Local\Docker\wsl\distro: exit code: -1
 stdout: Paramètre incorrect.

i tried to uninstall WSL et install it again, I tried to reset, delete and reinstall images, reinstall docker, etc. Always stops here. Also not an issue of legacy console. I tried to stop, start, restart, and tried in between LxssManager.

Thank you for your attention !

@devsuitup devsuitup changed the title WslRegisterDistribution fails with error 0x80070057 - Incorrect parameter WSL2 - Windows 19041.264 - WslRegisterDistribution fails with error 0x80070057 - Incorrect parameter Jun 2, 2020
@devsuitup
Copy link
Author

Please, I really need some help people, i re-installed everything (wsl, wsl2, windows components, etc..)
Same result :

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 ParamÞtre incorrect.

@benhillis
Copy link
Member

@devsuitup - Could you please take a trace so I can figure out where the error is coming from?https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-detailed-logs

@devsuitup
Copy link
Author

Hi @benhillis , thank you for your attention.
You will find the logs attached to this post, in a zip file -- .etl isn't supported by github

lxcore_logs.zip

Thanks !

@benhillis
Copy link
Member

@devsuitup - Thanks for the logs. It looks like the failure is coming from trying to create our virtual network. Could you please also collect the networking logs detailed here:
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#9-networking-logs

@devsuitup
Copy link
Author

@benhillis FYI, after your answer I uninstalled NordVPN, Hamachi, FortiClient and restarted the machine -- and got the same issue.

Here is the trace : https://aka.ms/AA8lxay

@devsuitup
Copy link
Author

@benhillis Any news ?

@mwt
Copy link

mwt commented Jul 27, 2020

I solved a similar problem for myself (#5660) by uninstalling HyperV under "Turn Windows features on and off". Does this happen to work for you, @devsuitup, as well?

@mkuder
Copy link

mkuder commented Aug 31, 2020

I had this problem after installing Ubuntu or Ubuntu 20.04 either from the Store or PowerShell, the latter still complained that no distributions are installed. I had HyperV already disabled and LxssManager was running. What finally fixed it was just restarting the computer and Ubuntu 20.04 ran fine then. Using Windows build 19041.450 (2004 feature update).

@dmitridb
Copy link

dmitridb commented Jan 5, 2021

Amusingly, this only was fixed for me after I turned hyper-v on. I figured it was somehow essential to the operation of WSL2, so it's funny hearing that turning it off worked.

@therealkenc therealkenc added the failure-to-launch failure to launch label Feb 11, 2021
@kall
Copy link

kall commented Mar 11, 2021

I created a new Virtual Switch in Hyper-V Manager.
Then it works well.
0x80070057 error did not occurred.

@tigercosmos
Copy link

Same issue. None of the methods above work :(

I have tried the following:
Turn on and off Hyper-V
Enable and disable WSL
Install and uninstall Ubuntu Package
image

Windows version 20H2

@tigercosmos
Copy link

This is still not resolved by the latest update for 20H2.
I am wondering that not body encounters this issue but we?
Seems only few discussion about the 0x80070057.

@tigercosmos
Copy link

I finally find a solution. Change back to WSL 1 works for me.

@CoolCold
Copy link

Happens to me as well with latest build 21364

  • system info
PS C:\WINDOWS\system32> wsl --status;cmd /c ver
Default Version: 2

Windows Subsystem for Linux was last updated on 22/04/2021
The Windows Subsystem for Linux kernel can be manually updated with 'wsl --update', but automatic updates cannot occur due to your system settings.
To receive automatic kernel updates, please enable the Windows Update setting: 'Receive updates for other Microsoft products when you update Windows'.
For more information please visit https://aka.ms/wsl2kernel.

Kernel version: 5.10.16

Microsoft Windows [Version 10.0.21364.1]
  • networking
PS C:\WINDOWS\system32> netsh interface show interface

Admin State    State          Type             Interface Name
-------------------------------------------------------------------------
Enabled        Connected      Dedicated        Wi-Fi
Enabled        Disconnected   Dedicated        Local Area Connection
Enabled        Disconnected   Dedicated        Ethernet
  • networking on WSL2 machine with beta channel and WSL2 working fine
PS C:\WINDOWS\system32> netsh interface show interface

Admin State    State          Type             Interface Name
-------------------------------------------------------------------------
Enabled        Disconnected   Dedicated        Ethernet
Enabled        Connected      Dedicated        Local Area Connection
Enabled        Connected      Dedicated        Wi-Fi
Enabled        Connected      Dedicated        vEthernet (Default Switch)
Enabled        Connected      Dedicated        vEthernet (Ethernet)
Enabled        Connected      Dedicated        vEthernet (WSL)
Enabled        Connected      Dedicated        vEthernet (Wi-Fi)

virtual platform/hyper-v is installed (as you see wsl --status do not complain)

@StarNamer
Copy link

I got the insider update to 21364 and was looking to try out the new GUI feature for WSl, but both my Debian and Ubuntu installations would not start with the message "The parameter is incorrect".

Tied uninstalled both and reinstalling but both still report:
WslRegisterDistibution: failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

At least I'm not the only one...

@renanlido
Copy link

I solved this problem by returning to the previous version of windows thereby removing the Windows 10 Insider Preview Dev Build 21364.1 version.

@renanlido
Copy link

renanlido commented Apr 22, 2021

WSL2 distro not starting since 21364 build #6839
Apparently solves this problem as well.

@fractalspace
Copy link

fractalspace commented Apr 25, 2021

I got the insider update to 21364 and was looking to try out the new GUI feature for WSl, but both my Debian and Ubuntu installations would not start with the message "The parameter is incorrect".

Tied uninstalled both and reinstalling but both still report:
WslRegisterDistibution: failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

At least I'm not the only one...

(replacing my last comment)
Success!: Here is what worked for me:
On an Administrative command line:
> wsl --set-default-version 1
Then install the distribution of your choice (e.g. > wsl --install -d kali-linux)

Error is gone, and distribution is installed successfully (takes a while)

@fractalspace
Copy link

I got the insider update to 21364 and was looking to try out the new GUI feature for WSl, but both my Debian and Ubuntu installations would not start with the message "The parameter is incorrect".
Tied uninstalled both and reinstalling but both still report:
WslRegisterDistibution: failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.
At least I'm not the only one...

(replacing my last comment)
Success!: Here is what worked for me:
On an Administrative command line:
> wsl --set-default-version 1
Then install the distribution of your choice (e.g. > wsl --install -d kali-linux)

Error is gone, and distribution is installed successfully (takes a while)

But the error returns if I switch to wsl version 2

@mtncork
Copy link

mtncork commented May 4, 2021

I am getting this behavior, "Incorrect parameter" and the shell not created with insider build 21370 for Linux 18.04. Same behavior for WSL1 or WSL2.

From the Event Log in PerfView it looks like there's a failure creating a virtual machine due to an incorrect parameter:

ThreadID="15,496" FormattedMessage="onecore\vm\compute\shared\vmwp\lib\workerprocess.cpp(1315)\vmcompute.exe!00007FF66FD2BDF3: (caller: 00007FF66FC4E45C) Exception(50) tid(3c88) 80070057 The parameter is incorrect. CallContext:[\VirtualMachine_Start] " TraceData="onecore\vm\compute\shared\vmwp\lib\workerprocess.cpp(1315)\vmcompute.exe!00007FF66FD2BDF3: (caller: 00007FF66FC4E45C) Exception(50) tid(3c88) 80070057 The parameter is incorrect. CallContext:[\VirtualMachine_Start] " VmName=" - " VmId=" - " StackFrame="<<<EXCEPTION_DURING_VALUE_LOOKUP InvalidCastException>>>" Module="[{ Name="C:\WINDOWS\system32\vmcompute.exe", BaseAddress="140696412815360", SizeOfImage=4091904, TimeDateStamp=1438749299 },{ Name="C:\WINDOWS\SYSTEM32\ntdll.dll", BaseAddress="140703339642880", SizeOfImage=2109440, TimeDateStamp=1581716554 },{ Name="C:\WINDOWS\System32\KERNEL32.DLL", BaseAddress="140703317295104", SizeOfImage=774144, TimeDateStamp=-257251206 }]"

I was unable to attach wsl.etl.

Default Distribution: Ubuntu-18.04
Default Version: 2

Windows Subsystem for Linux was last updated on 5/4/2021
WSL automatic updates are on.

Kernel version: 5.10.16

Microsoft Windows [Version 10.0.21370.1]

@mtncork
Copy link

mtncork commented May 4, 2021

I fixed this. I was missing a .wslconfig file in my user directory.

@gmag11
Copy link

gmag11 commented May 5, 2021

WSL2 distro not starting since 21364 build #6839
Apparently solves this problem as well.

This worked in my setup, thank you

@timmy3780
Copy link

On an Administrative command line:

wsl --set-default-version 1
then install the Linux.
Window needs to update the wsl documentation.

@corneliusroot
Copy link

I created a new Virtual Switch in Hyper-V Manager. Then it works well. 0x80070057 error did not occurred.
I was able to replicate this. Creating a new switch worked! I shared it on my site:
https://www.tidbitsfortechs.com/2022/04/wsl2-wont-start-0x80070057-the-parameter-is-incorrect/

@kgambrah
Copy link

Removing the existing install with wsl --unregister ubuntu-18.04 and installing again worked for me.

@amirhoseinJ
Copy link

Anyone having this issue might also want to try cleaning existing ".wslconfig" file which could cause the problem.

@jfrgagnon
Copy link

I had that issue on Ubuntu and Ubuntu 20.04 after installing the WSL2-Linux-Kernel . I don't know why it broke my WSL2 installation, but I realized that it was the kernel setting in the ./.wslconfig file that was creating this bug...

Skipping this setting with "#" in front of the line resolve the issue for me...

@taksqth
Copy link

taksqth commented Jul 13, 2023

I have the same problem, tried a couple different options but no luck.

  • I was able to install the distro by rolling back to wsl 1. I'm not able to update to wsl2 later, it results in the same error. This happens at least on both Ubuntu, Ubuntu-22.04 and Debian, I did not try others.
  • There is no .wslconfig file in my %UserProfile% directory
  • wsl does not list (prior to the wsl1 installation) any distros installed, it's a clean setup
  • Going a little deeper in the point above, I've tried deleting everything. WSL, the distros and I have disabled the "Virtual Machine Platform" and "Windows Subsystem for Linux" features. Reinstalling WSL reenabled the first one automatically, the second one only comes back after I manually enable it. The error happens regardless if it's on or off after this procedure. I even tried cleaning the microsoft store cache.
  • This is all after I've reset my windows installation (keeping my old files).
  • I've tried disabling and enabling network adapters based on WslRegisterDistribution failed with error: 0x80070057 #8216 (comment) , since I have both ethernet and wifi. It also didn't work.

@as-thanhdao
Copy link

the latest update of Windows is suck, tried to rollback then it works now.

@tek-aevl
Copy link

^This

@aristizabal95
Copy link

Indeed, it appears the windows update Windows 11 Insider Preview 25905.1000 (rs_prerelease) was the problem. Today I installed Windows 11 Insider Preview 25915.1000 (rs_prerelease) and the issue is gone now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failure-to-launch failure to launch
Projects
None yet
Development

No branches or pull requests