Known Issues 2025
- Last Updated: March 20, 2026
- 1 minute read
- WS_FTP Server
- Version 2025
- Documentation
This section details known issues and workarounds in all WS_FTP Server 2025.0 (10.0) releases.
|
ID |
Category |
Known Issue Description |
|---|---|---|
|
22306 |
Install, Upgrade |
Certain anti-virus products interfere with PostgreSQL database platform during the install and upgrade process, causing an error. To resolve this issue, disable your anti-virus during the install/upgrade process. The PostgreSQL install/upgrade error is caused by multiple
anti-virus products including:
|
|
25438 |
Anti-virus |
McAfee Endpoint Security is known to inject outdated DLLs (version 14.00.X of vcruntime140.dll and mscvp140.dll) into the IIS process. This causes a “No products installed” error in the WS_FTP Server Manager and renders the client inoperable. To resolve this issue, delete the problematic DLLs from the McAfee\Endpoint Security\Threat Prevention folder or uninstall McAfee Endpoint Security. If removing the anti-virus is not possible, reach out to the McAfee support team to request a process to whitelist the IIS process or an updated McAfee version based on redistributable DLLs version 14.40 or later. |
|
26701 |
FTPS |
WS_FTP Server upgrade requires the FTPS RSA SSL/TLS certificates to have a minimum key length of 2048 bits. Ensure your certificates meet this requirement before continuing. |
|
28259 |
Web Admin |
When a mapped network drive is configured, it does not appear in the Web Admin interface. To resolve this issue, use the UNC path (for example, \\server\share) instead of the mapped drive letter when configuring folder locations. |
|
28276, 28455 |
Multi-factor authentication |
The command-line utility
iftpaddu.exe
does not support options to exempt users from Multi-Factor
Authentication (MFA) or to reset their current MFA
configuration. These operations are available in the Admin
interface but not via the command-line utility. When MFA is
enabled for WS_FTP Server accounts, the Outlook Add-In log
displays the following error message during log on
attempts: |
|
29005 |
Failover |
In a failover configuration, only the first failover node is able to decrypt secrets stored in the shared database. As a result, the secondary node cannot correctly access encrypted data when operating against the common database. To resolve this issue, manually synchronize the encryption keys between
the failover nodes by copying the registry key material:
Note: This issue is resolved for new
failover installations created using the updated setup
process in 2025.0.2. Upgrades from earlier
versions still require manual registry
synchronization |