When kitty.exe is first downloaded and used, the SshHostKeys subdirectory is created as soon as it is needed.
However, for some reason, if you try to connect to a server before that, the configured private key is not used.
This affects us, because we roll out a premade package with kitty plus the configuration to client machines.
We'll just add an empty SshHostKeys subdirectory to the package, but I thought I'd create an issue anyway, so others with the same problem can find it.
When kitty.exe is first downloaded and used, the SshHostKeys subdirectory is created as soon as it is needed. However, for some reason, if you try to connect to a server before that, the configured private key is not used.
This affects us, because we roll out a premade package with kitty plus the configuration to client machines. We'll just add an empty SshHostKeys subdirectory to the package, but I thought I'd create an issue anyway, so others with the same problem can find it.