WSL: WSL2 fails to start following 18965 update
-
Your Windows build number: (Type
verat a Windows Command Prompt)Microsoft Windows [Version 10.0.18965.1000] -
What you’re doing and what’s happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
I noticed that Docker Desktop was reporting that Ubuntu 18.04 was not installed, when I was recently using the WSL2 tech preview prior to the current insider update. When I tried to launch from the command line, I received an error: 0xffffff
C:\Users\ccurw>wsl
Error: 0xffffffff
C:\Users\ccurw>ubuntu
Error: 0xffffffff
Since the ubuntu install was already existing, I attempted to install ubuntu1804 from the store, and when trying to run, i receive a similar error, this time with slightly more detail:
C:\Users\ccurw>ubuntu1804
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0xffffffff
Error: 0xffffffff (null)
Press any key to continue...
-
What’s wrong / what should be happening instead: I’m expecting to get a bash prompt after running
wsl,ubuntu, orubuntu1804, and I’m expecting docker desktop to pick up the WSL install -
Strace of the failing command, if applicable: (If
some_commandis failing, then runstrace -o some_command.strace -f some_command some_args, and link the contents ofsome_command.stracein a gist here). strace of thewslcommand: https://paste.cisien.com/f/lvoovmt3.strace -
For WSL launch issues, please collect detailed logs. logs taken of the
wslcommandlxcore_kernel.etl: https://paste.cisien.com/f/hts2g5mi.etllxcore_user.etl: https://paste.cisien.com/f/sjtjk1z3.etllxcore_service.etl:https://paste.cisien.com/f/zzffoqa3.etl
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 30
For anyone who’s trying to fix this, it wasn’t working for me as port 53 was bound. Use Resource Monitor > Network > Listening Ports to find out what has it bound, and stop the service temporarily.
I was having this issue and it resulted to be my port 53 being used by AcrylicService. After stopping the service and installing the distro on wsl 2 worked
Disabling SharedAccess/Internet Connection Sharing (ICS) solved my problem, DNSCrypt still enabled though.
If you have the DNSCrypt problem. change the DNSCrypt service startup type from Automatic to Automatic (Delayed Start) it will solve the problem.
In case anyone else has this issue. Simple DNSCrypt was the problem for me.
i had to stop DNSCrypt and SharedAccess services.
I have AcrylicDNS. Temporary disabled it, fixed the issue. Alter port for no future issues
I have DNSCrypt too. Temporary disabled it, fixed the issue
Here’s a workaround to make it works again:
Stop-Service com.docker.serviceNote: You can use other methods to stop this service.Start-Service com.docker.serviceI got the same error with os build 18936.1000
WSL 1 work properly. But I cannot start ubuntu with WSL2