Bitvise SSH Client 9.41

Installation:
Windows Server 2025 ships with Windows Terminal 1.18. This contains an issue where, if a console application enlarges the screen buffer height, Windows Terminal later crashes due to division by zero.
In previous Bitvise software versions, the installer would enlarge the screen buffer height if it is small. If the installer is run with Windows Terminal as the console application, and Windows Terminal has not yet updated to a more recent version, this would cause a later installation step to fail with error code 0xC0000142. The issue does not occur if Windows Terminal has already updated.
To improve compatibility with Windows Terminal, Bitvise installers no longer increase the screen buffer height if the console reports it as equal to the window height.
Command-line clients:
The command-line clients sftpc, stermc, sexec and spksc no longer enable the no-flow-control extension by default, unless it is enabled using an explicit parameter. The extension prevents opening additional SSH channels, which prevents the use of the exec command in sftpc, and agent forwarding in stermc.
sftpc:
sftpc now displays the default file transfer mode on startup. The default file transfer mode depends on the server and SFTP protocol version. It is either b (binary) or std (automatic text file detection; text files use SFTP v4+ text mode).
sftpc now detects the Maverick SSHD server via the vendor-id extension, and sets the default file transfer mode for this server to binary instead of std. This SFTP server does not properly implement SFTP v4+ text mode, so the std file transfer mode causes file transfer errors.
SFTP:
For downloads, text file auto-detection should now work with servers such as Maverick SSHD, which do not support re-reading data that was already read.
When errors occur while using SFTP v4+ text mode, the error description will now include a remark that the file was opened using SFTP v4+ text mode.
If the server sends a vendor-id SFTP extension, the information is now displayed or logged as part of the SFTP version message.
stermc:
On Windows 10 versions up to 1909, the Windows function ScrollConsoleScreenBufferW can return errors even though it succeeds. stermc now ignores errors from this function on these Windows versions.

Command-line clients:
Even when output was redirected, the command-line clients sftpc, sexec, stermc, stnlc and spksc would not run unless the process was associated with a console window. Fixed.
User interface:
Names and strings containing the & character were not properly displayed in lists. Fixed.
File transfer:
When using the Move to dialog in the SFTP window, the SSH Client could crash. Fixed.

Graphical client:
User Authentication Banner dialog text can now be selected and copied to clipboard.
Improved default file browse filter for client authentication keypair import.

Terminal:

Restored behavior from previous SSH Client versions, including 8.xx, where right-click can be used immediately after selecting to copy-and-paste the selected text.

The DECSTBM message (Set Top and Bottom Margins) should now be handled correctly.

spksc:

The command-line client for the SSH Public Key Subsystem, spksc, now supports commands to list local keys in addition to public keys configured for public key authentication on the server.

If Ctrl+C was pressed during command execution, spksc would previously hang. Fixed.

Host key manager:

When using the Modify Host Key dialog, pasting a host address containing spaces would cause the SSH Client to crash. Fixed.

Mobaxterm

SFTP drive:
On systems with negative UTC offsets, the Windows Command Prompt would display unexpected error messages as part of directory listings for directories without an SFTP file time. Fixed.
Terminal:
Starting a clipboard selection now pauses terminal output.
Double-clicking the system icon now once again closes the terminal window.
Remote Desktop:
The setting Share clipboard is now enabled for new profiles by default.
Window behavior:
The SSH Client can now be configured to prevent system sleep, for example when connected.
Command-line use:
The log utility did not work at all in version 9.12. Fixed.
The main SSH Client window now supports the option -start=login which can be used in conjunction with other -start=... options. For consistency with previous versions, the option -loginOnStartup is now an alias for -start=login,tray. This means the SSH Client connects automatically and also minimizes to the system notification area. When opening an SSH Client profile through right-click > Connect, the profile is now opened with -start=login, but not tray. This means the SSH Client connects automatically with the main window visible.

SSH:
The SSH Client will now recognize a server with "MFT" in its SSH version string as a variant of "J2SSH_Maverick". This means the SSH Client will no longer send SSH_MSG_EXT_INFO by default to such servers. See the previous compatibility change for J2SSH_Maverick, in version history for SSH Client version 8.42.

Authentication:
When the -keypairFile parameter is used to specify a password-protected keypair in a non-Bitvise format, and no valid passphrase is provided, the log message will now be more useful.

Remote Desktop:
When using the single-click Remote Desktop forwarding feature on an ARM version of Windows, the SSH Client will now disable hooking of the Remote Desktop client (MSTSC). The SSH Client normally does this on Windows x86 and x64 so that the Remote Desktop window title can reflect the destination of the Remote Desktop connection. However, this prevented single-click Remote Desktop forwarding from functioning on ARM versions of Windows.

SFTP:
Since version 8.45, the SSH Client now uses SFTP v6 file open block flags SSH_FXF_BLOCK_WRITE and SSH_FXF_BLOCK_ADVISORY if the server advertises support for them. This helps avoid corruption of files while they are being transferred. We have received a report of a server that advertises support for these flags, but fails an open request if the flags are used. The SSH Client will now repeat an open request that fails this way, without the flags.

Command-line clients:
When using Bitvise SSH Client command line clients sftpc, stermc, sexec, stnlc or spksc using a -keypairFile parameter that points to an encrypted keypair in non-Bitvise format, but without a -keypairPassphrase parameter that would provide a decryption passphrase, the SSH Client would display a cryptic error. The error is now less cryptic.

Зачем ЭТО, когда есть putty ?

In previous 8.xx versions, if the system clock was moved back after a check for updates (in UTC, not time zone specific), an automatic check would be repeated with high frequency. This could consume 80 kbps in bandwidth while the graphical SSH Client was running until the clock caught up. Fixed.
In previous 8.xx versions, an automatic check for updates would be performed if the graphical SSH Client was run with -noRegistry. An automatic check is no longer performed in this situation, but can be performed manually.