"The parameter is incorrect" when launching wsl

[KatamariJr]

Version

Microsoft Windows [Version 10.0.19044.1586]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

Open any wsl terminal or try running wsl from powershell.

Expected Behavior

It should work and allow execution as normal.

Actual Behavior

The parameter is incorrect.
[process exited with code 4294967295 (0xffffffff)]

I have tried using the .wslconfig + guiapplications fix as specified in other issues, but that did not change my results. After some effort with this, my pc restarted and WSL was working fine again, but now a few days later I am back to having this issue again. I also noticed that according to the wslconfig specs that guiApplications setting isnt even recognized if you arent on Windows 11.

Notable is that an Ubuntu 18.04 instance installed from the Microsoft Store running on WSL v1 will work as expected.

Diagnostic Logs

wsl.zip

[KatamariJr]

I also tried rolling back to kernel version 4.19.128 by running wsl --update --rollback, but the same results are occuring

[KatamariJr]

I was able to find a temporary workaround and more clear cause for this. I read #6085 (comment) and put together that my system had stopped working when i was on a different network with only wifi, but had been working when I was at home connected to an ethernet dock. I disabled my wifi network adapter and restarted my PC, which then allowed Hyper-V to create its virtual ethernet adapter, which I assume had been failing, and WSL2 started up without a hitch, and I could re-enable the adapter.

To narrow down the steps for reproducing:

• start the machine with only a wifi adapter enabled (my specific adapter is Intel(R) Wireless-AC 9560)

[hubertsvk]

I have the same problem
wsl --install
wsl --update
all works fine but when I installed WSL preview I cant start wsl
The parameter is incorrect. [process exited with code 4294967295 (0xffffffff)]
PS C:\Users\xxx> wsl.exe -l -v
NAME STATE VERSION
* Ubuntu Stopped 2

wsl --version
WSL version: 0.61.8.0
Kernel version: 5.10.102.1
WSLg version: 1.0.39
MSRDC version: 1.2.3213
Direct3D version: 1.601.0
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.778

[hubertsvk]

in EventLog I have this
The program dllhost.exe version 10.0.22000.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: e98
Start Time: 01d88df2825a5685
Termination Time: 4294967295
Application Path: C:\Windows\System32\dllhost.exe
Report Id: 79432537-c548-4a35-8f53-5c2639bbfafe
Faulting package full name: MicrosoftCorporationII.WindowsSubsystemForLinux_0.61.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Hang type: Quiesce

[clawsl]

I had a similar issue after changing the IP of a Nat network, which I'm using for one of my HyperV VMs. Once the change was done, my Default Network for HyperV disappeared and I could also no longer works with Ubuntu in WSL2.
To fix it, I tried many suggestions a simple networking reset + reboot after completely removing HyperV, Virtual Machine Platform and Windows Subsystem for Linux + reinstalling them after another reboot once the network reset was done. The error message however stayed. I also tried just creating a Nat Switch called WSL or an external Switch using my WiFi network, but that didn't help either.
I even tried upgrading to Window11 via the upgrade assistant, hoping the new OS would come with a fully working network setup, but that was also useless.

In the end I saw en error in the event log pointing to the NetNat service not being able to start. This then lead me to a SO article pointing to a potential registry issue with the settings under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\

Therefore, I tried resetting my network more thoroughly as suggested by one or more network protocols are missing and did a complete reset using the commands as admin

# release / renew ip + de/reregister dns 
ipconfig /release
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns

# network stack reset
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log 
netsh int ip reset all ip.log
netsh int ip reset ipreset.log
netsh int tcp reset tcp.log

For some netsh commands I got Access is denied.Resetting , OK! errors, which I fixed by granting access permissions in Regedit to all subkeys e.g. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}\26 for Everyone (Full Access) which was mentioned in the article and described there in more detail. Backup your full key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nsi\ first by doing an export to a file to be extra safe !)

Once the permissions were set, the netsh commands above worked without complaining about access.

Then I removed HyperV, Virtual Machine Platform and Windows Subsystem for Linux again rebooted and just installed HyperV after another reboot. To my joy, the previously missing Default Network adapter reappeared after that step.

Next I reinstalled Virtual Machine Platform and Windows Subsystem for Linux again and also deleted the old package information for the canonical package (as I was using Ubuntu) under %localappdata%\Packages (you need to take ownership first via right click Properties-> Security -> Advanced -> Owner (either administrators or your user is fine) and then grant yourself or administrators Full Control in Explorer).

After that I reinstalled the package via the store and WSL2 worked again for me.

[tyingq]

Getting this error as of today. Pretty frustrating that it's been around for more than a year with no obvious recourse.

[VaporumCoin]

Same, machine restarted last night im assuming windows update....what the hell microsoft, i have a production environment all setup that is now all screwed up after working for a year.

[whatcolor1]

The parameter is incorrect.
Error code: Wsl/Service/CreateInstance/CreateVm/E_INVALIDARG

[7-of-9]

+1
The parameter is incorrect.
Error code: Wsl/Service/CreateInstance/CreateVm/HCS/E_INVALIDARG

[PlasticCog]

Same here. This is pretty lame.

[lagset]

Getting this as of today. Yesterday it did just work normally.
Windows 11 23H2

[ferchor2003]

I had a similar issue after changing the IP of a Nat network, which I'm using for one of my HyperV VMs. Once the change was done, my Default Network for HyperV disappeared and I could also no longer works with Ubuntu in WSL2. To fix it, I tried many suggestions a simple networking reset + reboot after completely removing HyperV, Virtual Machine Platform and Windows Subsystem for Linux + reinstalling them after another reboot once the network reset was done. The error message however stayed. I also tried just creating a Nat Switch called WSL or an external Switch using my WiFi network, but that didn't help either. I even tried upgrading to Window11 via the upgrade assistant, hoping the new OS would come with a fully working network setup, but that was also useless.

In the end I saw en error in the event log pointing to the NetNat service not being able to start. This then lead me to a SO article pointing to a potential registry issue with the settings under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\

Therefore, I tried resetting my network more thoroughly as suggested by one or more network protocols are missing and did a complete reset using the commands as admin

# release / renew ip + de/reregister dns 
ipconfig /release
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns

# network stack reset
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log 
netsh int ip reset all ip.log
netsh int ip reset ipreset.log
netsh int tcp reset tcp.log

For some netsh commands I got Access is denied.Resetting , OK! errors, which I fixed by granting access permissions in Regedit to all subkeys e.g. HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}\26 for Everyone (Full Access) which was mentioned in the article and described there in more detail. Backup your full key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nsi\ first by doing an export to a file to be extra safe !)

Once the permissions were set, the netsh commands above worked without complaining about access.

I got the "Parameter is incorrect" after updating WSL with "wsl --update"
I followed the ipconfig and netsh commands proposed by clawsl and then restarted the PC. WSL would still give me the same error message.
I then did another "wsl --update" and that solved the problem

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!