Back
IBM
Patches for IBM Aspera Desktop Client x64
Windows
10 patches available
Easily integrate rapid, secure data transfer, administrative management and activity monitoring.
IBM Aspera Desktop Client x64 Version 4.4.7.2259
Release Date
5/20/2026
Bug Fix?
Yes
Minor Release?
No
Patch Notes
Release notes: IBM Aspera High-Speed Transfer Server; High-Speed Transfer Endpoint; and Desktop Client v4.4.7.2$$$Last Updated : 2026-05-20$$$This FixPack release includes fixes; and other updates.$$$$$$Product released: May 20; 2026.$$$Release notes updated: May 20; 2026.$$$$$$Issues fixed in this release$$$Aspera #4426 - Resolved an issue where a temporary problem reporting session data to Redis could leave the transfer in state partially_complete .$$$$$$Aspera #4795 - Addressed an issue where request timeouts could cause asperanoded to restart .$$$$$$Aspera #5108 - Corrected an issue with exclude rules not being applied to push Hot FoldersOther Updated the bundled nginx versions in the Linux x86_64 and Linux ppc64le packages.$$$$$$Other changes$$$Updated the bundled nginx versions in the Linux x86_64 and Linux ppc64le packages.
IBM Aspera Desktop Client x64 Version 4.4.7.2245
Release Date
3/5/2026
Bug Fix?
Yes
Minor Release?
No
Patch Notes
Release notes: IBM Aspera High-Speed Transfer Server; High-Speed Transfer Endpoint; and Desktop Client v4.4.7.1$$$Last Updated: 2026-03-05$$$This FixPack release includes breaking changes; new features; fixes; and other updates. Review breaking changes before upgrading.$$$Enhancements$$$Aspera #4811 - Added support in Async for paths with names containing special characters like $$$ and \r.$$$$$$Issues fixed in this release$$$Aspera #4274 - Improve the performance of processing watchfolders with a large amount of files and FILE_TRANSFER_DELETE enabled.$$$$$$Aspera #4617 - The owner of the synchronization directory might not be preserved in Async across multiple runs if the directory needs to be recreated.$$$$$$Aspera #4724 - Transfers from Cloud Object Storage using Trapd might fail with Disk Read Error when checksums are enabled.$$$$$$Aspera #4744 - Transfers using vlink restrictions can end up constrained to about 10% of the limit with no other active transfers sharing the vlink.$$$$$$Known issues$$$When attempting to start the IBM Aspera Desktop Client GUI on macOS Intel machines; the following error message appears: You cant open the application IBM Aspera Desktop Client because this application is not supported on this Mac.$$$$$$Refer - https://www.ibm.com/docs/en/adc?topic=SSXN9J_4.4/relnote/4-4-7-1.htm
IBM Aspera Desktop Client x64 Version 4.4.7.2245
Release Date
3/5/2026
Bug Fix?
Yes
Minor Release?
No
Patch Notes
Release notes: IBM Aspera High-Speed Transfer Server; High-Speed Transfer Endpoint; and Desktop Client v4.4.7.1$$$Last Updated: 2026-03-05$$$This FixPack release includes breaking changes; new features; fixes; and other updates. Review breaking changes before upgrading.$$$Enhancements$$$Aspera #4811 - Added support in Async for paths with names containing special characters like $$$ and \r.$$$$$$Issues fixed in this release$$$Aspera #4274 - Improve the performance of processing watchfolders with a large amount of files and FILE_TRANSFER_DELETE enabled.$$$$$$Aspera #4617 - The owner of the synchronization directory might not be preserved in Async across multiple runs if the directory needs to be recreated.$$$$$$Aspera #4724 - Transfers from Cloud Object Storage using Trapd might fail with Disk Read Error when checksums are enabled.$$$$$$Aspera #4744 - Transfers using vlink restrictions can end up constrained to about 10% of the limit with no other active transfers sharing the vlink.$$$$$$Known issues$$$When attempting to start the IBM Aspera Desktop Client GUI on macOS Intel machines; the following error message appears: You cant open the application IBM Aspera Desktop Client because this application is not supported on this Mac.$$$$$$Refer - https://www.ibm.com/docs/en/adc?topic=SSXN9J_4.4/relnote/4-4-7-1.htm
IBM Aspera Desktop Client x64 Version 4.4.7.2232
Release Date
11/26/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Breaking changes$$$Aspera #3625 - TLS 1.0 and 1.1 are not configurable as the minimum supported TLS versions in aspera.conf.$$$$$$New features$$$Aspera #996 - The Windows and macOS installers include the tooling to tether a node and report transfer activity to Aspera on Cloud.$$$$$$Aspera #3130 - Added a configuration option to limit the maximum number of active transfers.$$$$$$Aspera #3984 - Updated the bundled FIPS module to achieve FIPS 140-3 validation.$$$$$$Aspera #4153 - Improved scanning performance for async on Windows™ when using network storage.$$$$$$Aspera #4261/#4262 - Enabled automatic detection and use of IPv6 in ascp and async without requiring the -6 command line option.$$$$$$Aspera #4459 - Added an option to async to allow relaunching transfer threads if all fail.$$$$$$Issues fixed in this release$$$Aspera #323 - Fixed the logging level of a message incorrectly labeled as an error when no askms keystore is set up.$$$$$$Aspera #3606 - Resolved an issue in async where intermittently unresponsive or inactive storage could result in file deletions.$$$$$$Aspera #3930 - Fixed a problem where a single transfer with a vlink configured might not fully utilize the allowed bandwidth.$$$$$$Aspera #4057 - Corrected deletion counters returned by the summary endpoint in the Async API when a parent directory is deleted.$$$$$$Aspera #4100 - Fixed intermittent problems resuming files in Azure with libpvcl_cloud.$$$$$$Aspera #4142 - Added the missing indication of the resume option in async logs with session parameters.$$$$$$Aspera #4269 - Prevented transfers submitted through the Node API from starting multiple times under system overload.$$$$$$Aspera #4284 - Ensured active transfer listings through the Node API return an iteration token for paging through results.$$$$$$Aspera #4320 - Resolved an issue that prevented NodeD from responding to multiple HTTP or HTTPS listening sockets. The listening sockets limit is now set to 64.$$$$$$Aspera #4374 - Addressed cases where transfers using delete before transfer or remove after transfer could be marked as failed if the process took too long.$$$$$$Aspera #4426 - Corrected transfer status in the Node API that could remain in partially_complete.$$$$$$Aspera #4463 - Resolved issues with libpvcl_cloud and S3 storage where directory operations could fail due to naming patterns.$$$$$$Aspera #4612 - Fixed an issue where Hotfolders might start ascp with incorrect SSH key command line options; causing the transfers to fail until the service is restarted.$$$$$$Other changes$$$Aspera #344 - Enabled the activity_logging configuration option by default in new installations.$$$$$$Aspera #4280 - Enabled the pre_calculate_job_size configuration option by default in new installations.
IBM Aspera Desktop Client x64 Version 4.4.7.2232
Release Date
11/26/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Breaking changes$$$Aspera #3625 - TLS 1.0 and 1.1 are not configurable as the minimum supported TLS versions in aspera.conf.$$$$$$New features$$$Aspera #996 - The Windows and macOS installers include the tooling to tether a node and report transfer activity to Aspera on Cloud.$$$$$$Aspera #3130 - Added a configuration option to limit the maximum number of active transfers.$$$$$$Aspera #3984 - Updated the bundled FIPS module to achieve FIPS 140-3 validation.$$$$$$Aspera #4153 - Improved scanning performance for async on Windows™ when using network storage.$$$$$$Aspera #4261/#4262 - Enabled automatic detection and use of IPv6 in ascp and async without requiring the -6 command line option.$$$$$$Aspera #4459 - Added an option to async to allow relaunching transfer threads if all fail.$$$$$$Issues fixed in this release$$$Aspera #323 - Fixed the logging level of a message incorrectly labeled as an error when no askms keystore is set up.$$$$$$Aspera #3606 - Resolved an issue in async where intermittently unresponsive or inactive storage could result in file deletions.$$$$$$Aspera #3930 - Fixed a problem where a single transfer with a vlink configured might not fully utilize the allowed bandwidth.$$$$$$Aspera #4057 - Corrected deletion counters returned by the summary endpoint in the Async API when a parent directory is deleted.$$$$$$Aspera #4100 - Fixed intermittent problems resuming files in Azure with libpvcl_cloud.$$$$$$Aspera #4142 - Added the missing indication of the resume option in async logs with session parameters.$$$$$$Aspera #4269 - Prevented transfers submitted through the Node API from starting multiple times under system overload.$$$$$$Aspera #4284 - Ensured active transfer listings through the Node API return an iteration token for paging through results.$$$$$$Aspera #4320 - Resolved an issue that prevented NodeD from responding to multiple HTTP or HTTPS listening sockets. The listening sockets limit is now set to 64.$$$$$$Aspera #4374 - Addressed cases where transfers using delete before transfer or remove after transfer could be marked as failed if the process took too long.$$$$$$Aspera #4426 - Corrected transfer status in the Node API that could remain in partially_complete.$$$$$$Aspera #4463 - Resolved issues with libpvcl_cloud and S3 storage where directory operations could fail due to naming patterns.$$$$$$Aspera #4612 - Fixed an issue where Hotfolders might start ascp with incorrect SSH key command line options; causing the transfers to fail until the service is restarted.$$$$$$Other changes$$$Aspera #344 - Enabled the activity_logging configuration option by default in new installations.$$$$$$Aspera #4280 - Enabled the pre_calculate_job_size configuration option by default in new installations.
IBM Aspera Desktop Client x64 Version 4.4.5.1657
Release Date
11/25/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
New features$$$Aspera #106 - Added support for Linux on the ARM 64-bit architecture.$$$$$$Aspera #2740 - Added support to configure TLS v1.3 as the minimum version enabled for TLS connections.$$$$$$Aspera #2899 - Added new statistics to the Node API endpoint for async with metrics that are related to the source scan progress.$$$$$$Aspera #2952 - Added support to specify a remote log location and debug level in async and ascp for transfers that use WebSockets or aspshell.$$$$$$Aspera #3129 - Added support to configure in aspera.conf a minimum version for ascp and async to allow transfers from.$$$$$$Breaking changes$$$In this version; the Redis update might impact HA Redis cluster deployments bound to an external IP address. If authentication is not configured; Redis rejects connections to the external IP. Although configuring authentication is recommended for security; you can alternatively set protected-mode no in the Redis configuration if the IP addresses are accessible only by other cluster nodes.$$$$$$Issues fixed in this release$$$Aspera #2371 - Fixed an issue where updating an access key with partial contents for the storage_class object can reset other keys that are previously set in the same object.$$$$$$Aspera #2946 - Fixed an issue where the setting transfers_share_request is not observed in HSTS clusters.$$$$$$Aspera #2965 - Fixed an issue where transfers might fail when using Object Storage if the object name contains special characters in the key name.$$$$$$Aspera #2996 - Fixed an issue where a transfer that is submitted to the Node API /ops/transfers endpoint might say in Waiting status indefinitely if the job times out before ascp starts.$$$$$$Aspera #2997 - Fixed an issue where an ascp upload that uses stdio-tar might hang if any files that are in the file set is skipped.$$$$$$Aspera #3028 - Fixed an issue where transferring a directory with a very large number of files can cause a crash in ascp.$$$$$$Aspera #3032 - Fixed an issue that caused transfers using the trapd service to fail to start on Microsoft Windows.$$$$$$Aspera #3095 - Fixed an issue where Watchfolders that uses multi-session might result in a transfer hanging.$$$$$$Aspera #3107 - Fixed an issue where the information that was reported by the Node API for a transfer that uses HTTP Fallback mode can be incorrect and incomplete.$$$$$$Aspera #3119 - Fixed an issue where a message Invalid transport parameter can be incorrectly logged in a Watchfolder in Pull mode.$$$$$$Aspera #3134 - Fixed an issue where transferring a directory with a very large number of files can cause a crash in ascp.$$$$$$Aspera #3137 - Fixed an issue where ascp4 transfers that use --delete-before on Microsoft Windows does not work as expected in some cases.$$$$$$Aspera #3141 - Fixed an issue where files with the .asp-meta extension and other special extensions were not filtered by using the /files/page Node API endpoint.$$$$$$Aspera #3145 - Fixed an issue where resuming very large files can cause UDP timeout errors and the transfer to fail.$$$$$$Aspera #3251 - Improved the scan performance in async when running on Microsoft Windows that uses a UNC path as the source.$$$$$$Aspera #3276 - Fixed an issue where the error message is unclear in async when using --create-dir and the directory fails to be created.$$$$$$Aspera #3305 - Fixed an issue where transfers that use WebSockets as the transport fail to start through IBM Aspera Proxy configure in forward proxy mode.$$$$$$Other changes$$$Aspera #2421 - The aclean tool was deprecated in HSTS/HSTE 4.4.4 and removed in the 4.4.5 release.$$$$$$Aspera #2572 - The Hadoop Distributed File System (HDFS) was discontinued in HSTS/HSTE 4.4.4. Support and documentation were removed in the 4.4.5 release. An alternative workflow is available using IBM Aspera faspio Gateway.$$$$$$Aspera #3217 - The DSA SSH keys that are bundled are deprecated and will be removed in a future version of the product.
IBM Aspera Desktop Client x64 Version 4.4.5.1657
Release Date
11/25/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
New features$$$Aspera #106 - Added support for Linux on the ARM 64-bit architecture.$$$$$$Aspera #2740 - Added support to configure TLS v1.3 as the minimum version enabled for TLS connections.$$$$$$Aspera #2899 - Added new statistics to the Node API endpoint for async with metrics that are related to the source scan progress.$$$$$$Aspera #2952 - Added support to specify a remote log location and debug level in async and ascp for transfers that use WebSockets or aspshell.$$$$$$Aspera #3129 - Added support to configure in aspera.conf a minimum version for ascp and async to allow transfers from.$$$$$$Breaking changes$$$In this version; the Redis update might impact HA Redis cluster deployments bound to an external IP address. If authentication is not configured; Redis rejects connections to the external IP. Although configuring authentication is recommended for security; you can alternatively set protected-mode no in the Redis configuration if the IP addresses are accessible only by other cluster nodes.$$$$$$Issues fixed in this release$$$Aspera #2371 - Fixed an issue where updating an access key with partial contents for the storage_class object can reset other keys that are previously set in the same object.$$$$$$Aspera #2946 - Fixed an issue where the setting transfers_share_request is not observed in HSTS clusters.$$$$$$Aspera #2965 - Fixed an issue where transfers might fail when using Object Storage if the object name contains special characters in the key name.$$$$$$Aspera #2996 - Fixed an issue where a transfer that is submitted to the Node API /ops/transfers endpoint might say in Waiting status indefinitely if the job times out before ascp starts.$$$$$$Aspera #2997 - Fixed an issue where an ascp upload that uses stdio-tar might hang if any files that are in the file set is skipped.$$$$$$Aspera #3028 - Fixed an issue where transferring a directory with a very large number of files can cause a crash in ascp.$$$$$$Aspera #3032 - Fixed an issue that caused transfers using the trapd service to fail to start on Microsoft Windows.$$$$$$Aspera #3095 - Fixed an issue where Watchfolders that uses multi-session might result in a transfer hanging.$$$$$$Aspera #3107 - Fixed an issue where the information that was reported by the Node API for a transfer that uses HTTP Fallback mode can be incorrect and incomplete.$$$$$$Aspera #3119 - Fixed an issue where a message Invalid transport parameter can be incorrectly logged in a Watchfolder in Pull mode.$$$$$$Aspera #3134 - Fixed an issue where transferring a directory with a very large number of files can cause a crash in ascp.$$$$$$Aspera #3137 - Fixed an issue where ascp4 transfers that use --delete-before on Microsoft Windows does not work as expected in some cases.$$$$$$Aspera #3141 - Fixed an issue where files with the .asp-meta extension and other special extensions were not filtered by using the /files/page Node API endpoint.$$$$$$Aspera #3145 - Fixed an issue where resuming very large files can cause UDP timeout errors and the transfer to fail.$$$$$$Aspera #3251 - Improved the scan performance in async when running on Microsoft Windows that uses a UNC path as the source.$$$$$$Aspera #3276 - Fixed an issue where the error message is unclear in async when using --create-dir and the directory fails to be created.$$$$$$Aspera #3305 - Fixed an issue where transfers that use WebSockets as the transport fail to start through IBM Aspera Proxy configure in forward proxy mode.$$$$$$Other changes$$$Aspera #2421 - The aclean tool was deprecated in HSTS/HSTE 4.4.4 and removed in the 4.4.5 release.$$$$$$Aspera #2572 - The Hadoop Distributed File System (HDFS) was discontinued in HSTS/HSTE 4.4.4. Support and documentation were removed in the 4.4.5 release. An alternative workflow is available using IBM Aspera faspio Gateway.$$$$$$Aspera #3217 - The DSA SSH keys that are bundled are deprecated and will be removed in a future version of the product.
IBM Aspera Desktop Client x64 Version 4.4.6.2029
Release Date
7/8/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Breaking changes$$$Aspera #2422 - The aclean program is not included with the product.$$$$$$Aspera #3218 - The legacy DSA key used for SSH connections from very old and unsupported versions of IBM Aspera client applications and SDKs is not included with the product.$$$$$$Enhancements$$$Aspera #1743 - Added a new configuration option for FIPS to set up strict mode to require both sides of the transfer to be setup in FIPS mode for the transfer to take place.$$$$$$Aspera #2781; #2782 - Updated asperanoded and asperahttpd to enforce the use of the configured provider for FIPS if the setting is enabled in aspera.conf.$$$$$$Aspera #2789 - Added new options to async to enable preserving Cloud Object Storage metadata.$$$$$$Aspera #3052 - Added the capability to configure custom client encryption password complexity requirements for an access key.$$$$$$Aspera #3184 - Added a new configuration setting and Node API endpoints to allow using arbitrary SSH keys for transfers that uses transfer tokens. For information about the configuration of these keys; see Configuring SSH dynamic keys.$$$$$$Aspera #3519 - Improved the reporting of deleted files for async in the log to follow the same format and can ensure that there is a log entry in all situations where a file might be deleted.$$$$$$Aspera #3546 - Added a new option to async to specify a timeout for the move operation from the local cache to the destination path.$$$$$$Aspera #3736 - Fixed an issue where the preserve_creation_time option for an async job using the API is ignored on Windows.$$$$$$Aspera #3755 - Added a new field to the data reported for a transfer to indicate when a transfer stalls.$$$$$$Issues fixed in this release$$$Aspera #105 - Fixed an issue where the asperaejd service attempts to run and gets restarted when it fails even if there is no configuration for it in place.$$$$$$Aspera #843 - Fixed an issue where the information that is reported through Lua for events of type session do not include the state key.$$$$$$Aspera #2790 - Fixed an issue where an async job might be reported as defunct after issuing a stop request through the Async Node API.$$$$$$Aspera #3144 - Fixed an issue where concurrent transfers controlled by vlinks with different policies might result in transfers with policy low using a higher rate than transfers with policy high.$$$$$$Aspera #3185 - Fixed an issue where async sessions can hang when transferring a large number of small files using libpvcl_cloud.$$$$$$Aspera #3342 - Fixed an issue where asperawatchfolderd might fail with a crash when attempting to delete directories during the post processing step.$$$$$$Aspera #3372 - Fixed an issue that was introduced in 4.4.5 where connections to Redis fail to work when there is a db_host configuration setting in aspera.conf with a hostname longer than 64 bytes.$$$$$$Aspera #3428 - Fixed an issue where files that encounter a specific error condition in mirror mode might be deleted from the source.$$$$$$Aspera #3505 - Fixed an issue where the data returned by the /ops/transfers endpoint for a download by using HTTP Fallback reports an incomplete path.$$$$$$Aspera #3576 - Fixed an issue where post-processing might not take place for some files transferred that use WatchFolders.$$$$$$Aspera #3628 - Fixed an issue where a message that indicates that a possible malicious attack might be erroneously written to the log file.$$$$$$Aspera #3642 - Fixed an issue where async does not preserve timestamps if the destination path is specified as URI or access keys are used.$$$$$$Aspera #3657 - Fixed an issue where transfers initiated that uses the WebSockets transport fail to start if the destination path is specified as a UNC path.$$$$$$Aspera #3748 - Fixed an issue where the session statistics reported can show invalid counter values$$$$$$Aspera #3750 - Fixed an issue that was introduced in 4.4.5 where submissions to /ops/transfers fail with an error when a ssh_private_key is specified in the JSON payload.$$$$$$Aspera #3767 - Fixed an issue where the /asyncs/ID/
IBM Aspera Desktop Client x64 Version 4.4.6.2029
Release Date
7/8/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Breaking changes$$$Aspera #2422 - The aclean program is not included with the product.$$$$$$Aspera #3218 - The legacy DSA key used for SSH connections from very old and unsupported versions of IBM Aspera client applications and SDKs is not included with the product.$$$$$$Enhancements$$$Aspera #1743 - Added a new configuration option for FIPS to set up strict mode to require both sides of the transfer to be setup in FIPS mode for the transfer to take place.$$$$$$Aspera #2781; #2782 - Updated asperanoded and asperahttpd to enforce the use of the configured provider for FIPS if the setting is enabled in aspera.conf.$$$$$$Aspera #2789 - Added new options to async to enable preserving Cloud Object Storage metadata.$$$$$$Aspera #3052 - Added the capability to configure custom client encryption password complexity requirements for an access key.$$$$$$Aspera #3184 - Added a new configuration setting and Node API endpoints to allow using arbitrary SSH keys for transfers that uses transfer tokens. For information about the configuration of these keys; see Configuring SSH dynamic keys.$$$$$$Aspera #3519 - Improved the reporting of deleted files for async in the log to follow the same format and can ensure that there is a log entry in all situations where a file might be deleted.$$$$$$Aspera #3546 - Added a new option to async to specify a timeout for the move operation from the local cache to the destination path.$$$$$$Aspera #3736 - Fixed an issue where the preserve_creation_time option for an async job using the API is ignored on Windows.$$$$$$Aspera #3755 - Added a new field to the data reported for a transfer to indicate when a transfer stalls.$$$$$$Issues fixed in this release$$$Aspera #105 - Fixed an issue where the asperaejd service attempts to run and gets restarted when it fails even if there is no configuration for it in place.$$$$$$Aspera #843 - Fixed an issue where the information that is reported through Lua for events of type session do not include the state key.$$$$$$Aspera #2790 - Fixed an issue where an async job might be reported as defunct after issuing a stop request through the Async Node API.$$$$$$Aspera #3144 - Fixed an issue where concurrent transfers controlled by vlinks with different policies might result in transfers with policy low using a higher rate than transfers with policy high.$$$$$$Aspera #3185 - Fixed an issue where async sessions can hang when transferring a large number of small files using libpvcl_cloud.$$$$$$Aspera #3342 - Fixed an issue where asperawatchfolderd might fail with a crash when attempting to delete directories during the post processing step.$$$$$$Aspera #3372 - Fixed an issue that was introduced in 4.4.5 where connections to Redis fail to work when there is a db_host configuration setting in aspera.conf with a hostname longer than 64 bytes.$$$$$$Aspera #3428 - Fixed an issue where files that encounter a specific error condition in mirror mode might be deleted from the source.$$$$$$Aspera #3505 - Fixed an issue where the data returned by the /ops/transfers endpoint for a download by using HTTP Fallback reports an incomplete path.$$$$$$Aspera #3576 - Fixed an issue where post-processing might not take place for some files transferred that use WatchFolders.$$$$$$Aspera #3628 - Fixed an issue where a message that indicates that a possible malicious attack might be erroneously written to the log file.$$$$$$Aspera #3642 - Fixed an issue where async does not preserve timestamps if the destination path is specified as URI or access keys are used.$$$$$$Aspera #3657 - Fixed an issue where transfers initiated that uses the WebSockets transport fail to start if the destination path is specified as a UNC path.$$$$$$Aspera #3748 - Fixed an issue where the session statistics reported can show invalid counter values$$$$$$Aspera #3750 - Fixed an issue that was introduced in 4.4.5 where submissions to /ops/transfers fail with an error when a ssh_private_key is specified in the JSON payload.$$$$$$Aspera #3767 - Fixed an issue where the /asyncs/ID/
IBM Aspera Desktop Client x64 Version 4.4.4.1313
Release Date
6/28/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
New features$$$Aspera #1477 - Added the capability in async to restart a failed ascp process when using multiple transfer threads.$$$$$$Aspera #2720 - Added the option to libpvcl_cloud to disable the Glacier class option in Amazon S3.$$$$$$Issues fixed in this release$$$Aspera #134 - Fix potential crash in ascp4 transfers.$$$$$$Aspera #2342 - Enforce strict order for deletions before any transfers start when using --delete-before in async.$$$$$$Aspera #2766 - Resolved an issue that when using growing files with a slow reader; the growing file stops sending before the file stopped growing.$$$$$$Aspera #2767 - Fixed an issue where libpvcl_cloud fails to create objects that contain special characters in their paths.$$$$$$Aspera #2821 - Fixed an issue where Lua scripts are not being activated.$$$$$$Aspera #2908 - Restored signing and notarization on the MacOS installer for both Intel and ARM v8 architectures.$$$$$$Aspera #2973 - Fixed an issue where libpvcl_cloud does not work with access keys while server-side-encryption is set to NONE.
IBM Aspera Desktop Client x64 Version 4.4.4.1297
Release Date
3/28/2024
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
New features$$$Aspera #492 - Added support for Growing Files to work with a Cloud Storage destination.$$$$$$Aspera #769 - Updated cryptographic library and FIPS module to use the latest validated module from OpenSSL 3.$$$$$$Aspera #854 - Added support to specify and pass the unit sizes -K; -M; or -G to the --support-resume async option. For example; to specify megabytes use --support-resume=xxxM instead of using separate -K; -M; and -G units.$$$$$$Aspera #1443 - Added support for requiring strong passwords for Node API access as the default option. It is enabled by default when creating Node API users as well.$$$$$$Aspera #1751 - Improved file browsing cache so that when a ascp transfer occurs the browsing cache for the directory is updated instead of being invalidated$$$$$$Aspera #1905 - Added statistics in the log files for storage I/O performance when using pvcl_cloud storage modules; such as Cloud Object Storage.$$$$$$Aspera #1943 - Improved pvcl_cloud logging to generate more data for all logging modes (info and debug).$$$$$$Breaking changes$$$Aspera #2001 - On Windows; the port files directory defaults to stronger permissions; allowing only Administrator users to create port files for monitoring transfers with the Desktop GUI.
IBM Aspera Desktop Client x64 Version 4.4.3.891
Release Date
9/26/2023
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Release Notes: IBM Aspera High-Speed Transfer Server;$$$High-Speed Transfer Endpoint; and Desktop Client; 4.4.3$$$Product Released: September 26; 2023.$$$Release Notes Updated: September 26; 2023.$$$This release of IBM Aspera High-Speed Transfer Server (HSTS); High-Speed Transfer Endpoint (HSTE);$$$and Desktop Client provides the new features; fixes; and other changes that are listed in the following$$$sections. In particular; the Breaking Changes section provides important information about modifications$$$to the product that might require you to adjust your workflow; configuration; or usage. Additional sections$$$cover system requirements and known problems.$$$New features$$$Added support to Watchfolders for using multi-session mode for transfers in parallel. (Aspera #20)$$$Added a new configuration option db_cert_file to specify the certificate that is used to enable and$$$verify TLS connections to the configured Redis server. (Aspera #807)$$$Added support for specifying URIs as source and destinations in async. (Aspera #991)$$$Added support to async to use local Basic and Bearer tokens. (Aspera #992)$$$Added support for reporting HTTP fallback transfers activity through the Node API. (Aspera #1133)$$$SSH Pull watchfolder to work without a token. (Aspera #1191)$$$Added support for newer algorithms that allow the transfer tools to connect as clients to servers with a$$$hardened SSH configuration. (Aspera #1484)$$$Added support for specifying a replacement character in asperatrapd if object names contain XML$$$control characters. (Aspera #1550)$$$Added additional settings to the pvcl_cloud library to control how it connects to Cloud Object Storage$$$servers. (Aspera #1691)$$$Added support to async to use Node user bearer tokens for transfer authorization. (Aspera #1726)$$$Issues fixed in this release$$$Aspera #69 - Fixed an issue where transfers that are returned by /ops/transfers using iteration$$$tokens might return inconsistent or duplicate results.$$$Aspera #838 - Fixed an issue where access keys might not be updated to modify the credentials if the$$$previous credentials had expired.$$$Aspera #850 - Fixed an issue where configuration setting in aspera.conf associated with a Local Group$$$in a domain environment would not be applied.$$$Aspera #887 - Reduced the default verbosity of the log messages generated by the pvcl_cloud library.$$$Aspera #1120 - Fixed a potential memory leak in ascp when running in persistent mode.$$$Aspera #1204 - Fixed an issue where the expiration of tokens that are issued by the Cloud Object Storage$$$service might not be properly managed when using the pvcl_cloud library.$$$Aspera #1347 - Reduced the default verbosity of the log messages generated by the asperarund process.$$$Aspera #1354 - Fixed an issue where async jobs might be terminated if a file is removed from the source$$$system while it is being processed for synchronization.$$$Aspera #1386 - Fixed an issue where async would repeatedly assign the same paths to transfer$$$processes that had terminated with an error.$$$Release Notes: IBM Aspera High-Speed Transfer Server; High-Speed Transfer Endpoint; and Desktop Client;$$$4.4.3 1$$$Aspera #1391 - Fixed a performance regression when downloading from Cloud Object Storage using$$$asperatrapd.$$$Aspera #1423 - Updated and resolved the problem that prevented asperanginx from starting correctly in$$$4.4.2.$$$Aspera #1528 - Fixed an issue where it is not possible to register or use an entitlement license when$$$deployed on Microsoft Windows in 4.4.2.$$$Aspera #1534 - Fixed an issue where asperarund sometimes does not stop asperawatchd or$$$asperawatchfolderd processes.$$$Aspera #1544 - Fixed a resource leak in asperanoded when activity_logging is enabled and there$$$are no access keys.$$$Aspera #1547 - Fixed an issue where a PUT request to update an access key would be rejected if the$$$payload contained an id field with the same access key ID.$$$Aspera #1577 - Fixed an issue where transfers token generated through a request to the /file
IBM Aspera Desktop Client x64 Version 4.4.2.572
Release Date
5/2/2023
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Release Notes: IBM Aspera High-Speed Transfer Server;$$$High-Speed Transfer Endpoint; and Desktop Client; 4.4.2$$$Product Released: May 2; 2023.$$$Release Notes Updated: May 2; 2023.$$$This release of IBM Aspera High-Speed Transfer Server (HSTS); High-Speed Transfer Endpoint (HSTE);$$$and Desktop Client provides the new features; fixes; and other changes that are listed in the following$$$sections. In particular; the Breaking Changes section provides important information about modifications$$$to the product that might require you to adjust your workflow; configuration; or usage. Additional sections$$$cover system requirements and known problems.$$$NEW FEATURES$$$Added support in async for storing the preserved ACL contents in the async database. (Aspera #25)$$$Added support for authenticating to Redis by using ACL user identifiers and storing them securely in$$$askms. (Aspera #388)$$$Added support for preserving Object Lock and Legal Hold metadata for AWS S3 objects when$$$transferring from an AWS S3 source to an AWS S3 destination. (Aspera #413)$$$Added support for a new option in async to perform deletes before new or updated files are transferred to$$$the destination. (Aspera #514)$$$Added support for timestamp; uid; and gid preservation for growing files through Watch Folders. (Aspera$$$#546)$$$Added support for additional parameters for growing files through Watch Folders like ssh fingerprint; read$$$block size; connect timeout; ... (Aspera #617)$$$Added support for automatically storing and updating the ID of the primary asperanoded node in a HA$$$redis deployment. (Aspera #633)$$$BREAKING CHANGES$$$If you are upgrading from a previous release; the following changes in this release might require you to$$$adjust your workflow; configuration; or usage.$$$Aspera #940 - The default for _transfer_in_bandwidth_flow_min_rate_cap and$$$_transfer_out_bandwidth_flow_min_rate_cap has changed from Unlimited to 0 to prevent$$$setting a minimum rate that conflicts with the vlink configured rate.$$$Aspera #1056 - The --log-io functionality in asperanoded has been remove
IBM Aspera Desktop Client x64 Version 4.4.1.51
Release Date
11/29/2022
Bug Fix?
Yes
Minor Release?
Yes
Patch Notes
Please refer below URL for release notes:$$$$$$https://www.ibm.com/docs/en/asdc/4.4?topic=release-notes
Interested in automating patching for IBM Aspera Desktop Client x64?