WSL 2 messes the power options on windows

whenever I try installing Docker, it shows an error related to WSL 2, and when I use PowerShell commands to install WSL 2, docker then starts working fine, but windows starts acting up, it stops wanting to shutdown (unless I use “shutdown /p” in cmd), and the option to hibernate stops working, the pc simply either locks the screen or signs out, but refuses to power down, I’ve undid this a couple times by removing WSL 2 and docker entirely and that fixes things, but then when I try again, nothing changes, same result every time.

If you have come across this issue at some point, I’d appreciate it if you share with me how you got around it.

Thank you very much.

Does it happen also when you have only WSL2 installed but not Docker Desktop?

I stand corrected, it wasn’t about docker, simply running “wsl -install” in PoweShell and finishing the process created the issue again.
Still, if you have an idea about how to solve it I would appreciate that.

I would tell you if I knew a way to solve it, but I don’t know. If you wrote the issue happened only with Docker, I would have shared the github repo of Docker Desktop to report the issue. If WSL itself causes it, you could try Microsoft’s forum.

https://answers.microsoft.com/

My guess is that it is either a hardware issue which is triggered by WSL or just a WSL bug. Hopefully not a hardware issue. Since WSL2 has a special kernel and some integration with Windows, I guess they could do something that breaks the Windows host.

1 Like

Furthermore, you can check the GIthub Issues for the WSL repo:

If the issue was not already raised, you could open an issue in the repo.

1 Like

@rimelek what you said made me think, why would I even need wsl 2 if there’s the option that I can untick and use Hyper-V instead, but sure enough, as soon as docker finished installing the same issue happened, I’m beginning to think setting up any sort of virtual environment is causing this problem.
.
I’ll try a fresh installation of windows and see how it goes, since this problem is so specific and no one encountered it before, it might be a deep seated problem in my windows that’s interacting with virtual environments abnormally causing this issue. Thank you so much for trying to help.