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

Error: 0x80070057 The parameter is incorrect #10287

Closed
1 of 2 tasks
tyingq opened this issue Jul 13, 2023 · 2 comments
Closed
1 of 2 tasks

Error: 0x80070057 The parameter is incorrect #10287

tyingq opened this issue Jul 13, 2023 · 2 comments

Comments

@tyingq
Copy link

tyingq commented Jul 13, 2023

Windows Version

Microsoft Windows [Version 10.0.25905.1000]

WSL Version

WSL version: 1.2.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5,15,90,1

Distro Version

Ubuntu

Other Software

No response

Repro Steps

WSL stopped working. Trying to use it results in this error:

PS C:\WINDOWS\system32> wsl --install Ubuntu
Ubuntu is already installed.
Launching Ubuntu...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

Expected Behavior

Wsl should work

Actual Behavior

WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

Diagnostic Logs

WslLogs-2023-07-13_10-31-06.zip

@tyingq
Copy link
Author

tyingq commented Jul 13, 2023

WSL suddenly stopped working today, I didn't change anything about the machine, WSL, etc. I first noticed it because Docker Desktop complained with this error:

Failed to deploy distro docker-desktop to C:\Users\UsernameHere\AppData\Local\Docker\wsl\distro: : The parameter is incorrect. 
Error code: Wsl/Service/CreateVm/E_INVALIDARG

So, I tried using wsl from a cmd.exe window, and get the error below:

WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 The parameter is incorrect.

There are many issues here and in the wslg repo citing the same "parameter is incorrect" thing. I tried some of the recommended fixes:

  • turning the hyperv windows feature completely off.
  • turning the hyperv feature off, then on.
  • adding a hyperv switch
  • disabling the gui features via guiapplications=false in the .wslconfig file under the [wsl2] key
  • various sequences of uninstalling/reinstalling either everything (wsl, virtual machine platform, hyper-v), or one component at a time, with and without hyper-v, and so on.

I did attach the logs.

If MS is unable to address this, I'd appreciate a pointer to an open issue that I can follow.

@tyingq
Copy link
Author

tyingq commented Jul 13, 2023

Rolling back Windows 11 canary fixed it. Closing the issue.

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

No branches or pull requests

1 participant