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

Backup agent version 12.0 release notes

Overview

This page lists new features and bug fixes for backup agent version 12.0.

Version 12.0 is only available after you enable agent modernization. Contact your Customer Success Manager (CSM) to get started.

If you have not enabled agent modernization, version 11.0 is the most recent version.

Backup agent version 12.0.1

March 2, 2023

  • Security updates.
  • Fixed an issue on Mac devices which could display a keychain error to the user in some circumstances.

Backup agent version 12.0.0

October 27, 2022

Features

Agent modernization

Agent modernization separates the functions of the Code42 app into two different agents:

  • Backup agent version 12.0 (and later) performs backup and restore functions.
  • The insider risk agent, which must be installed alongside the backup agent, performs insider risk and security monitoring functions.

See Getting started with Incydr agent modernization for more details.

Enhancements and updates

  • A single deployment properties file can now be used for Windows, macOS, and Linux devices. Previously, a separate file was required for each operating system.
  • Added a new path.analyze Code42 command to help troubleshoot backup path selection and exclusions.
  • Updated third-party library Apache Commons Text to version 1.10.0 to mitigate CVE-2022-42889.
  • Performance and stability improvements.
  • Security updates.

Bug fixes

Fixed issues where:

  • On Ubuntu 18.04 and 20.04, the Code42 service did not automatically restart if the device was restarted.
  • For devices configured to use a proxy URL, restarting the device during the Code42 app installation could prevent the device from reconnecting via the proxy.
  • Full disk access status for macOS devices was reported incorrectly in some cases.
  • The Rosetta translation process was unexpectedly required under some circumstances on macOS devices with the M1 processor.
  • Was this article helpful?