Bitvise SSH Server: baixar versions anteriors

- Release notes:
- We are anticipating an "information security armageddon" due to increasing ability of AI to find security issues, in all software and systems, which were not found in human testing and code review.
The quality of commercially available AI tools has improved to where they are now indispensable for software correctness. We are applying AI tools proactively to find and fix flaws which previously missed detection.
Users will observe this as an increased frequency of significant and important updates. We believe the time to do this is now, before exploitation becomes too easy.
- Control Panel and Settings:
- Advanced settings and its windows now open much faster.
Recent Windows versions have become painfully slow to open settings, compared to older Windows versions. We implemented optimizations to restore and improve performance.
- Improved interactive diagnostics for connections that fail due to SSH algorithm mismatches.
- SSH:
- Improved multiple avenues which an authenticated client could use to exert disproportionate memory pressure on the server.
- The SSH Server now accepts the client's SSH_MSG_EXT_INFO if the client sends it incorrectly as the next packet after SSH_MSG_SERVICE_REQUEST. Correct client implementations must send this packet after SSH_MSG_NEWKEYS. If the packet is sent late, not all extensions are supported.
If the SSH_MSG_EXT_INFO packet is received even later, this still causes an SSH protocol disconnect.

- Release notes:
- We are anticipating an "information security armageddon" due to increasing ability of AI to find security issues, in all software and systems, which were not found in human testing and code review.
The quality of commercially available AI tools has improved to where they are now indispensable for software correctness. We are applying AI tools proactively to find and fix flaws which previously missed detection.
Users will observe this as an increased frequency of significant and important updates. We believe the time to do this is now, before it becomes too easy to exploit issues by pointing an AI to an executable binary.
- Installation and updates:
- If the SSH Server cannot load instance type settings when upgrading or reinstalling, it now disables checking for updates in new default settings, so that automatic updates remain disabled in case they were disabled previously.
- Reworked corner-case behaviors and status reporting when upgrading settings from much older versions.
- Control Panel and Settings:
- Improved reporting for connections stuck in disconnect cleanup.
- If the SSH Server Control Panel cannot load instance type settings, it now more clearly indicates that update settings will also reset to defaults.
- Scriptable settings:
- Since version 9.51, the BssCfg command-line configuration utility failed to implement round-trip support for BssCfg settings exportText followed by BssCfg settings importText. Fixed.
- Connect profiles:
- When making an outgoing connection via an HTTP CONNECT proxy, the SSH Server now limits the maximum size of received HTTP headers.
- General:
- It is possible for SSH Server subsystems to hang indefinitely after a client disconnects. To some extent, this is unavoidable: Windows API functions can hang indefinitely when accessing a network share. If this happens in a file transfer session, the SSH Server's file transfer subsystem hangs until Windows calls return. It is possible that they never return.
In versions before 9.5x, the SSH Server would mitigate this by unconditionally terminating subsystems after a client disconnects. This could cause pending log events and On-upload commands to not be processed.
In recent versions, we removed the unconditional termination, favoring to wait until the subsystem exits. This revealed that some users are seeing indefinite hangs. Connection cleanup can wait indefinitely for stuck subsystems to complete. This can block new connections until the SSH Server is restarted.
The SSH Server now once again terminates stuck subsystems when a client disconnects, as long as the subsystem is not generating further log events or upload notifications. If a subsystem has to be terminated, the SSH Server now performs a diagnostic mini-dump. Recent dumps are retained in the ChildProcessDumps subdirectory of the SSH Server installation directory.
We are not aware of anything we can do about subsystems which are stuck in Windows APIs that do not return on network share access. However: if you see subsystems stuck in situations without network shares, any dumps would be of interest for us to investigate.
- A number of SSH Server settings support environment variable expansion. The SSH Server previously implemented recursive expansion: an expanded variable could reference another one which would also be expanded. This is atypical for Windows applications and could produce unexpected results. When expanding environment variables, the SSH Server now uses a single expansion pass.
- Improved connection disconnect logging.
- The SSH Server is now less permissive with regard to NUL characters in protocol strings where NULs are not expected.
- Authentication:
- When handling many new connections from SSH, SFTP or SCP clients that use the none preliminary authentication method, the SSH Server could lock out IP addresses because of the number of none authentication requests, even though no authentication attempt carrying actual credentials failed. Fixed.
- File t

