Workplace Desktop 8.4.2
July 4, 2022
We're pleased to announce the release of Workplace Desktop 8.4.2.
The stability and security of our service is always central to our development efforts. All releases contain improvements related to that goal; those improvements may also enhance app performance.
Specifically, in this release we've improved input/output operations and resource usage of the Workplace app.
In addition, Workplace Desktop 8.4.2 includes the features, changes, and issue resolutions listed below.
We've introduced multi-thread caching when copying files into your local cache before they are uploaded to Workplace. This improvement will correct the time lag one might previously have experienced when syncing large files.
We've amended the presentation of the right-click menu in the Workplace Folder in this release, giving Windows 11 users first-level access to the context menu features. Previously, these options were nested one level down in Windows 11.
We have removed support for Transport Layer Security (TLS) 1.0 and 1.1, as they are no longer used in any way by the Workplace service.
In rare cases, a missing or corrupted Windows Registry value could cause Workplace to prompt the user for a password, but not accept a correct entry. The problem has been resolved.
In the case of a failed download, the Workplace app attempted to determine the progress of the file transmission and could not. We have introduced additional exception handling that will trigger a full re-transmission of the file under these circumstances.
Workplace briefly displayed a notification popup with no content after a team linked was copied to the user's clipboard. The notification will now no longer display.
A customer reported a security alert related to Log4j. It was a false alarm and there was no vulnerability, but since we were already examining our logging platform, we elected to exchange log4net for NLog, which we already use elsewhere in the product. This will not result in any changes to your Workplace experience.
In a recent release, we added code that streamlines backup scans. Under rare circumstances, consecutive scans that completed very quickly resulted in the creation of two scan files with the same timestamp-based name. The issue has been resolved by switching to an increment-based naming convention.