User guide Windows

Windows

PlexusTerm also builds for Windows 10/11. Everything works as on Linux except:

  • Local terminal: the default shell is PowerShell 7 (pwsh.exe) when it is on PATH, otherwise Windows PowerShell (powershell.exe), with %COMSPEC% as the last fallback; it starts in %USERPROFILE%. Settings → Terminal → Shell for local terminals picks another one, such as cmd, WSL or Git Bash.
  • File explorer: following the terminal folder needs the shell to send OSC 7 (see File explorer for PowerShell); Windows does not let PlexusTerm read another program's working folder. Permissions… is not offered.
  • Home directory: ~ is %USERPROFILE%, so host keys go to %USERPROFILE%\.ssh\known_hosts and key paths accept both ~/ and ~\.
  • SSH agent: SSH_AUTH_SOCK when set, otherwise the Windows OpenSSH agent pipe \\.\pipe\openssh-ssh-agent (start the "OpenSSH Authentication Agent" service and add keys with ssh-add).
  • Saved files (sessions, settings, macros) rely on the permissions of your user profile instead of Unix file modes.
  • Serial consoles list the COM ports reported by Windows (COM3, ...) and accept a typed port name.
  • Port and network scanners: Windows retries a refused connection for about two seconds, longer than the one-second probe, so closed ports may be listed as filtered. Open ports are found as on Linux.
  • Mosh is not offered: there is no packaged mosh-client for Windows. A Mosh session imported or saved elsewhere reports "Mosh is not available on Windows" unless a mosh-client.exe is on PATH.