Skip to main content

Who is this article for?

Incydr risk agent
Backup and legacy agents

Not sure which agent type you have? See the Organizations screen in the Code42 console.

Instructor, no.

Incydr Professional, Enterprise, Horizon, and Gov F2, no.

Incydr Basic, Advanced, and Gov F1, yes.

HOME
GETTING STARTED
RELEASE NOTES
FAQs
APIs
SYSTEM STATUS
Code42 Support

Code42 legacy agent version 11.0 release notes

Who is this article for?

Incydr risk agent
Backup and legacy agents

Not sure which agent type you have? See the Organizations screen in the Code42 console.

Instructor, no.

Incydr Professional, Enterprise, Horizon, and Gov F2, no.

Incydr Basic, Advanced, and Gov F1, yes.

Overview

This page lists new features and bug fixes for Code42 legacy agent version 11.0.

For the Code42 cloud, see Code42 cloud release notes.

Code42 agent version 11.0.2

User devices begin automatically upgrading February 2, 2023, unless your administrator configured a client update delay.

Enhancements and updates

  • Security updates.
  • Improved accuracy of backup completion percentage.
  • Improvements to archive maintenance.
  • Improvements to logging.
  • Other performance and stability improvements.

Bug fixes

  • Fixed an issue on Mac devices introduced in Code42 agent version 11.0.1 which could display a keychain error to the user in some circumstances. 

Code42 agent version 11.0.1

User devices begin automatically upgrading November 29, 2022, unless your administrator configured a client update delay.

Enhancements and updates

  • Security updates.
  • Updated third-party library Apache Commons Text to version 1.10.0 to mitigate CVE-2022-42889.
  • If a 32-bit installer is used on a 64-bit device, the Code42 agent now automatically upgrades to the 64-bit version.

Bug fixes

Fixed issues where:

  • Devices using a proxy connection and a VPN were intermittently unable to connect to the Code42 cloud.
  • On devices using a VPN connection, the Code42 agent could not connect to its background service in some circumstances.
  • For devices configured to use a proxy URL, restarting the device during the Code42 agent installation could prevent the device from reconnecting via the proxy.
  • The Rosetta translation process was unexpectedly required under some circumstances on macOS devices with the M1 processor.
  • On Ubuntu 18.04 and 20.04, the Code42 service did not automatically restart if the device was restarted.
  • Some file events were not reported if the Code42 agent was unable to obtain the file hash.

Code42 agent version 11.0.0

User devices begin automatically upgrading September 14, 2022, unless your administrator configured a client update delay.

Enhancements and updates

  • For Macs, uninstalling the Code42 agent now uses a Terminal command, instead of the Uninstall.app file. If you use scripts or MDM commands to uninstall the Code42 agent on Macs, you may need to update them for Code42 agent version 11.0. 
  • Performance and stability improvements to both Incydr and backup processes.
  • Security updates.
  • Improvements to logging.

Bug fixes

General
  • Fixed an issue where installing the Code42 agent on a Linux Ubuntu or Debian device did not prompt to install the libxss1 dependency if it was missing. The Code42 agent uses this library to determine if the user is away or present
Insider risk detection

Fixed issues where:

  • Some file events for OneDrive sync folder activity reported the Destination user as "Unknown."
  • Printer detection required manually adjusting the backup file selection to capture images of printed files if all backup sets were locked. Now, images of printed files are captured automatically even if all backup sets are locked. 
Backup and restore

Fixed issues where:

  • On some Windows devices, the Code42 agent intermittently stopped backing up. 
  • Backup statistics in the Code42 console did not include all backup sets in some circumstances.
  • On Windows devices, some metadata was not backed up or restored for files with an Access Control List (ACL).
  • Usernames containing the $ character could prevent the user's home directory from backing up properly.
  • The file verification scan did not automatically run as scheduled under some circumstances. 
  • Windows devices using the User State Migration Tool (USMT) could fail to back up the user profile (.MIG file) if all backup sets were locked.

Known issues

  • Windows devices using the User State Migration Tool (USMT) may fail to apply settings during the device replacement process. If you experience this issue, include the /c option in the LoadState command.
  • Was this article helpful?