WSL2 - "The Windows Subsystem for Linux instance has terminated." #5110

Some1OnLine · 2020-04-20T05:22:42Z

Your Windows build number: (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.19041.207]
What you're doing and what's happening: (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)
I moved/exported/Imported my WSL2 Debian Distro from an old Computer (AMD A10) to a newer AMD FX8350 based Computer that has a lot more memory, using WSL --import. The export and import was successful but now the distro fails to start with the message "The Windows Subsystem for Linux instance has terminated."
One thing I noticed is that if I convert the Distro from WSL v2 to WSL v1 the distro starts and im able to get into most of it. But a lot of things in the distro dont work. As soon as I convert it back to WSL v2 it fails again. Both the old and new computer are the same build of Windows 10
What's wrong / what should be happening instead:
The distro should start.
Strace of the failing command, if applicable: (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here).
For WSL launch issues, please collect detailed logs.

The text was updated successfully, but these errors were encountered:

martinfojtik · 2020-04-29T11:45:07Z

I have the same problem. My Ubuntu distro stopped working, If I convert it to WSL1 it starts working, but when I move it back to wls 2, I can't start it again.

EDIT: I founded what caused the problem in my distro. I have mounted folder which require "sshfs" and is in a VPN network. I couldn't start Ubuntu because my VPN wasn't started.

ludzzz · 2020-05-05T06:40:17Z

@martinfojtik Thank you so much, Got the exact same issue, but I didn't thoughts about the mounted folder through VPN.
It's kinda obvious when you know it.

Welquer · 2020-05-12T00:19:17Z

wsl command was failing for me, but after ejecting my external HD it worked fine and WSL has been started.

kreczko · 2020-05-19T09:06:48Z

Similarly here.

The Windows Subsystem for Linux instance has terminated.
[process exited with code 4294967295]

I think it might be due to changes to /etc/fstab I've done - is there a way to edit the file without starting WSL? Or maybe it is because of the docker service.

Log capture does not provide any additional information:

logman.exe create trace lxcore_kernel -p "{0CD1C309-0878-4515-83DB-749843B3F5C9}" -mode 0x00000008 -ft 10:00 -o .\lxcore_kernel.etl -ets
logman.exe create trace lxcore_user -p "{D90B9468-67F0-5B3B-42CC-82AC81FFD960}" -ft 1:00 -rt -o .\lxcore_user.etl -ets
logman.exe create trace lxcore_service -p "{B99CDB5A-039C-5046-E672-1A0DE0A40211}" -ft 1:00 -rt -o .\lxcore_service.etl -ets

→ Event Viewer info is barren.

wisepotato · 2020-05-25T20:45:07Z

same here, i think its my fstab, but no way to edit it without starting wsl.. bit of a catch 22..

kreczko · 2020-05-26T08:13:34Z

same here, i think its my fstab, but no way to edit it without starting wsl.. bit of a catch 22..

Had to convert back to WSL 1, edit the fstab, then convert again to WSL 2.

boblitex · 2020-05-28T01:47:54Z

same here, i think its my fstab, but no way to edit it without starting wsl.. bit of a catch 22..

Had to convert back to WSL 1, edit the fstab, then convert again to WSL 2.

how did you manage to do this, having the same issue here. WSL 2 sounded very promising with the performance dreams but I don't know if all this stress is worth it

wisepotato · 2020-05-28T07:56:57Z

same here, i think its my fstab, but no way to edit it without starting wsl.. bit of a catch 22..

Had to convert back to WSL 1, edit the fstab, then convert again to WSL 2.

oh god.

wisepotato · 2020-05-28T08:05:55Z

same here, i think its my fstab, but no way to edit it without starting wsl.. bit of a catch 22..

Had to convert back to WSL 1, edit the fstab, then convert again to WSL 2.

how did you manage to do this, having the same issue here. WSL 2 sounded very promising with the performance dreams but I don't know if all this stress is worth it

i mean you are running an insider preview, this is bound to happen. Wait until actual release and it'll probably be buttery smooth

kreczko · 2020-05-28T08:07:15Z

how did you manage to do this, having the same issue here.

wsl --set-version Ubuntu-18.04 1
# edit fstab
wsl --set-version Ubuntu-18.04 2