- Installation:
- Version 9.63 inadvertently broke compatibility with Windows XP SP3 and Windows Server 2003. Fixed.
- Control Panel and Settings:
- Versions 9.61 - 9.63 would load and use a previous splitter position even if it was too large for the current window. This could result in a settings window where only the navigation pane was visible. Fixed.
- Restoring the SSH Server Control Panel after it's hidden to the system tray should now work better if it was previously displayed on a second monitor that was unplugged.
- BvShell:
- BvShell now supports command operators && and ||. command1 && command2 executes command2 only if command1 is successful (completes with a zero exit code). command1 || command2 executes command2 only if command1 cannot be executed, or completes with a non-zero exit code.

- Release notes:
- We are anticipating an "information security armageddon" due to increasing ability of AI to find security issues, in all software and systems, which were not found in human testing and code review.
The quality of commercially available AI tools has improved to where they are now indispensable for software correctness. We are applying AI tools proactively to find and fix flaws which previously missed detection.
Users will observe this as an increased frequency of significant and important updates. We believe the time to do this is now, before it becomes too easy to find an issue and generate an exploit by pointing an AI to an executable binary.
- DoS protection:
- The previous Accept delay mechanism is now removed. The accept delay was triggered based on static parameters, instead of whether the SSH Server was actually handling the load. Once triggered, the accept delay would discard incoming connections indiscriminately, including from clients that were not the cause of the load. The rate of incoming connections was limited, but under some conditions, the total number of connections that have not authenticated could still accumulate.
- The SSH Server now uses a new DoS protection mechanism. The new mechanism uses similar settings as Accept delay, but applies them differently. The administrator configures a maximum number of unauthenticated connections that the SSH Server will accept from a single IP address when the server is not otherwise under load. If a client exceeds this limit, or if the server is generally under load, it may start to discard connections. The SSH Server now prefers to accept connections from IP addresses that are less similar to those that are causing the load. When connections authenticate, further new connections can be immediately accepted.
Administrators should no longer need to disable DoS protection to accommodate clients which initiate hundreds of concurrent connections. Administrators may still need to increase the setting Max pre-auth conns from single IP. Clients from other IP addresses that connect at the same time as another aggressive client are now less likely to have their connection refused.
- Login serialization:
- The setting Delayed login expiration is now removed. Login attempts that are delayed due to login serialization now expire either consistently with the Login timeout setting for the connection, or after a maximum time if the login timeout is disabled or very long.
- The SSH Server now detects disconnects for connections that are delayed by login serialization, or which receive a Penalty login attempt delay if the configured delay is long.
- For clients connecting using IPv6, the SSH Server would use the full client IPv6 address for login serialization by IP address. The full IPv6 address is too easy for clients to vary. The SSH Server now serializes such login attempts using the 64-bit IPv6 address prefix.
- Stuck connection detection:
- SSH Server versions 9.5x and newer support detection and reporting of stuck connections. The SSH Server now detects stuck connections in additional situations, in particular if connection cleanup is delayed by subsystem exit. This can happen if the file transfer subsystem is stuck in a blocking Windows API while attempting to access a network path.
- Control Panel and settings:
- In versions 9.61 and 9.62, the Manage password cache interface did not display correctly when using dark mode. Fixed.
- Time-based one-time password (TOTP) authentication: When generating a 2D code for authenticators to scan, commonly used authenticators get confused if the Issuer or Issued to fields contain a colon (":"), even if it's URL-encoded. Colons in these fields are now encoded as the Unicode character U+02D0 (Modifier Letter Triangular Colon).
- Scriptable settings:
- In SSH Server versions 9.61 and 9.62, settings that are retained for scriptable compatibility could not be mutated by scripts. Fixed.
For example: the setting $cfg.settings.co

