search

mskyaxl / wsl-terminal

Terminal emulator for Windows Subsystem for Linux (WSL)
MIT License
3.12k stars 160 forks source link

Immediately crashing #208

Open Waxxx333 opened 1 year ago

Waxxx333 commented 1 year ago

All of a sudden WSL Terminal is immediately crashing when I try to open it.

085astatine commented 1 year ago

I also encountered a similar problem.

wsl-terminal was momentarily giving the following error message when it crashed.

assertion "hRes == 0" failed: file "GetVmId.cpp", line 115, function: HRESULT GetVmId(GUID, const wstring&, int)

GetVmId.cpp exists in Biswa96/wslbridge2. Therefore, it seems that wsl-terminal chash due to an error in wslbridge2.

After downloading the latest version (v0.10) wslbridge2_cygwin_x86_64.zip and unzipping it to wsl-terminal/bin, the problem was solved.

paxsali commented 1 year ago

I have the same error. I can only say it started roughly at the same time the new feature in Windows 10 was introduced, where you can have a "Linux" tree on the left side of the Windows Explorer.

I get ...

On opening you get the internal filesystem via some kind of Samba share presented to the host OS.

Not sure whether this is related to the issue, but the timing was very close.

EDIT: btw, I'm using wsl-terminal-tabbed 0.9.2 on Windows 10.

Also to be clear: I can login to my WSL environments using other terminal emulators, such as Windows Terminal or Hyper etc. fine. Only my previous shortcut that I used for years and haven't changed doesn't work anymore, like above users already mention.

Waxxx333 commented 1 year ago

I also encountered a similar problem.

wsl-terminal was momentarily giving the following error message when it crashed.

assertion "hRes == 0" failed: file "GetVmId.cpp", line 115, function: HRESULT GetVmId(GUID, const wstring&, int)

GetVmId.cpp exists in [Biswa96/wslbridge2[(https://github.com/Biswa96/wslbridge2). Therefore, it seems that wsl-terminal chash due to an error in wslbridge2.

After downloading the latest version (v0.10) wslbridge2_cygwin_x86_64.zip and extacting it to wsl-terminal/bin, the problem was solved.

I was just able to snag that error by attempting to open WSL Terminal from an external drive. Opening it locally crashed too quickly to catch the error. I'm going to do some looking into it now that I have something to work with.

Also to be clear: I can login to my WSL environments using other terminal emulators, such as Windows Terminal or Hyper etc. fine. Only my previous shortcut that I used for years and haven't changed doesn't work anymore, like above users already mention.

Same. I have also tried different releases of WSL Terminal to no avail.

jamesdboone commented 1 year ago

I saw same thing immediately after windows patching. Thanks Waxxx333, that solved my issue as well.

duyanning commented 1 year ago

image