wslg: After most recent WSL update, WSL won't start
Environment
Windows build number: 10.0.21364.0
Your Distribution version: Ubuntu 18.04
Your WSLg version: 1.0.17.1
WSL Update Version: 5.10.16
Steps to reproduce
- Update WSL to support WSLg
- Run the distro
WSL logs:
Expected behavior
WSL should start
Actual behavior
WSL fails to start with:
The parameter is incorrect.
[process exited with code 4294967295]
The solutions is to disable WSLg as per: https://github.com/microsoft/WSL/issues/6839 by disabling it in .wslconfig file via
[wsl2]
guiapplications=false
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 16
- Comments: 35 (4 by maintainers)
Correct, system distro runs at same VM as user distro, In WSL, all distro run on same VM. You can check with “hcsdiag list” command to see which VM host WSL instance.
And the reason this only happen with GUI support is because, in order to make efficient graphics data transfer between host, it allocate larger cache in MMIO space. This doesn’t happen without WSLg enabled.
We are working on fix this, thanks for reporting this issue.
@hajekj , thanks for reporting this and providing wsl.etl, according to the log, your CPU only support 36bits physical address. We are working on the fix to support this type of CPU.
“Virtual machine ‘Virtual Machine’ cannot be started. The upper MMIO region (0x00000012001ff000) is above the supported physical address range. Make sure that the upper MMIO region is below 0x0000001000000000.”
I’m in the same boat!
Everything was working after installing the WSLg Preview before updating to Windows Insider update build 21364. It seems like I lost everything I invested in rebuilding my WSL2 Ubuntu 18.04 before this crash.
This is sad that there’s a good chance that Windows Insider will impact WSL installations.
I was getting the message “The parameter is incorrect” which I thought was due to the guiapplications setting. It was actually fixed by reverting to using Windows Console Host instead of Windows Terminal Preview. Apparently noting to do with the network either.
It would help if the message was less ambiguous about where the issue is!
@ABQJuan - The fix is not in 21370, but will be in this week’s Insider Dev build (21376).
pls refer to：
https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#networking-issues
Networking issues If the issue is about networking, run networking.bat in an administrative command prompt:
$ git clone https://github.com/microsoft/WSL --depth=1 %tmp%\WSL $ cd %tmp%\WSL\diagnostics $ networking.bat Once the script execution is completed, include both its output and the generated log file, wsl.etl on the issue.
https://github.com/Microsoft/WSL/blob/master/diagnostics/networking.bat
@StarName That message appears when the vNIC for WSL2 can’t be created. Try resetting your network: https://www.howtogeek.com/265870/how-to-reset-your-entire-network-in-windows-10-and-start-from-scratch/
@Meltrust
1, GUI https://www.mydockfinder.com/
2, dark file explorer : Kali Linux Thunar
enjoy it😊
@Meltrust seems to be this one: MyDockFinder
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).
Issue will be closed soon see https://github.com/microsoft/WSL/issues/6839#issuecomment-829440007
@hajekj how i can get my wsl.etl