- Release notes:
- We are anticipating an "information security armageddon" due to increasing ability of AI to find security issues, in all software and systems, which were not previously found in human testing and code review.
The quality of commercially available AI tools has improved to where they are now indispensable for software correctness. We are applying available AI tools proactively, to find and fix flaws which previously missed detection.
Users will observe this as an increased frequency of updates with a security or reliability significance. We believe this is important to do now, before anyone can find an issue and generate an exploit just by pointing an LLM to an executable binary.
- Authentication:
- If one of the IP blocking settings Penalty threshold or Total threshold was disabled (set to 0); but not both; the SSH Server would apply an immediate block on the first failed login attempt. Fixed.
- FTPS:
- Fixed a security issue where an FTPS data connection could be matched to the wrong authenticated control connection in some circumstances.
- In Advanced SSH Server settings > TLS algorithms, users can configure restrictions on TLS algorithms for FTPS, in addition to restrictions configured in Windows. In previous SSH Server versions, when used on recent Windows (Windows 10 v1809, Windows Server 2019, or newer), the settings RSA and DH had the opposite effect as intended. Enabling the settings would disable RSA or DH, and disabling the settings would enable them, if they were also enabled in Windows.
The setting for ECDHE operated correctly and is unaffected. SSH, SFTP and SCP are unaffected. Users who disabled RSA and DH key exchange using Windows Schannel settings are unaffected.
- In some circumstances, valid FTPS data connections could be incorrectly rejected with a TLS resume error. Fixed.
- The SSH Server could send an incorrect numeric reply code for some FTPS errors. Clients could interpret the reply code to mean success. Fixed.
- SFTP:
- The SSH Server's file transfer subsystem now throttles incoming data more thoroughly while processing expensive requests.

- General:
- The SSH Server is now more defensive against processing patterns which could cause the SSH Server or its subsystems to allocate large amounts of memory.
- FTPS:
- Fixed issue which can allow hijack of FTPS data connections by an attacker on the network path. Users who enable FTPS should update.
- Authentication:
- If Windows stalls during Windows account lookup, this would previously stall all connections that require Windows account lookup. The SSH Server cannot fully mitigate blockage due to stalling Windows APIs, but the impact of a single stalled lookup is now less system-wide, and lookup for independent accounts can proceed concurrently.
- Auto-execute commands:
- Version 9.51 introduced configurable limits for concurrent execution of custom commands, including On-upload command, Connection on-logon command, On-disconnect command, Windows on-logon command, and Windows on-logoff command. In previous 9.5x versions, these limits were applied incorrectly to also count against commands not yet started, which were still in queue to execute. It was possible for the limits to be exceeded solely by the queued commands. This would cause execution of custom commands to completely stall. Connections that had already disconnected would remain stuck, waiting for command execution and cleanup.
Auto-execute command limits are configured in Advanced settings > Server > Auto-execute commands. Default limits could most readily cause deadlock on servers with a low amount of RAM. If you are using a 9.5x version with custom commands, we recommend updating, while keeping configured limits. If you continue to use a previous 9.5x version, maximally relax the limits under Auto-execute commands.
- Improvements to child process management and monitoring.
- Control Panel and Settings:
- When the SSH Server is stopped, the SSH Server Control Panel would previously immediately clear any displayed notifications about warnings and errors. Existing notifications of this type now continue to be displayed until the SSH Server is next started.
- Ctrl+Backspace is now more consistently supported across input elements.
- The Comment field for account settings entries is now also available in Easy settings.
- UI improvements, including for issues related to dark mode.
- Tightened information that is sent to delegated administrator clients without full administrative access.
- Scriptable settings:
- A new utility PowerShell script, PubKeyMaint.ps1, is available in the SSH Server installation directory. An administrator can run it, or configure it as a scheduled task, to scan the SSH Server's log files and remove client authentication public keys in SSH Server settings which have not been used for a specified number of days.
- Logging:
- The SSH Server now logs elapsed times for all SSH channels, including port forwarding channels.
- Filenames for archived log files now include a dash between the SSH Server instance name and timestamp, consistent with the same change for log files in 9.51.
- SSH:
- Cisco clients advertise support for the SSH protocol extension SSH_MSG_EXT_INFO, but incorrectly disconnect if extension information contains binary data. The delay-compression extension sent by the SSH Server contains binary data. The SSH Server will now avoid sending this extension for Cisco clients.
- Tightened environment variable handling for clients which are permitted to set environment variables for terminal shell and exec requests. Permission to set environment variables is disabled by default for virtual accounts, but enabled for Windows accounts.
- Port forwarding:
- When accepting port-forwarded connections using server-to-client port forwarding (reverse tunneling), the SSH Server would previously impose a fixed limit of 1 connection per listening socket per 200 ms. This would adversely affect normal use, but could still overburden the server if accept rules were taking a long time to process.
The SSH Server now imposes no accept delay under no