where Ubuntu-18.04 is the distribution I use.

Fun fact: all the mounts in the fstab work if I execute them after the machine is up (sudo mount ...) → feels like a startup order problem.

Had to convert back to WSL 1, edit the fstab, then convert again to WSL 2.

oh god.

Yeah, debugging functionality in WSL still needs to improve. But at least I can FUSE mount now in WSL 2 which completes the last of my requirements for development on WSL.

liudonghua123 · 2020-06-08T02:04:14Z

After I Updated the WSL 2 Linux kernel, the problem fixed.

Notice, Need to download and install the latest package on https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel.

nikhildaga · 2020-06-10T23:17:53Z

Still facing this issue

gerardojbaez · 2020-06-17T18:06:54Z

This is becoming really annoying. 😢 I get this error every time I turn on the PC and open the WSL console (Ubuntu-18.04).

chuyangliu · 2020-06-17T18:26:21Z

Facing the same issue when using WSL 2 with Docker Desktop

ttutko · 2020-06-17T19:15:31Z

I've seen several issues that seem similar to this and to me the most frustrating things are:
1.) There doesn't appear to be a good way to see anything that is happening to even begin to troubleshoot this. I know we can collect logs but I haven't seen a good way to view anything useful from them without having the source code.
2.) The only responses I have seen from Microsoft were asking to submit logs but no acknowledgement of any issues or replies given after those logs were submitted to help anyone get past the issue.

I've now had this happen to me twice where I had a great working wsl setup then all of a sudden it just stopped working with this same error. I can export it and re-import it and the same thing happens (this leads me to believe it's some sort of state in the file system but I have no idea how to track down what saved state to modify in the exported tar file to get it to work after re-import). The second time I should have known better than to mess with things but I saw there was a new kernel update, I installed it, then terminated the distro to get the new kernel version to take affect and it never started up again.

Is there any way to see something like dmesg type output from when an instance (distribution) tries to transition from "Stopped" to Running?

MJLHThomassen-Sorama · 2020-06-18T13:25:15Z

Facing the same issue when using WSL 2 with Docker Desktop

Same here

hsakkout · 2020-06-19T03:19:28Z

I can't install the WSL kernel update either, as the installer is assuming I don't have WSL.

brunswick42 · 2020-06-22T03:42:58Z

2.) The only responses I have seen from Microsoft were asking to submit logs but no acknowledgement of any issues or replies given after those logs were submitted to help anyone get past the issue.

I've now had this happen to me twice where I had a great working wsl setup then all of a sudden it just stopped working with this same error.

This happened to me twice as well, and I'm tired of starting over. I want to WSL2, but I can't use it if it breaks and I lose everything each week. I could even live with this for a while if there was a way to recover from the failure. But as it stands it is not clear if anyone is looking into it, or if there is anything we can do to help solve the problem.

ttutko · 2020-06-22T21:44:33Z

To add some more information to the madness that I am experiencing as well as some of you have also been experiencing:

