WSL: WslRegisterDistribution failed with error: 0x80070057
Windows Version
Microsoft Windows [Version 10.0.25905.1000]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
- Install windows 11 canary build 25905 with iso, removing all programs but keeping files
- Install wsl with
wsl --install
Expected Behavior
WSL installs.
Actual Behavior
Wsl itself and Ubuntu installs. Then ubuntu starts and produce:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070057
Error: 0x80070057 ?????
Diagnostic Logs
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 30 (1 by maintainers)
I also got “Wsl/Service/CreateInstance/CreateVm/E_INVALIDARG” when I try to import my old wsl distribution instead of install.
Yes, It works, sorry I forgot to update.
downloading… let me try it.
Judging by the current issues, WSL is completely inoperable in this version of Windows. In the absence of a way to restore the Windows version, I tried to export the image of the WSL distribution and was unsuccessful. If the problem of WSL operation is difficult to solve, it is hoped that the part of the exported image can be fixed as soon as possible. In this way, some users can restore the working environment by reinstalling the system.
Just hit this same one this morning
After last nights update I encountered an error attempting to launch wsl in any way:
The parameter is incorrect. Error code: Wsl/Service/CreateInstance/CreateVm/E_INVALIDARG
Attempted solutions:
uninstall/reinstall wsl: result: encountered new error WslRegisterDistribution failed with error: 0x80070057 Error: 0x80070057 The parameter is incorrect.
disable/re-enable windows virtualization: result: no impact, error persists
added
guiapplications=falseto .wslconfig result: no impact, error persistslogs: https://aka.ms/AAljpom
Of course this gets fixed the day after I reinstall clean. lol
25915 fixed the bug
Experiencing the same issue solution please?
“Appreciate your patience - we’ve investigated your reports, and believe this should be fixed in the next flight. If WSL is something you use regularly, you may wish to roll back to the previous build until this is fixed”——Official response from Feedback Hub return to wsl1 is a workaround if you use nothing depending on wsl2… PS: This is a Hyper-V error so anything based on Hyper-V like WSA, Windows Sandbox etc. will also be affected, but there are also reports said that only WSA will be affected
same os version … same issue … same waitting …