- Installation and startup:
- The SSH Server installer still requires administrative rights for installation, but can now be run without administrative rights for help with command-line parameters.
- In previous 8.xx and 9.xx versions, the SSH Server used low-level techniques to improve memory allocation performance on servers that handle many concurrent connections. The improvement is significant, and has worked well for 7+ years. However, after recent Windows updates and hotfixes, some users reported the SSH Server would no longer start, and attempts to reinstall would fail with STATUS_DLL_INIT_FAILED (0xC0000142).
The low-level techniques are inherently sensitive to changes in Windows. We are now seeing these as a surprise with Windows updates and hotfixes. To avoid issues, the SSH Server now disables this low-level functionality by default, but still uses other measures to improve memory allocation performance.
Most users will not notice a performance difference. Servers that handle hundreds of concurrent connections may notice a longer service shutdown. In most cases, this is preferable to the SSH Server not starting after a Windows update.
Most users are not affected by this issue. Users who wish to maximize memory allocation performance can re-enable this by creating two plain text files in the SSH Server installation directory. Name the files BvAlloc32.cfg and BvAlloc64.cfg. In each file, enter a single line:
Hook=yes
This restores the default behavior of previous versions.
- The SSH Server installation now includes a small process startup debugger. The installer will use it automatically for diagnostics in case of STATUS_DLL_INIT_FAILED, which has other possible causes.
- Logging:
- In all previous versions, the SSH Server would fail to log events to the Windows Event Log if the size of the event exceeded the ReportEventW per-string limit (31,839 characters). The SSH Server now truncates overly long events. This in particular affects the I_SERVICE_CONFIG_DESCRIPTION event, which can be very large.
In versions before 9.51, Windows Event Log failures were silently ignored. In 9.5x versions, such failures are logged in the SSH Server's textual log files, and displayed in the SSH Server Control Panel.
- The SSH Server now logs an additional I_SERVICE_STOPPING event when initiating service shutdown.
- File transfer:
- For virtual filesystem mount points of type Another SFTP server, version 9.32 introduced handling to strip or reduce file open block flags sent by the client if the block flags include SSH_FXF_BLOCK_ADVISORY, if the other SFTP server does not support them. This introduced an issue where the SFTP channel would close abruptly if the other SFTP server does not send the supported2 extension. This is now fixed. Most notably, this would happen if the other server is OpenSSH.
Independently of SSH Server version, it is possible to avoid this issue by configuring the SSH Server to always strip block flags for the affected mount point. This can be done using mount point settings:
File sharing behavior: Force File sharing for uploads: Read, Write, Delete File sharing for downloads: Read, Write, Delete

- Startup:
- During SSH Server startup, it is unusual, but possible, for Windows APIs to block initialization of SSH Server components for long periods of time. If the delay was very long, the Long Operations Monitor, a new component in versions 9.5x, could exit unexpectedly if other components have not yet initialized.
The initialization sequence is now reorganized to avoid this type of issue. Additionally, long delays during component initialization are now logged at Info or Trace level, depending on the duration.
- FTPS:
- For FTPS connections, the SSH Server no longer adds the authorized_keys mount point (by default, "/.ssh") if SSH public key management using authorized_keys is enabled for the user.
Previous 9.5x versions would add this mount point for FTPS, even though SSH public key management is not supported using FTPS. Connections that tried to access this path via FTPS would become unresponsive, although the connection would still respond to disconnect.

- Updates:
- In some environments, downloading a new version installer fails with Windows error code 12057 (ERROR_INTERNET_SEC_CERT_REV_FAILED). The Windows error description for this error code is misleading. The update interface now provides an error description which is hopefully more useful.
- Master/follower synchronization:
- The settings interface now checks that a synchronization password is configured, and that at least one host key or fingerprint for the master server is configured in follower settings. Synchronization cannot work without these settings.
- Control Panel:
- In previous versions 9.5x, it was possible for the SSH Server Control Panel to start fully open, instead of creating an icon in the system notification area, if it started before Windows initialized the system notification area. The SSH Server Control Panel now allows extra time for Windows to initialize the system tray. If the tray icon still cannot be created, the Control Panel opens with its window minimized.
- Scriptable settings:
- In previous versions, attempting to use the Bitvise.BssCfg COM object from a process without administrative privileges would result in a 30-second delay, followed by an unhelpful error. This now fails promptly with Access is denied.
- File transfer:
- We have seen that it's possible for Windows API functions to block indefinitely when attempting to connect to a Windows file share (network share), or when accessing a share, or disconnecting from a share.
The SSH Server now implements more granular logging for connection threads which are stuck disconnecting network shares.
When the SSH Server is shutting down, it now aborts prolonged network share disconnects, but Windows APIs may still block threads indefinitely.
We added a Best practices section in our page Accessing network shares, to help administrators increase reliability of Windows file share connections.

