Sorry in advance for the long post, I am very desperate for help and all info I think is helpful has been provided.
Main Issue:
WSL processes are going crazy and I don't know why.
Here is an example image of my
Problem 1:
The ONLY way to "resolve" this that I have found so far is to restart my laptop.
This is NOT a fix. But an annoying workaround. And after restarting, every two or three times when I try to run bash it hangs up on me and this happens again. I have been scouring the internet about these issues and this github post is the closest I have come to my problem, but no solution has been found.
My laptop did not have these issues a couple days ago. I did nothing, installed nothing, updated nothing. My laptop has been having other issues as well (browsers shutting down randomly, very slow terminal response time - this is definitely related to Problem 1, occasionally freezing upon boot - this has turned into Problem 2). This one, however, started happening at the same time as the hanging: Occasionally, upon booting my computer I get this:
I don't know if Problem 2 is related to 1 but my focus is on figuring out 1 for now.
Attempts at solving the problem:
Of course I've tried killing the processes in Task Manager (and with Process Hacker). I've tried running wslconfig.exe /t Ubuntu
but wsl just hangs and nothing happens. When these processes come up, my terminals are slow and basically unusable. Any instance of bash hangs forever. Some IT person ran a Windows checkdisk program thing and it did not help. I have tried using Windows repair features to no avail. I think this might be a hard drive issue but I have no idea.
Does anyone have an idea of what I could do to solve this? Is my computer just lost?
wslconfig /unregister Ubuntu
in an elevated command prompt. Your other issues are likely the reason WSl is behaving the way it is. However, the reason for those behaviors, is not clear based on the information you have provided. Trying to nuke the configuration from orbit, is one way, to see if the problems are connected ("other issues" is not a helpful description of an issue).wslconfig
(/unregister
/t
/l') when Problem 1 is happening.
/unregister' outputsUnregistering...
and does nothing to the processes. I ran it wit cmd as an admin.