Unable to update/uninstall: "Cannot stop tabby"

[crNewton]

UPDATE: I managed to uninstall, but Tabby (V1.0.183) is not showing the cmd terminal (works for powershell/cygwin/git etc).

Describe the problem: Unable to uninstall or update tabby: "tabby cannot be closed". Note that there is something wrong with my tabby, it opens but clink and cmd aren't working: (cygwin, powershell, git those terminals work through tabby) Directly from windows my cmd works fine.

To Reproduce:

• Windows 10 64x 10.0.19043
• Install tabby 1.0.176 (Plugins: none, Frontend: xterm)
• break tabby (as shown in the picture above). I have no idea how this happened :(
• try to update/uninstall tabby

Tried and didn't solve:

• Disable all plugins
• Remove %APPDATA%/tabby
• I checked for running processes/services, but there is no running 'tabby'
• Reboot also didn't resolve the issue

Log from DevTools: -1659429852079.log

[JeanPluzo]

Hi, this also happened to me, but without the "tabby cannot be closed" message. I deleted the %APPDATA%\tabby directory, removed tabby, installed as portable, and it worked. I did have to download the latest version (1.0.183).

[crNewton]

Hi, this also happened to me, but without the "tabby cannot be closed" message. I deleted the %APPDATA%\tabby directory, removed tabby, installed as portable, and it worked. I did have to download the latest version (1.0.183).

This did not work for me.

[crNewton]

I managed to uninstall Tabby by removing the registery key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.

I could then install the latest version (1.0.183), but the problem of not showing my terminals is still there:

This is on a clean install of V1.0.183, before this installation I removed all tabby folders under %APPDATA%, and /ProgramFiles. Running tabby as admin does not solve the issue (still not showing a cmd terminal in tabby)

[crNewton]

UPDATE: When I use "Duplicate as administrator" an a terminal, it works, and doesn't show the empty windows as shown above. clink however shows the following error in the log: ERROR: Unknown verb -- 'inject ', but seems to work.

So not fixed, but it might give further insight in the problem.