Using KiTTY with ConEmu in Windows 10 with Anniversary Update

jdunn0 - Tue 04/10/2016 11:31:41 CEST +0200

There is a program called ConEmu with the ability to open Windows Command Line (cmd.exe), PowerShell, Cygwin and other shells in individual tabs in one Window.
It also lets you have tabs that host the Window of a specific program like PuTTY or KiTTY.
I have used it successfully this way until I installed the Windows 10 Anniversary Update.
After that when I used ConEmu to run "kitty.exe -load SavedSession", this error message appears:
Title: "KiTTY Error"
Message: "Unable to open connection to ssh.example.com
Network error: Windows error code 10106 (and FormatMessage returned 122)"
Note: "SavedSession" and "ssh.example.com" are examples as I don't want to list the actual address of my devices.

This problem does not occur when using PuTTY with ConEmu as when I run "putty.exe -load SavedSession" with ConEmu, PuTTY loads without error and ConEmu shows it in a tab.

One other odd thing is that if I run just "kitty.exe" from ConEmu then KiTTY does appear to show a list of saved sessions where I can then open a session and then ConEmu will put the opened session in a tab.

So the problem seems to only happen when passing command line arguments to KiTTY from ConEmu.
Passing Command Line Arguments to KiTTY.com without using ConEmu does work so I initially thought the problem was with ConEmu but the author of ConEmu in a Github Ticket has said that ConEmu just launches programs and any errors with the programs show be directed to the program author so I'm doing that here.

Note: I'm am using the latest versions of both KiTTY (0.67.1.4) and ConEmu (161002).

Markus - Tue 04/10/2016 14:58:59 CEST +0200

Hi Guys,

i have the same issue like jdunn. But i dont use "-load SavedSession" I select the session from the Kitty Connection Window.
There is no problem with Putty or any other Software with ConEmu. Only Trouble with Kitty.

Best Regards,
Markus

Josch - Mon 10/10/2016 20:41:26 CEST +0200

I have the exactly same problem on my German Windows 10 64bit since the Anniversary upgrade.
Sucks really, because I love to have multiple KiTTY tabs in ConEmu.
PuTTY works somehow.

Dinkonin - Wed 26/10/2016 10:32:16 CEST +0200

Same problem here with Windows 10 Pro Anniversary , Kitty 0.67.3.1 and ConEmu 161022. Putty works fine. Hope this gets resolved.

Cyd - Wed 26/10/2016 14:55:59 CEST +0200

Personally I can't even use conEmu ... even with a simple cmd.exe.
The session shows up, but conEmu does not react to any keystroke ! It does not trap any keyboard event.
As I can't use it I can't reproduce your issue.
Personally I use PuTTY Tab Manager.

Dmitry - Tue 08/11/2016 11:46:39 CET +0100

Similar problems here.
I have Windows 10 version 1607 (OS Build 14393.0) with Anniversary Update installed and Kitty 0.67.3.1p.

1. Earlier everything was working fine, but few weeks ago Kitty become slow:
From time to time it takes 5-10 seconds to start the kitty with command line like "D:\Program Files\kitty\kitty_portable.exe" -folder testfolder", it doesn't matter if I start it from cmd.exe or from Conemu
At the same time if I run it without parameters - it starts fast.
2. Quite often now I started getting message:
Unable to open connection to x.x.x.x
Network error: Windows error code 10106 (and FormatMessage returned 122)
When I start Kitty with parameters from Conemu, like:
"D:\Program Files\kitty\kitty_portable.exe" -folder testfolder -load sessionName -cmd " sudo bash && mc"
I think it started after installation of this Anniversary update, as I started getting these messages just few days ago.
I'm not sure where the problem but probably author of Kitty could give us an idea.

Cyd - Tue 08/11/2016 13:54:23 CET +0100

No idea.
10106 error code is a Windows (Winsock2.h) message to inform that the program was not able to initialize the socket library.
WSAEPROVIDERFAILEDINIT 10106:
Fournisseur de services n'a pas pu s'initialiser. Le fournisseur de services demandé n'a pas pu être chargé ou initialisé. Cette erreur est retournée si DLL soit un fournisseur de services ne peut être chargé (LoadLibrary a échoué) ou le fournisseur WSPStartup ou NSPStartup fonction a échoué.

Just a question: do you have the same behavior with original PuTTY ?

Dmitry - Tue 08/11/2016 15:19:31 CET +0100

Hi Cyd,
Thanks for the prompt answer and for the great modification of Putty.

I've created a new session in Putty Release 0.67 and starting it from Conemu as
> -cur_console:d -cur_console "D:\Program Files\kitty\putty.exe" -load SessionName
- works all the time.

But when I start
> -cur_console:d -cur_console "D:\dimic\Google Drive\Program Files\kitty\kitty_portable.exe" -load SessionName
8 times out of 10 I'm getting the error
Unable to open connection to x.x.x.x
Network error: Windows error code 10106 (and FormatMessage returned 122)
2 times it starts Kitty and connects to the host.

