Skip to content

Windows

Iain Smith edited this page Sep 14, 2026 · 2 revisions

Windows

veetee runs on 64-bit Windows 10 version 1809 or later. The download is a zip with everything it needs, including GTK 4 and libadwaita; nothing is installed and nothing is written to the registry.

Installing

  1. Download veetee-VERSION-x86_64-windows.zip from the releases page and check it against SHA256SUMS if you like (certutil -hashfile veetee-0.7.0-x86_64-windows.zip SHA256).
  2. Unzip it anywhere, for example to C:\Tools\veetee.
  3. Run bin\veetee.exe, or make a shortcut to it with the options you want, such as bin\veetee.exe --telnet vms1.

The build is not code-signed yet, so SmartScreen may ask before the first run (More infoRun anyway).

What works

Feature On Windows
Emulation, fonts, colour, dual sessions Same as Linux
Local shell Command Prompt (%COMSPEC%) on a Windows pseudo console (ConPTY)
--command Run through cmd /C
--telnet veetee's own Telnet client, as on Linux
--ssh Windows' OpenSSH client (ssh.exe, an optional Windows feature) on a pseudo console
--serial COM3 COM ports through the Windows communications API; Break sends a line break
Keyboard map Saved in %LOCALAPPDATA%\veetee\keymap.toml
vt-headless Included in bin

bin\veetee.exe --help prints every option when run from a Command Prompt.

Differences from Linux

  • Local sessions go through ConPTY. Windows' pseudo console re-draws a program's output itself, so console programs such as cmd see a Windows console rather than a raw VT420 line. Hosts reached with Telnet, SSH or a serial port talk to veetee directly, exactly as on Linux.
  • Host-programmed keys (DECPAK) are matched by key position using Windows virtual-key codes, which assume a US layout; on layouts such as AZERTY a programmed letter key may land elsewhere.
  • OpenGL comes from the graphics driver. Very old drivers, remote desktop sessions and some virtual machines offer only OpenGL 1.1; veetee then cannot draw (see Troubleshooting).

How the Windows build is tested

CI builds and tests the whole workspace on Windows for every push, builds the zip, and launches it with software OpenGL to capture a screenshot of a Command Prompt session. Real graphics drivers, COM port hardware and SSH logins are not covered by CI; reports are welcome.

Clone this wiki locally