I have the same issue. After update to Windows 10 Insider Preview Build 21364 WSL does start any more.
In terminal appears "The parameter is incorrect."

Same issue here. After update to Windows 10 Insider Preview Build 21364 WSL does start any more.

[wsl2]
guiapplications=false

fixes the problem.

I have enabled wslg and wsl stopped working I have reported this issue to wslg repository
you can fix wsl by adding this to your .wslconfig file
[wsl2]
guiapplications=false

I was having the same issue and this fixed it for me.

Thanks!

Same issue here. After update to Windows 10 Insider Preview Build 21364 WSL does start any more.

[wsl2]
guiapplications=false

fixes the problem.

Thanks!
It works now.

@github348's fix worked for me, too.

For what it's worth, the fix here didn't work for me, nor did any of the other suggestions on that issue. I couldn't install any more distros; they all failed with error 0x80070057.

Same issue here. After update to Windows 10 Insider Preview Build 21364 WSL does start any more.

[wsl2]
guiapplications=false

fixes the problem.

Thank you! Wasted so much time on this...

One more note, as I had to look this up to:
the ".wslconfig" file goes is in your %UserProfile% folder (ie. c:/users/[name] ). The file may not exist, you may have to create it.

I have enabled wslg and wsl stopped working I have reported this issue to wslg repository
you can fix wsl by adding this to your .wslconfig file
[wsl2]
guiapplications=false

Worked for me.

This fix also works for me, although the reason I was trying to install it, was to try out the gui support., so I guess this means I can't

I have enabled wslg and wsl stopped working I have reported this issue to wslg repository
you can fix wsl by adding this to your .wslconfig file
[wsl2]
guiapplications=false

Worked for me.

This fix also works for me, although the reason I was trying to install it, was to try out the gui support., so I guess this means I can't

More details about the underlying cause can be found here and here. A fix is being worked on.

I have enabled wslg and wsl stopped working I have reported this issue to wslg repository
you can fix wsl by adding this to your .wslconfig file
[wsl2]
guiapplications=false

Thank you. I have almost lost entired night trying to solve this issue. Now it's up and running.

On a german Windows Version it's simply Falscher Paramter, on might think it's a different problem, but this fix does the trick.

And it does not hinder any previous settings that let me use gui apps through X410.

Though i just notice, that gitkraken now can display it's icon (rather than the one of X410, that was used before the newest updates). May be unrelated, since i updated the WSL-Kernel as part of finding a solution.

See reason of why this could happen in microsoft/wslg#33

We've identified an issue with some CPUs and a fix is inbound.

@benhillis could this be also related to your fix ? MicrosoftDocs/WSL#798

@P4R4DiSi4C To know if it's related just use this wslconfig option to disable GUI support.
Also remember to run wsl.exe --shutdown to make the changes effective.

@P4R4DiSi4C To know if it's related just use this wslconfig option to disable GUI support.
Also remember to run wsl.exe --shutdown to make the changes effective.

Okay, then it's not related thanks :)

On a german Windows Version it's simply Falscher Paramter, on might think it's a different problem, but this fix does the trick.

And it does not hinder any previous settings that let me use gui apps through X410.

Though i just notice, that gitkraken now can display it's icon (rather than the one of X410, that was used before the newest updates). May be unrelated, since i updated the WSL-Kernel as part of finding a solution.

Yes, it's a good idea👍. wsl2 ver.5.10.16.3 works @win10 ver. 21359, but not work when update 21364!
thunar and gedit icon now can display on taskbar.👍

tks.

This need more investigation...
I'm suspecting that this whole issue was due to a missing ".wsl2config" file. I'm only wondering this could have work by just creating an empty file could.
Also, we got to be on the lookout with upcoming Windows Insider updates breaking WSL installations.
I have an idea which I'm going to post soon to test this scenario.

For now... creating the ".wsl2config" file with the content:

[wsl2]
guiapplications=false

It Works!!

Repro Steps
(*** Please do this on a VM ***)

Duplicate the situation, now that I got my WSL to work , I'm went back to delete the config file: ".wslconfig" in the User Profile folder, run cmd "wsl --shutdown". Reboot not necessary.

Start WSL and now I'm back to square one! So, I can't open WSL.

Then try to recover with the following WSL Settings Options:
I did the "Repair Option", didn't work.
I did the "Reset Option, that didn't work neither.

I did uninstall all distro, remove the WSL Update, uncheck WSL Feature, then Reboot machine

Check back the WSL Feature, Reboot machine, install back the WSL Update then manually create the WSL config file "wslconfig" in your Windows User Profile folder" c:\Users\username" with the following entries:

[wsl2]
guiapplications=false

Proceed to Download and Install UBUNTU-20.04
Open WSL and it's working again!!

Bottom-line: WSL needs to have the configuration file ".wslconfig" , or it won't start. So, you didn't need to uninstall WSL to get it to work.

This issue is well-understood. Unless something unexpected happens this should be fixed with next week's Insider Dev build.

The fix mentioned here didn't work for me. After putting
[wsl2]
guiapplications=false

into %userprofile%\.wslconfig I get another error:

{Application Error}
The exception s (0xPress any key to continue...

@andalou

Did you do open a PowerShell console (as Admin), and ran the command: "wsl --shutdown"?
Then you should try to start wsl again.

@andalou

Did you do open a PowerShell console (as Admin), and ran the command: "wsl --shutdown"?
Then you should try to start wsl again.

Yes I did it, I get the same message

@P4R4DiSi4C To know if it's related just use this wslconfig option to disable GUI support.
Also remember to run wsl.exe --shutdown to make the changes effective.

I already did it. I put
[wsl2]
guiapplications=false

into %userprofile%\.wslconfig and I did, as administrator, wsl.exe --shutdown but I get another message, namely:
{Application Error}
The exception s (0xPress any key to continue...

That is 21364.1 build

@andalou

Please, can you provide a print-screen of the message you're getting?
thx

@andalou

Please, can you provide a print-screen of the message you're getting?
thx

@andalou

That message, I haven't seen it. I ended up with the pain of resetting and reinstalling everything (all components/features) to finally get it to work.

Today I updated my Windows 10 Insider to Build 21370.

This time WSL works! But now fighting with Docker-Desktop(3.3.1), which installs but doesn't work in WSL2.
I hope someone can offer a resolution.

@MaximoTrinidad I'm running it right now without problem. I had to add guiapplications=false to .wslconfig file before launching Docker Desktop for first time though.

@andalou

That message, I haven't seen it. I ended up with the pain of resetting and reinstalling everything (all components/features) to finally get it to work.

Today I updated my Windows 10 Insider to Build 21370.

This time WSL works! But now fighting with Docker-Desktop(3.3.1), which installs but doesn't work in WSL2.
I hope someone can offer a resolution.

My advice regarding Docker is to install it on WSL directly.

I have enabled wslg and wsl stopped working I have reported this issue to wslg repository
you can fix wsl by adding this to your .wslconfig file
[wsl2]
guiapplications=false

This works for me.

After so many Trials finally Docker is running.

Thanks so much

Fixed adding .wslconfig file to %UserProfile%. Thank you

PS C:\WINDOWS\system32> wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.
PS C:\WINDOWS\system32> wsl --status;cmd /c ver
Default Distribution: Ubuntu-20.04
Default Version: 2

Windows Subsystem for Linux was last updated on 02/05/2021
WSL automatic updates are on.

Kernel version: 5.10.16

Microsoft Windows [Version 10.0.21370.1]

Fixed adding .wslconfig file to %UserProfile%. Thank you

PS C:\WINDOWS\system32> wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.
PS C:\WINDOWS\system32> wsl --status;cmd /c ver
Default Distribution: Ubuntu-20.04
Default Version: 2

Windows Subsystem for Linux was last updated on 02/05/2021
WSL automatic updates are on.

Kernel version: 5.10.16

Microsoft Windows [Version 10.0.21370.1]

TKS. I will have a try.

I have enabled wslg and wsl stopped working I have reported this issue to wslg repository
you can fix wsl by adding this to your .wslconfig file
[wsl2]
guiapplications=false

This did not do anything for me.. Restarted machine & WSL and reinstalled WSL with the .wslconfig file but it didn't work!

The fix for this issue (not a workaround) is in build 21376.

Fixed adding .wslconfig file to %UserProfile%. Thank you

PS C:\WINDOWS\system32> wsl --set-default-version 2
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
The operation completed successfully.
PS C:\WINDOWS\system32> wsl --status;cmd /c ver
Default Distribution: Ubuntu-20.04
Default Version: 2

Windows Subsystem for Linux was last updated on 02/05/2021
WSL automatic updates are on.

Kernel version: 5.10.16

Microsoft Windows [Version 10.0.21370.1]

The parameter is incorrect.

[process exited with code 4294967295]

PS X:\app\tmp\WSL\diagnostics> wsl --status;cmd /c ver
Default Distribution: Kali-linux
Default Version: 2

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

Kernel version: 5.10.16

Microsoft Windows [Version 10.0.21370.1]

Build 21376 releases today. We encourage you to turn GUI applications back on, as that should now be fixed (you can remove guiapplications=false from .wslconfig).

Build 21376 releases today. We encourage you to turn GUI applications back on, as that should now be fixed (you can remove guiapplications=false from .wslconfig).

Confirmed, GUI is now working

Build 21376 releases today. We encourage you to turn GUI applications back on, as that should now be fixed (you can remove guiapplications=false from .wslconfig).

Confirmed, GUI is now working

Can u give me a link or the way to enable GUI?

Build 21376 releases today. We encourage you to turn GUI applications back on, as that should now be fixed (you can remove guiapplications=false from .wslconfig).

Confirmed, GUI is now working

Can u give me a link or the way to enable GUI?

https://github.com/microsoft/wslg

Confirmed, GUI is now working Update 21376. Tks.

In my case, after 3hrs installing Windows Insider build 21376, on my old Lenovo T430s, and removing the line:
"guiapplications=false
" on my .wslcinfig file ., I got an error two times:

"Windows SubSystem for Linus was terminated.

I had to use the command in the PowerShell console:

wsl --shutdown

`Then, I was able to enable open WSL2with graphics enabled.

What a ride!

I'm glad this is finally resolved!

Build 21376 releases today. We encourage you to turn GUI applications back on, as that should now be fixed (you can remove guiapplications=false from .wslconfig).

Works now, thanks!