WSL: WSL takes too long to start after a Windows Update

Just installed Windows 19023, and WSL seems broken. I noticed this issue happening since 19023. After updating Windows, WSL takes too long, aproximately 30 minutes, to actually start.

What’s not working

  • Network drive mount of \\wsl$
  • wsl command in CMD
  • bash command in CMD
  • Windows Terminal, which has bash as default profile
  • Docker in WSL2 profile, i.e Docker not starting and Docker Settings -> Resources -> WSL integration, All distros are unselected (which were previously selected when everything is running fine)

Expected behaviour

WSL should work instantly after updating Windows. So, when entering wsl in CMD. Network drive mounts to \\wsl$ should be mounted and working. bash should start the default distro when entering in CMD. Docker should start and all the distros under Resources -> WSL integration should be selected.

Actual behaviour

  • Running wsl in CMD does nothing, no errors, nothing.
  • Running bash command in CMD just hangs, no erros, nothing.
  • When opening network mount of \\wsl$ this error message shows up image
  • After some minutes (30 or so) everything starts to work as expected.

Things tried so far without success

  • Restart/Shutdown
  • Enable-WindowsOptionalFeature -Online -FeatureName $("VirtualMachinePlatform", "Microsoft-Windows-Subsystem-Linux")

Infos

image image

Update

After a while, everything started to work again as expected. Now, even after a restart, everything works instantly.

Fixed

I realized that my PC was slow overall, when waking from hybernate or restarting. After fiddling around, I found out that the firewall of Kaspersky Internet Security 2019 was causing the lags, and the slow startup of WSL and all the realted service (network mount, docker, etc…)

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 16

Most upvoted comments

Same for me after this update but I resolved the issue with :

CMD + R : optionalfeatures.exe Disable Linux windows sub system Reboot

CMD + R optionalfeatures.exe Enable back Linux sub system it works now

Strange, now everything works 😃