microsoft
WSL2 shut down without warning while I was using it, because Windows Store began to update it
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I'm frustrated when WSL2 shut down itself without any warning while I'm still using it. And that's because Windows Store began to update it.
Describe the solution you'd like A clear and concise description of what you want to happen.
A warning of shutting down before updating it would be greatly appreciated (something like Office update, asking users save their work). I feel like WSL2, as a subsystem, should be treated more as a "system" instead of an app.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
It is convenient for the Store to auto-update some apps that are not running. However, for things that are running, especially WSL2, why does the Store has such a high priority of doing what it wants?
Additional context Add any other context or screenshots about the feature request here.
Agreed - we've given this feedback to the store team and they've said it's something they ware working on. Thanks for the suggestion, will leave this open for tracking.
This just happened with me. I use WSL as a working environment and had it close without any warning.
This happened to me again today on a new machine where I forgot to turn off auto updates. I treat WSL as a working environment, not a toy... sigh
WSL version: 2.1.3.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22635.3140
I decided to move on from WSL and Windows entirely. This issue was the last straw. I had my workflow interrupted way more than I wanted because it would just shutdown without a warning. Running Linux as my main OS is way more reliable at this moment.
Today it happened again. Microsoft Store updated WSL without my consent. And I already turned off auto updates in Store!
Obviously, you didn't.
How condescending. The only thing exposed to users is the toggle in Store's settings. I'd be glad to hear more if you know other measures.
This issue is still present, System Components from Store ignore automatic update settings.
My understanding is that this is now supported by the Windows Store since Sept 2023, as it's being used by Windows Terminal for exactly the same use case.
It probably works for Apps, but not System Components - forced Store update killed my very-much-running WSL just 2 days ago.
I'm having this problem as well. It's happened twice in as many weeks. If it would at least allow me to do a controlled shutdown outside of my working hours, I would let it. But instead it just kills all my applications. This is equivalent to just pulling the battery from a running laptop. How is this acceptable?
Just had this happen; why would this be the default? Just randomly killing your sessions with no warning?
So annoying I workaround this by using tmux when I want to use Windows Terminal so my sessions aren't lost and conhost.exe (legacy console) when I don't use a multiplexer.
EDIT: Somehow misread this so thought it was about Windows Terminal when it's about WSL2. My fault.
This auto-update issue just shut down my WSL while I was in the middle of running a backup, and I have now lost several hours' productivity as a consequence. +1 to any effort that seeks to resolve this, because this is ridiculous and unacceptable.
I don't understand why this issue still exists more than 3 years later. If this is so hard to fix, at least allow us to turn off auto-update entirely until a proper solution is in place.
This is still an issue. Now I've lost unsaved work in VSCode because WSL did an update while it's being actively used.
Ugh, this is a major problem for me - In my enterprise environment, I don't have the ability to shut off automatic updates and this issue is very disruptive to my workflow. How is this acceptable to Microsoft?
It's crazy they were working on it since 2022 and I still just encountered this today. I tried to search how to turn off WSL2 store auto updates and there are no viable solutions.