At the same time the only problem which I see when I start Kitty from cmd.exe - some times there is a delay 5-10 seconds before it starts, but I've never had any errors.

Before installation of windows updates - everything was working well, the problems with delays on start showed up 1-2 weeks ago and the error showed up few days ago. I've uninstalled all updates which I was able to uninstall, but it seems that I can't uninstall the Anniversary update (don't have such option at least)

Do you think it is something with Conemu or with Kitty which is incompatible with latest version of Windows 10?

Cyd - Tue 08/11/2016 15:27:22 CET +0100

As I wrote before, I was completely unable to use conEmu on my Windows 10.
The conEmu I've installed on my PC did not trap any keyboard event !!!

Dmitry - Tue 08/11/2016 18:41:22 CET +0100

Yeah, skipped that :(
Don't think that it will help you, but I'm using Conemu 161022 [64]{stable} on my Windows 10.


However the issue with delay on start is reproducible from cmd.exe.

Cyd - Tue 08/11/2016 20:59:02 CET +0100

One more think
Do you have the same delay in registry mode ?

Dmitry - Tue 08/11/2016 21:07:09 CET +0100

Interesting suggestion, I'll check this out tomorrow and let you know. Thanks!

Dmitry - Wed 09/11/2016 10:24:39 CET +0100

Hi, I've tested out with registry - kitty works with registry without problems, I can load saved sessions without any errors.

However I have the same error as before (Network error: Windows error code 10106 (and FormatMessage returned 122) ) when I'm using sessions which are saved in files. The error occurs very often but not always.

I've tried to:
remove kitty.ini
remove all saved ssh_keys
remove all sessions from ./sessions
remove "default settings" session and create a new session
disable antivirus

nothing helped :(

Cyd - Mon 14/11/2016 21:30:19 CET +0100

Ok
The problem is related to the "Windows Search Service": https://social.technet.microsoft.com/Forums/fr-FR/1abde9b9-9e6f-4241-9fd5-0175871f6c63/slow-folder-creation-deletion-with-anniversary-update-and-windows-server-2012?forum=win10itprosetup
Try to disable it, and everything will go faster.

Dmitry - Tue 15/11/2016 09:57:55 CET +0100

Hi,
I'm afraid that didn't solve the issue with delay on start, I've disabled Windows Search service, but from time to time it takes 5-10 seconds to start the app.

And here is a cross link to the issue with error code 10106 which was posted to Conemu's support forum: https://github.com/Maximus5/ConEmu/issues/858 .

I'll probably start using use kitty with sessions, stored in registry on Windows 10 :(
Thanks.

Dmitry - Tue 15/11/2016 16:50:01 CET +0100

Exported sessions into registry, so far so good, I can use ConEmu with Kitty on Windows 10 Anniversary update. No errors.
Unfortunately I can't sync sessions between multiple computers now, but at least the main functionality works well.

Cyd - Wed 16/11/2016 22:06:04 CET +0100

Finally found something.
Zmodem patch is not compatible with ConEmu.
Please find a version without Zmodem here: http://www.9bis.net/kitty/data/beta/kitty_nozmodem.exe

Josch - Thu 17/11/2016 21:30:51 CET +0100

Thank you very much! It works great again on Windows 10 with ConEmu and Sessions stored in files with the kitty_nozmodem.exe

Would be great if you could provide that version also for future releases, if that incompatibility can't be resolved.

Dmitry - Thu 17/11/2016 21:44:48 CET +0100

Thanks a lot! Works great again!

Markus - Tue 22/11/2016 09:37:50 CET +0100

Hi,

0.67.3.2 is also Working for me with Conemu. Thank you!

Best Regards,
Markus

TOm - Mon 18/12/2017 02:01:35 CET +0100

Hi,

The nozmodem link is now broken. Would it be possible to re-add it or add a disable zmodem startup switch?

I'm not sure if this is the same problem though...

Kitty sessions jump out of conemu immediately, into their own window (which sort of defeats the purpose of conemu).

I'm left with a conemu tab that says "Root process was alive for less than 10 sec, ExitCode=0"

Thanks,

Tom

Cyd - Mon 18/12/2017 08:55:37 CET +0100

Try the -nozmodem option

Tom - Fri 12/01/2018 07:27:10 CET +0100

Thanks Cyd, that works, but the conemu issue persists unfortunately.

I even tried the -putty option and it still jumps into its own window.

I can attach the opened window to a conemu tab after it's open, so it seems to be an issue on first load.

Putty itself opens fine in conemu.

Cheers,

Tom

Tom - Fri 19/01/2018 00:33:14 CET +0100

Hi Cyd,

Mea culpa - I found the problem. I installed kitty via chocolatey and it creates a dummy exe that then calls kitty.

I tried it with a direct call to the real exe and the attach worked perfectly.

Hope this helps anyone with similar issues.

Tom

Answer

The forum is actually closed