- Control Panel and Settings:
- Dark mode: If the Windows color mode is set to Light or Custom; and the Windows app mode is set to Light; then list view headers, scrollbars and system menus would appear with light backgrounds instead of dark. Fixed.
- Logging:
- It is possible to configure the SSH Server with a very long Penalty login attempt delay, for example if the purpose is to confuse clients that attempt to guess passwords. This would cause previous 9.5x versions to log warnings about stuck connections. This is now logged at Info-level only.

- Control Panel:
- Tab and pane titles are now more colorful in dark mode, similar to light mode.
- Settings:
- Versions 9.51 and 9.52 would incorrectly upgrade configured email notifications to the new Summary notification type, instead of the previous Single notification type. The converted Summary notifications would be configured without a time trigger, so they would be sent only rarely, when something causes them to flush.
Installations that newly update from 9.1x to 9.53+ will now have email notifications upgraded to Single, preserving previous behavior. Installations that previously updated to 9.51 or 9.52, and now have non-working Summary notifications, will assign a default time trigger (1 minute) for Summary notifications that lack time triggers.
- When upgrading to previous 9.xx versions, from significantly older versions, Shell access type settings Git access only and Telnet server would be upgraded incorrectly to non-functional Custom shell settings. Fixed for future upgrades, as long as they are performed directly to 9.53 or higher.
- Monitor CPU usage is now disabled in new settings by default. It produces frequent warnings when the system is simply used normally, particularly on systems with limited resources.
- In settings that were newly created by previous 9.xx versions, it was not sufficient to enable Permit S2C forwarding in order to use server-to-client port forwarding (reverse tunneling). The default Listening rule configured for group settings entries in Advanced settings was initialized with Allow listening disabled. This needed to be enabled, or overridden in account settings, for server-to-client port forwarding to work. This is now fixed for newly created settings, newly created groups, or if the administrator resets group settings to defaults.
- In Easy settings, the labels for Next and Back buttons were incorrectly reversed. Fixed.
- Logging:
- Information logged about the currently employed FTPS certificate is now more detailed.
- When an exec request or SCP request is rejected, the sanitized command which the client attempted to execute is now logged.

- Terminal and exec requests:
- In version 9.51, the bash shell access type did not work, and had to be configured using Custom shell settings. Fixed.

- Authentication:
- In previous versions, the SSH Server could enter a state where the login attempt delay feature, which protects against brute-force password guessing, could cause all connections from an IP address to be refused, until a connection arrived from a different IP address, which would unblock the internal state. Fixed.
The setting Penalty login attempt delay is configured in Advanced settings > Connections. It is enabled by default. This setting is essential to limit the effectiveness of brute-force password guessing. If this setting is disabled, password authentication should also be disabled, or the administrator must ensure that all passwords are long, randomly generated and secure.

- Control Panel and Settings:
- The Advanced settings window should now drag more smoothly when moved using the mouse, in particular if the mouse has a high polling rate.

- Installation:
- When using the -keypairs command-line parameter, the SSH Server installer did not support importing passphrase-protected keypairs. Also, the installer would import all keypairs if the file is in the .wkp format (as stored in the Config subdirectory of the SSH Server installation directory); but it would only import the first keypair when using the Bitvise .bkp format, even though the format supports multiple keypairs.
The installer now accepts a -keypairsPass parameter to import passphrase-protected keypairs, and imports all keypairs when using the .bkp format.
- Proxy support:
- When configured to make an outgoing connection via an HTTP CONNECT proxy, the SSH Server now sends an HTTP/1.1 request, including a Host header. Previous versions sent an HTTP/1.0 request (no Host header).
- File transfer:
- If a user was configured with a virtual filesystem mount point with the permission Permit Move Existing, and also Permit Read/Write/Delete New; then after moving or renaming a file, the SSH Server would treat the destination file as a new upload, and permit the user to read, write or delete it; even if the user does not have the corresponding virtual mount point permissions for existing files.
When moving existing files, the SSH Server no longer considers the moved-to file as new.
This issue could have a security impact if you have settings which permit users to move files, but the settings do not account for that previous SSH Server versions will treat moved-to files as new.

