Unexpected WSL error
The solution is at the bottom, hope it works for you
On this beautiful day, I turned on my computer as usual and started working. However, the docker client that was set to start automatically did not start as usual. Instead, a long text error window popped up. At first, I didn't pay much attention to it and just closed it. But then, the familiar docker interface also closed automatically. I smiled slightly and thought, "Oh my, how can such a stable docker have this kind of situation? Impossible! Absolutely impossible! I must take a screenshot to commemorate this!"
I restarted docker several times and even restarted Win11. By now, I was completely sure that restarting was not the solution. I quietly greeted Microsoft and tried to appear calm, afraid that my colleagues would notice my anxiety. But in reality, I was panicking because I had six months' worth of data in docker!
Oh almighty Baidu, here we meet again. How should I deal with this? Restarting WSL, right? Well, that command didn't work. It might work for those who have used proxies or accelerators, but not for me.
netsh winsock reset
You're just WSL, aren't you? It's been an hour, do you know how I spent this hour? WSL, you're going to be messed up. Even if Kingsoft Guardian comes, it won't be able to save you. I'm telling you!!!
Win+R regedit to find the registry
Find WSLService
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WSLService
Right-click -> Delete -> Restart the machine
At least this method worked for me. It seems to be caused by a Windows update. Fortunately, now I can happily play with my six months' worth of data again.
For more exciting content, visit my website xiao4.wang