Icon The Kermit Project   |   Now hosted by Panix.com
New York City USA   •   kermit@kermitproject.org
since 1981
The first new Kermit release for Windows in nearly twenty years...

  CKW: C-Kermit 10.0 for Microsoft Windows

Download   Install   Run   SSH   Coexist   Documentation

This page assumes a degree of familiarity with Kermit software; if you need an introduction, look HERE.

Frank da Cruz
Created: 16 July 2022
Last update: Thu Jul 21 08:49:29 2022
Work on a free Open Source™ version of Kermit 95 for Microsoft Windows commenced in 2013 then ended inconclusively in 2015 (see this page). Work resumed in 2022 as part of the C-Kermit 10.0 rollout. The first Beta-test version appeared on 17 July 2022. The name of the executable program is K95G.EXE (which is the traditional name, but it might change); it is a text-mode application that executes in a GUI window. The Windows builds and packaging were done by David Goodwin in New Zealand, based on his 2013 work and the latest C-Kermit 10.0 Beta test source code. The result is called C-Kermit for Windows, CKW for short. Source code is not available yet; it will be included beginning with the next C-Kermit 10.0 Beta test, Beta.05. The first downloadable version of CKW announces itself as:
C-Kermit 10.0 OPEN SOURCE:, Jul 17 2022, for Windows
 Copyright (C) 1985, 2022,
  Trustees of Columbia University in the City of New York.
The copyright remains with Columbia U, in accordance with the separation agreement of 2011. CKW uses the C-Kermit version number, not the K95 one, which was different (the last K95 release was 2.1.3, which was contemporary with C-Kermit 8.0.207). The LICENSE command shows the new Open Source license.

SSH Connections

The SSH support code from K95 2.1.3 has been retired because it doesn't work any more due to changes in the ciphers used by modern SSH servers. SSH connections can be made in CKW by using an external helper program as described in THIS PAGE. It is hoped that the final CKW release will have an SSH command that works transparently, like C-Kermit's, i.e. by redirecting an external passthough SSH client such as Plink through a pseudoterminal (using a new Windows API called ConPTY, that did not exist until 2018; this work remains to be done).

David Goodwin says that "executables built with newer versions of Visual C++ likely won't work on older versions of Windows. Building with Visual C++ 2022 should get us PTY support on Windows 10 but at the cost of being able to run on anything older than Windows 7 (the clibs minimum supported windows release). So if we wanted to have a version of C-Kermit that still worked on anything older than Windows 7 we'd have to do two builds — one with a current compiler so people on Windows 10 can use new Windows 10 features like ConPTY, and one with an older compiler which couldn't support those features but could produce binaries that work on old machines. I think at the moment PTY support would really be the only feature difference between something built with a new version of Visual C++ and an old version — everything else would be identical."

Known Problems

Send questions, bug reports, and comments to ckw@kermitproject.org.


  1. Download ckn10b4-2-vc6.zip to your Windows desktop (just click on the highlighted link).
  2. Right-click on the .zip file and choose "Extract All...". This creates a subdirectory called .
  3. Delete the .zip file (right-click → delete).


There is no "one-click" installer yet. Here is the procedure for the first Beta; hopefully it will evolve into something simpler:
  1. Open the "" folder (double-click it).
  2. See a folder called "dist"; double-click it.
  3. The dist folder contains 14 files, which include:

    • k95g.exe - the executable C-Kermit 10.0 for Windows (K95) program
    • k95.exe - ditto, but runs in "console mode" (like DOS, not recommended)
    • MSVCP60.DLL - Microsoft Visual C++ 6 SP6 DLL appropriate for this version of Kermit
    • MSVCRT.DLL - The C Runtime Library that C-Kermit was built with
    • And a bunch of others that can be ignored
    The DLL's are required for Kermit to run, so don't delete them.
  4. If you already have an icon on your desktop called "k95g.exe - Shortcut" from a previous CKW test version, delete it (right-click → delete)
  5. Right-click on k95g.exe and choose "Create shortcut" This creates a file called "k95g.exe - Shortcut"
  6. Drag the "k95g.exe - Shortcut" to your Windows desktop or wherever else you want to run Kermit from.
Leave the folder as it is, don't move, rename, or delete it.


Start (run) the new C-Kermit for Windows program by double-clicking the "k95g.exe - Shortcut" icon. The first time you start it you'll get warnings from Windows and/or your antivirus software because this is a new program and it's free and open-source. Examples of warnings:

  1. Windows protected your PC
    Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.
    More info ← click this
    App:  k95g.exe
    Publisher:  Unknown publisher
    [ Run anyway ] ← click this

  2. Symantec Endpoint Protection Download Insight
    Our information on this file is inconclusive. We recommend not using this file unless you know it is safe.
    [ Remove this file from my computer ]
    [ Allow this file ] ← click this

    Unproven: There is not enough information about this file to recommend it. Very few users: This file has been seen by fewer than 5 Symantec users. Very new: Symantec has known abou this file approximately 2 days.

    Permission: If you press OK, an application exemption will be created for this file. You should allow only files you are sure are safe. Are you sure you want to allow this file?
    [ Cancel ]
    [ OK ] ← click this

These warnings appear only the first time you start the new Kermit.

Coexistence with K95 2.1

If you already have Kermit 95 2.1.3 (or earlier) installed on your PC, CKW won't interfere with it and you can use both versions, and you can still use the K95 Dialer. At present CKW is installed in a folder on your desktop, whereas K95 2.1 was installed in the normal Windows way:
File Filename Directory Kermit variable
Executable (GUI) k95g.exe C:\Program Files (x86)\Kermit 95 2.1\ \v(exedir)
Executable (console) k95.exe C:\Program Files (x86)\Kermit 95 2.1\ \v(exedir)
Initialization file k95.ini C:\Users\user\AppData\Roaming\Kermit 95\ \v(appdata), \v(inidir)
Customization file k95custom.ini C:\Users\user\AppData\Roaming\Kermit 95\ \v(appdata), \v(inidir)
CKW uses the same initialization and customization files. If these files contain any commands not supported by CKW (e.g. "set ssh") or by K95 ("set rename"), you can protect them with:
if < \v(version) 1000000 {
    commands for K95    
if >= \v(version) 1000000 {
    commands for CKW
\v(version) is all-numeric version number of the C-Kermit code used for the Windows build. 1000000 is C-Kermit 10.0 and 800207 is C-Kermit 8.0.207. When CKW is finally released it will still peacefully coexist with K95, although the exact mechanisms have yet to be worked out.


There is no single comprehensive user manual but since C-Kermit for Windows is C-Kermit, you can refer to the C-Kermit documentation for most everything:
For an introduction to the Kermit script language (which lets you write procedures to automate common tasks), see this page:
For CKW's Windows-specific aspects, see:
  1. Chapter 6 of the Kermit 95 manual: Using the Command Screen,
  2. Chapter 7 of the Kermit 95 manual: Using the Terminal Emulator, and
  3. Chapter 8 of the Kermit 95 manual: File Transfer.

The New Open-Source Kermit Project hosted by Panix.com