- Control Panel and Settings:
- Manage certificates interface: Improved error messages and handling of TLS certificate import. Improved display of certificates and private keys not supported by current cryptography settings.
- The SSH Server implements an installation path hijack check. This displays a warning if the filesystem permissions or ownership of parent directories could allow a path hijack by a less privileged user.
This is not a complete check. Permissions on the installation directory itself are not validated, and remain the responsibility of the administrator. The SSH Server checks for path hijack conditions, which can be subtle.
The BssCfg command-line configuration utility now supports the following commands:
BssCfg instDirCheck <run|status|enable|disable>
These can be used to run the installation path check for diagnostics; to see if it is enabled; or to disable it, if the administrator has confidence in the configured filesystem permissions.
- SSH cryptography:
- Starting with 9.43, the latest versions of Bitvise software no longer use OpenSSL:
- OpenSSL no longer supports versions 1.1.1. Our recent software versions used this to support a handful of algorithms not supported by Windows.
- There are new fixes only available in OpenSSL 3.x.
- OpenSSL 3.x promotes opaque interfaces and hides details. This is the opposite of our requirements.
- OpenSSL 3.x is even larger than 1.1.1, and dramatically increases linker bloat. Updating OpenSSL 1.1.1 to 3.4.1 increases the size of CiWinCng64.dll from 3.3 MB to 5.0 MB. Removing OpenSSL reduces the size to 1.4 MB. The difference, 3.6 MB, is a lot of complexity to support some marginal algorithms.
This change does not affect most algorithms. We support most algorithms using Windows cryptography. Only the following is affected:
- chacha20-poly1305: We now support this algorithm using public domain ChaCha20 implementations from Goll & Gueron (on most CPUs with AVX2), Daniel J. Bernstein (on CPUs without AVX2), and Poly1305 from Andrew Moon (poly1305-donna).
In new Bitvise software installations, chacha20-poly1305 is disabled by default, because it is the most susceptible to the Terrapin attack if the counterparty does not implement strict key exchange. This algorithm is secure if both parties support strict key exchange. In Bitvise software, strict key exchange is supported in versions 9.32 and newer.
- ECDSA and ECDH over the curve secp256k1: On Windows 10 and newer, and Windows Server 2016 and newer, we continue to support this curve using Windows cryptography. On these Windows versions, there is no change.
On Windows Vista to 8.1, and Windows Server 2008 to 2012 R2, secp256k1 is now supported using Crypto++ 5.6. This implementation is not constant-time, so in this case, we enable signature timing mitigations. The timing mitigations favor security over performance: a signature is delayed to take e.g. 50 ms instead of 1 ms.
In SSH, this prime field curve is rarely used. We support it for compatibility with previous versions. We originally added this curve because it is used in Bitcoin, so it is subject to intense scrutiny. However, users who want elliptic curve cryptography, but doubt the widely used NIST curves, have usually chosen Curve25519 and Ed25519.
If FIPS 140-2 cryptography is enabled in Windows, there is no change. If FIPS mode is enabled, Bitvise software already restricts itself only to algorithms supported by Windows. In this case, chacha20-poly1305 is not available, and secp256k1 is available only on Windows versions 10 and newer, which support it.
- Bitvise software versions 9.xx remain compatible with Windows XP and Windows Server 2003. To support SSH cryptography on these platforms, our installers include DLL files CiCpFips32/64.dll and CryptoPP530Fips32/64.dll. These DLLs are not used on Windows Vista and newer, but were previously installed on all Windows versions. They are now no longer installed on Windows versions where they are not used.
- SMTP email

- Master/follower synchronization:
- When configured as a master or secondary master, the SSH Server no longer subjects authentication attempts from followers to logon serialization if the provided synchronization password is correct. This avoids some of the followers receiving disconnects, and having to retry, if many followers connect at the same time.
- Control Panel:
- The feature Query settings with PowerShell did not detect that PowerShell is available when installed on Hyper-V Server 2019. Fixed.