I exported my broken wsl2 distro then imported it again under a different name to try some things out. Of course, the copy did not work. I then tried to convert it to wsl1 which hung. After a reboot, my original wsl2 distro was still broken but I was able to convert the copy to version 1. After conversion to version 1, the copy was able to start. I removed an entry from /etc/fstab as some people seemed to indicate issues with mounting drives fixed their problem. I then tried converting to version 2. After conversion to version 2, it wouldn't start and was broken again. I decided to go convert back to version 1 and just live with that for now until hopefully we get some answers so I kicked off the conversion to version 1 (of the copy, the original distro was still left alone). While the copy was converting back to version 1, I clicked to open a new tab in windows terminal with the intention of opening powershell core. I accidentally clicked on my original broken wsl2 distro though and IT STARTED. I'm so thoroughly confused :(

brunswick42 · 2020-06-22T22:20:45Z

I have no idea what happened, but yesterday on a whim, I ran wsl in PowerShell, which seemed to start the instance, and I've been able to use it ever since.

gerardojbaez · 2020-06-23T16:18:55Z

Windows 10 Home Insider Preview. Build 20150.rs_prerelease.200612-1734

Today, after turning on my PC and opening Windows Terminal, the Ubuntu console got stuck on an empty screen (nothing showed up). I closed it and opened an instance of PowerShell, I executed wsl, and got "An error occurred mounting one of your file systems. Please run 'dmesg' for more details.". I ran dmesg and this is the result:

This is a clean boot, no program was opened before opening the Windows Terminal, so plenty of memory were available. No VPN, no Docker for Windows (installed only inside WSL2).

This is becoming really annoying. No word from Windows or the WSL team, not even a workaround or an explanation of the issue/cause.

The only solution, for now, is to restart the PC until WSL2 is able to start.

At this point, I'm considering switching to a dual-boot with Ubuntu and use that as my development machine while this issue is solved.

I post this on this thread because I feel it is a related issue.

enthusiast · 2020-06-25T04:44:59Z

I had the same problem after switching to WSL2. I launched the bash on Ubuntu shortcut and there was still some setup to be done. After it did that I am able to launch it from the terminal again. Yay!

FabienNeibaf · 2020-07-02T12:23:02Z

I had the same issue. And I tried to run again the command wsl --set-default-version 2 on PowerShell and hourra it works again. I guess you need to run this command each time you restart your PC to choose the version of wsl you want to run.

kzlsakal · 2020-07-09T14:50:38Z

I have the same issue after every clean boot. Using Ubuntu 20.04 with WSL2 on W10 Pro 20152.rs_prerelease.200617-1502.

I run Ubuntu after waiting for the startup processes to finish what they are doing. So no conflict. The terminal gives the specified error:

The next behavior depends on how much I wait after getting this error. If I wait long enough and open a PowerShell as admin, then run wsl, it starts Ubuntu normally.

In other cases, it waits for 30-45 seconds after running wsl and gives the following error:

The virtual machine or container was forcefully exited

Then I do wsl --shutdown and if I haven't waited long enough, it would tell me that the program is being used by another process. If I tried again after 1 minute or so, it executes the command. After that, if I try running wsl again, it gives me the same error:

The virtual machine or container was forcefully exited

If I restart Windows after that, I can run Ubuntu just by clicking the Ubuntu button or opening a Linux shell anywhere.

I will try to add the actual screenshots of the errors as this issue reproduces itself circumstantially.

debosmit-git · 2020-07-12T18:58:26Z

exiting docker, opening a new wsl window and restarting docker gets me out of this loop

amaria · 2020-07-24T14:47:11Z

I've found that if I wait a few minutes and try opening the terminal again (maybe a couple more times), it works.

softveda · 2020-08-06T10:39:24Z

I am having the same issue suddenly after restarting my machine. Trace files attached.
Microsoft Windows [Version 10.0.19041.388]
Ubuntu-20.04
lxcore_trace.zip

aMozejko1 · 2020-08-07T04:32:14Z

same issue for me. Restarted last night after applying updates and cannot launch a previously working distro.

creating a new distro works as expected.

docker running or not running makes no difference

Microsoft Windows [Version 10.0.19041.388]

edte · 2022-07-29T10:14:56Z

sometimes wsl will stuck, and after some minutes, when i try to enter new terminal, it will show The Windows Subsystem for Linux instance has terminated.

news-ttt · 2022-08-01T01:28:58Z

sometimes wsl will stuck, and after some minutes, when i try to enter new terminal, it will show The Windows Subsystem for Linux instance has terminated.

The default one you set is that. Is it convenient to tell

news-ttt · 2022-08-01T02:13:16Z

sometimes wsl will stuck, and after some minutes, when i try to enter new terminal, it will show The Windows Subsystem for Linux instance has terminated.

Is it convenient to provide the list you obtained

edte · 2022-08-01T02:46:08Z

news-ttt · 2022-08-01T02:48:18Z

Is the version too high，You can try downloading a lower version as the default

edte · 2022-08-01T03:06:53Z

i download it from microsoft store😰

dcharlespyle · 2022-08-01T03:40:51Z

I usually wait for Ubuntu releases until it is at least xx.04.1 or higher. Earlier releases tend to be a bit buggy. At least that has been my experience over the years. May need to add some libraries, too. It's pretty much a bare-bones install image on the Store. I'm on 20.04.4 LTS and see none of the termination errors I saw before. I'm also using WSL Preview, also from the store, and I don't use Docker. These kinds of termination errors seem to occur more frequently when using Docker than without.

news-ttt · 2022-08-01T03:47:11Z

My version is also 20.04.4

dcharlespyle · 2022-08-01T03:58:11Z

My version is also 20.04.4

Seeing the same crashes? Are you using Docker?

On my WSL installation, I use a script on the Linux side to start a few services. I also keep a couple scripts on the Windows side to terminate WSL, restart the service associated with WSL, and then call the script on the Linux side to start services again. I don't use it often but perhaps it might help you. Following is the Windows side script that terminates and restarts WSL.

@echo off

REM - Shutdown and terminate Linux WSL VM.

echo Shutting down running WSL Linux instance...

wsl --shutdown

echo WSL Linux session terminated...

TIMEOUT 5

REM - Restart LxssManager Service

echo Restarting LxssManager Service...

powershell -Command "Restart-Service -Name LxssManager -PassThru -Force"

TIMEOUT 10

REM - Start Linux WSL VM and services.

"C:\Users\Public\Public Virtual Machines\Scripts\StartWSL.cmd"

REM - Uncomment below line to troubleshoot.
REM - pause

exit 0

Following is the script that starts WSL (it has elements for use with both a third-party XServer and Windows' standard.

@echo off

REM - Start XServer.
REM - "C:\Program Files\VcXsrv\vcxsrv.exe" +bs -ac -multiwindow -multimonitors -wgl -swrastwgl

REM - Allow XServer time to start.
REM - timeout /t 10 /nobreak >NUL

REM - Update WSL Kernel and components.
REM - C:\Windows\System32\wsl.exe --update

REM - Allow update process to close.
REM - timeout /t 5 /nobreak >NUL

echo Starting WSL Linux...

:RETRY

REM - Run some WSL Services.

REM - C:\Windows\System32\wslg.exe -d Ubuntu -- /usr/bin/start-wsl-services

C:\Windows\System32\wslg.exe -d Ubuntu -- /usr/bin/start-wsl-services

REM - IF %ERRORLEVEL% NEQ 0 (GOTO RETRY)

REM - Allow time to see all results.
timeout /t 2 /nobreak >NUL

REM - Uncomment below line for troubleshooting.
REM - pause

exit 0

Following is the script on the Linux side.

#!/bin/bash

# Check for and run System-wide DBus service.
SERVICE="dbus-daemon"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/dbus start
    pgrep -a "$SERVICE"
fi

# Check for and run CUPS Printing Service.
SERVICE="cupsd"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/cups start
    pgrep -a "$SERVICE"
fi

# Check for and start Freshclam CLAMAV Update service.
SERVICE="freshclam"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/clamav-freshclam start
    pgrep -a "$SERVICE"
fi

# Check for and start SANED Scanner service.
SERVICE="saned"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/saned start
    pgrep -a "$SERVICE"
fi

# Check for and start Preload service.
SERVICE="preload"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/preload start
    pgrep -a "$SERVICE"
fi

# Start LibreOffice and terminate for faster loading.
/usr/bin/libreoffice --terminate_after_init

# Check for error, make sure all functions called and run, and pass the result on to calling process.
if [[ $? -ne 0 ]] ; then
    exit 1
else
    exit 0
fi

edte · 2022-08-01T04:06:21Z

I am indeed using docker desktop

dcharlespyle · 2022-08-01T04:15:40Z

Make sure that Docker Desktop is fully updated as well as WSL. Also check to make sure that the default is set to WSL2. Other than that, not sure what else can help. As I said, I don't use Docker for my configuration.

Dacesilian · 2022-08-01T17:48:06Z

I've set all mentioned here (default WSL2, swap, memory) and Ubuntu crashed again. Yes, I'm using Docker, also fully updated. I don't know why Microsoft and Docker don't cooperate and work on this issue. It must be a problem for a huge amount of people :(

dcharlespyle · 2022-08-02T16:39:32Z

I haven't seen that "WARNING: Waiting for service. 'LxssManager (LxssManager)'..." error for a very long time. And, fortunately, that error has nothing to do with Docker. Whenever you see that error, use Windows Task Manager to find the PID of the service.

Use Resource Monitor to find the same process PID.

End Process Tree for the process PID. Then start the LxssManager service and run WSL again.

rvanlaak · 2022-08-04T09:30:19Z

https://github.com/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-5.15.57.1

The first 5.15 kernel series was released Aug 2nd, and running wsl --update nicely updated me to that version.

Regarding the changelog:

Fix 9p filesystem regressions since the last v5.10 WSL2 kernel

Would that be related to our long awaited fix?

Also, did anyone try the PATH workaround in the discussion? #7869

Toastzam · 2022-08-18T13:04:54Z

shibal wsl

HenTorgeman · 2022-08-22T09:06:21Z

Hi! I had the same issue, the below steps solved it for me 👍

pause docker-engine
close all apps accessing Linux files (e.g. vscode)
Power shall ( to check the distro name): $ wsl -l -v
Power shall ( to start the WSL distributuion again): $ wsl -d Ubuntu-18.04

johny-mnemonic · 2022-09-21T14:04:14Z

Not sure I am having the same issue, but I am getting this same error from vscode and also when I try to execute any command in new shell, i.e.:

wsl -d Ubuntu-20.04 -e uptime
The Windows Subsystem for Linux instance has terminated.

But in the terminal where I started wsl I am logged in and everything seems to work.

COMPUTER :: c/Users/USER » uptime
 16:02:24 up 12:11,  2 users,  load average: 0.02, 0.07, 0.02

Also I have xrdp running in my wsl distro and I am connected there (KDE UI) and everything seems to work normally.
When I try to list running wsl distros it is also reported as running:

C:\WINDOWS\System32\wsl.exe -l --running
Windows Subsystem for Linux Distributions:
Ubuntu-20.04 (Default)

So I am really confused what is going on 🤯

zeeshananjumjunaidi · 2022-09-21T19:27:43Z

I ran
wsl --shutdown
then
wsl
and it started working again.

johny-mnemonic · 2022-09-21T20:16:50Z

I ran wsl --shutdown then wsl and it started working again.

Well, "fixing" computer issues by restarting it is always an option, but when you have a lot of open work it is a nuisance 🤷‍♂️
I know I can kill that running OS and start it again, but it means I will loose my open work and it also takes time as I am using genie to have fully working systemd in my Ubuntu...

wenjoy · 2022-10-01T04:07:23Z

I ran wsl --shutdown then wsl and it started working again.

This is the way.

Dacesilian · 2022-10-01T04:58:47Z

But symbolic link share is not restored, so all applications are freezed and you must reboot whole computer.

I think this problem is somehow connected with filesystem activity or files count... It freezes more often when doing git commit, copying files etc.

johny-mnemonic · 2022-10-03T15:45:19Z

I ran wsl --shutdown then wsl and it started working again.

This is the way.

Do you realize, that this is like telling someone whose wifi driver is sometimes starting to drop packets to fix the issue by rebooting his laptop? 🙄

dcharlespyle · 2022-10-03T16:08:56Z

I ran wsl --shutdown then wsl and it started working again.

This is the way.

Do you realize, that this is like telling someone whose wifi driver is sometimes starting to drop packets to fix the issue by rebooting his laptop? 🙄

Well, truth be told, if this is Dell hardware a reboot actually can be a correct answer. For some Dell hardware I supported over the years, one had first to turn off the device, unplug the device from power for 15 seconds, and then plug it back in and boot up the computer again. Had much experience with Dell hardware in a College computer Math Lab that had issues with dropping packets until that was done. All of the computers would do it. Had to do this about every couple of weeks or so with the 3Com hubs and switches that were in use at the time. And it was similar with the Wifi hardware. I don't what it was about the Dells at that time, but it was a regular occurrence. They all were Optiplex models, but I no longer recall the specific model numbers. Some Dell Inspirons would do the same with their Wifi hardware. It did not matter what settings were used. Even worse, some Dell models were certified for Ubuntu, but the Wifi hardware always had issues with dropping packets until rebooted (in which case it would be fine for a few days before problems would start up again), and we never could get hibernation to work properly on those systems supposedly certified for Ubuntu Linux!

Long rant about the way things were, but I also have found that when there are troubles with WSL, shutting it down and starting it up again would fix the troubles with interoperability. After some updates, the problem came back with a vengeance, and I found I had to run the command several times a day. So, I just wrote a couple of scripts so that when it occurs, I just double click a shortcut to the main script, click to allow elevation, and let it shutdown WSL, restart the service, and then restart WSL and run a few services from the Linux side (such as CUPS, saned, and systemwide DBus). This is the script I now am using (until changes to WSL require modification):

@echo off

REM - Shutdown and terminate Linux WSL VM.

echo Shutting down running WSL Linux instance...

wsl --shutdown

echo WSL Linux session terminated...

TIMEOUT 5

REM - Restart LxssManager Service.

echo Restarting LxssManager Service...

powershell -Command "Restart-Service -Name LxssManager -PassThru -Force"

TIMEOUT 10

REM - Start Linux WSL VM and services.

"C:\Users\Public\Public Virtual Machines\Scripts\StartWSL.cmd"

REM - Uncomment below line to troubleshoot.
REM - pause

exit 0

The Start WSL script is as follows (the script can be adjusted for either use of WSLg or the third party XServer I was using):

@echo off

REM - Start XServer.
REM - "C:\Program Files\VcXsrv\vcxsrv.exe" +bs -ac -multiwindow -multimonitors -wgl -swrastwgl

REM - Allow XServer time to start.
REM - timeout /t 10 /nobreak >NUL

REM - Update WSL Kernel and components.
REM - C:\Windows\System32\wsl.exe --update

REM - Allow update process to close.
REM - timeout /t 5 /nobreak >NUL

echo Starting WSL Linux...

:RETRY

REM - Run some WSL Services.

REM - C:\Windows\System32\wslg.exe -d Ubuntu -- /usr/bin/start-wsl-services

C:\Windows\System32\wslg.exe -d Ubuntu -- /usr/bin/start-wsl-services

REM - IF %ERRORLEVEL% NEQ 0 (GOTO RETRY)

REM - Allow time to see all results.
timeout /t 2 /nobreak >NUL

REM - Uncomment below line for troubleshooting.
REM - pause

exit 0

And on the Linux side of WSL, I use the following script (with several available options) named start-wsl-services in /usr/bin/:

#!/bin/bash

# Check for and run System-wide DBus service.
SERVICE="dbus-daemon"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/dbus start
    pgrep -a "$SERVICE"
fi

# Check for and run CUPS Printing Service.
SERVICE="cupsd"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/cups start
    pgrep -a "$SERVICE"
fi

# Check for and start Freshclam CLAMAV Update service.
SERVICE="freshclam"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/clamav-freshclam start
    pgrep -a "$SERVICE"
fi

# Check for and start SANED Scanner service.
SERVICE="saned"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/saned start
    pgrep -a "$SERVICE"
fi

# Check for and start Preload service.
SERVICE="preload"
if pgrep -x "$SERVICE" >/dev/null
then
    pgrep -a "$SERVICE"
else
    sudo /etc/init.d/preload start
    pgrep -a "$SERVICE"
fi

# Start LibreOffice and terminate for faster loading (uncomment to use).
# /usr/bin/libreoffice --terminate_after_init

# Check for error, make sure all functions called and run, and pass the result on to calling process.
if [[ $? -ne 0 ]] ; then
    exit 1
else
    exit 0
fi

imPankajShaw · 2023-01-04T08:58:11Z

Quick solution:
(1):

Check the state of the wsl instance (wsl --list --verbose)
if your wsl instance state is 'running' then terminate (wsl -t DISTRO_NAME)
then shutdown the instance (wsl --shutdown)
now the instance should work fine.

(2):

Check the state of the wsl instance (wsl --list --verbose)
if your wsl instance state is 'stopped' then shutdown the instance (wsl --shutdown)
restart the instance, it should work fine.

ankurga · 2023-06-26T07:41:21Z

For most of the issues. I just apply what we call a "Microsoft" solution.

Restart of WSL.

Run powershell as admin >> wsl --shutdown >> Start "Ubuntu on Windows" again from the start button.

Close and open VScode again and it's solved.

hoggatt · 2023-09-22T03:34:24Z

For most of the issues. I just apply what we call a "Microsoft" solution.

Restart of WSL.

Run powershell as admin >> wsl --shutdown >> Start "Ubuntu on Windows" again from the start button.

Close and open VScode again and it's solved.

As I like to say: Microsoft problems require Microsoft solutions.

sollyucko · 2024-03-06T20:37:58Z

Quitting Docker Desktop fixed it for me.

Some1OnLine changed the title ~~WSL v2 - "The Windows Subsystem for Linux instance has terminated."~~ WSL2 - "The Windows Subsystem for Linux instance has terminated." Apr 20, 2020

patricknazar mentioned this issue Aug 5, 2020

"first boot of the day" takes wsl a long time to start #5680

Closed

github-actions bot mentioned this issue Jan 24, 2024

WSL2. Can no longer find 'C:\Program Files\WSL\system.vhd' #11069

Closed

2 tasks

github-actions bot mentioned this issue Mar 22, 2024

ERROR: CreateProcessEntryCommon - unable to login to WSL after import #11343

Closed

2 tasks

github-actions bot mentioned this issue Jan 22, 2025

WSL backup and restore not working #12491

Closed

WSL2 - "The Windows Subsystem for Linux instance has terminated." #5110

WSL2 - "The Windows Subsystem for Linux instance has terminated." #5110

Comments

Some1OnLine commented Apr 20, 2020 • edited Loading

martinfojtik commented Apr 29, 2020 • edited Loading

ludzzz commented May 5, 2020

Welquer commented May 12, 2020 • edited Loading

kreczko commented May 19, 2020 • edited Loading

wisepotato commented May 25, 2020

kreczko commented May 26, 2020

boblitex commented May 28, 2020

wisepotato commented May 28, 2020

wisepotato commented May 28, 2020

kreczko commented May 28, 2020

liudonghua123 commented Jun 8, 2020

nikhildaga commented Jun 10, 2020

gerardojbaez commented Jun 17, 2020

chuyangliu commented Jun 17, 2020

ttutko commented Jun 17, 2020

MJLHThomassen-Sorama commented Jun 18, 2020

hsakkout commented Jun 19, 2020

brunswick42 commented Jun 22, 2020

ttutko commented Jun 22, 2020

brunswick42 commented Jun 22, 2020

gerardojbaez commented Jun 23, 2020 • edited Loading

enthusiast commented Jun 25, 2020

FabienNeibaf commented Jul 2, 2020

kzlsakal commented Jul 9, 2020

debosmit-git commented Jul 12, 2020

amaria commented Jul 24, 2020

softveda commented Aug 6, 2020

aMozejko1 commented Aug 7, 2020 • edited Loading

edte commented Jul 29, 2022

news-ttt commented Aug 1, 2022

news-ttt commented Aug 1, 2022

edte commented Aug 1, 2022

news-ttt commented Aug 1, 2022

edte commented Aug 1, 2022

dcharlespyle commented Aug 1, 2022 • edited Loading

news-ttt commented Aug 1, 2022

dcharlespyle commented Aug 1, 2022

edte commented Aug 1, 2022

dcharlespyle commented Aug 1, 2022

Dacesilian commented Aug 1, 2022 • edited Loading

dcharlespyle commented Aug 2, 2022

rvanlaak commented Aug 4, 2022 • edited Loading

Toastzam commented Aug 18, 2022

HenTorgeman commented Aug 22, 2022

johny-mnemonic commented Sep 21, 2022

zeeshananjumjunaidi commented Sep 21, 2022

johny-mnemonic commented Sep 21, 2022

wenjoy commented Oct 1, 2022

Dacesilian commented Oct 1, 2022

johny-mnemonic commented Oct 3, 2022

dcharlespyle commented Oct 3, 2022

imPankajShaw commented Jan 4, 2023

ankurga commented Jun 26, 2023 • edited Loading

hoggatt commented Sep 22, 2023

sollyucko commented Mar 6, 2024

Some1OnLine commented Apr 20, 2020 •

edited

Loading

martinfojtik commented Apr 29, 2020 •

edited

Loading

Welquer commented May 12, 2020 •

edited

Loading

kreczko commented May 19, 2020 •

edited

Loading

gerardojbaez commented Jun 23, 2020 •

edited

Loading

aMozejko1 commented Aug 7, 2020 •

edited

Loading

dcharlespyle commented Aug 1, 2022 •

edited

Loading

Dacesilian commented Aug 1, 2022 •

edited

Loading

rvanlaak commented Aug 4, 2022 •

edited

Loading

ankurga commented Jun 26, 2023 •

edited

Loading