You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Windows version: 10.0.17763.475
Distribution: Debian
Problem: Seems like ports will become unavailable over time. First I can't view websites, but can ping. Then I can't ping. And finally Windows will see it as no network access. It all happens over a couple of hours. Rebooting Windows will restart the process.
Explanation:
I wanted to use WSL as a webserver running NGINX instead of using Docker. So I uninstalled Docker and had some leftover Hyper-V instances, and the problem occured. So I thought it was Hyper-V that was causing it and I reset Windows fully. Now I tried it on a fresh install and it's happening again.
The only fix that seems to work for me is to uninstall WSL, so I've done that for now.
Im ready to reinstall it again in case more info needs provided.
The text was updated successfully, but these errors were encountered:
Sounds like #3951, maybe. See if you've got a large number of processes lingering in RamMap (message). Try upgrading to Insider 18890 if you can, and see if that helps.
Current Windows version: 10.0.17763.475
Distribution: Debian
Problem: Seems like ports will become unavailable over time. First I can't view websites, but can ping. Then I can't ping. And finally Windows will see it as no network access. It all happens over a couple of hours. Rebooting Windows will restart the process.
Explanation:
I wanted to use WSL as a webserver running NGINX instead of using Docker. So I uninstalled Docker and had some leftover Hyper-V instances, and the problem occured. So I thought it was Hyper-V that was causing it and I reset Windows fully. Now I tried it on a fresh install and it's happening again.
The only fix that seems to work for me is to uninstall WSL, so I've done that for now.
Im ready to reinstall it again in case more info needs provided.
The text was updated successfully, but these errors were encountered: