Skip to main content
CrashPlan Support

CrashPlan For Home Version 4.5.0

Applies to:
  • CrashPlan for Home
Need enterprise or small business documentation?
This article is intended for CrashPlan for Home users. For Code42 CrashPlan and CrashPlan for Small Business documentation, read this page on our enterprise support site.


Version 4.5.0 of the CrashPlan app is a minor release that includes a small number of enhancements and fixes. All CrashPlan apps that connect to the Code42 cloud will be upgraded over several days, beginning on November 23, 2015.

Fixes and enhancements

  • Security updates.
  • Performance and stability improvements.
  • After adopting a computer, CrashPlan now automatically updates the backup file selection to include the User or Home folder of your new computer. This ensures your new computer is protected. Like earlier versions of the CrashPlan app, your previous computer's file selection is also transferred as part of the adoption.
  • Improvements to OS X CrashPlan app upgrades.
  • Corrects an issue introduced in version 4.4 in which entering an incorrect archive key password required restarting the CrashPlan app before being allowed to re-enter the password.
  • Improvements to logging.
  • Corrects an issue for per user CrashPlan app installations in which the backup progress never reached 100% under certain circumstances.
  • The CrashPlan app now displays fewer confirmation dialogs when installing per user on Windows devices.
  • Fixes an issue that caused deactivated devices to display in My Account.

Announcing Linux kernel 2.6.31 retirement

CrashPlan app version 4.5.0 requires Linux kernel version 2.6.32 or later. Additionally, Code42 is retiring support for all distributions running kernel version 2.6.31 or earlier, such as:

  • Red Hat Enterprise Linux 5
  • CentOS 5
  • Ubuntu 6, 7, 8, and 9
  • Debian 5

As of November 30, 2015, the CrashPlan app will not automatically upgrade to version 4.5.0 on devices running kernel version 2.6.31 or earlier. CrashPlan app version 4.4.1 is the last supported version for kernels 2.6.31 and earlier. See Linux CrashPlan App Version 4.5 Cannot Back Up for more details.

Maintenance update 4.5.2

Version 4.5.2 of the CrashPlan app is a patch release that includes the following enhancements and fixes. All CrashPlan apps that connect to the Code42 cloud will be upgraded over several days, beginning on January 12, 2016.

  • Improvements to the CrashPlan app upgrade process.
  • When the CrashPlan app is installed per user in a non-default location on a Windows device, the CrashPlan tray app now opens correctly.
  • Corrects an issue introduced in CrashPlan app version 4.5.0 in which the backup To Do list could incorrectly include files that haven't changed since the last backup.
  • Corrects an issue introduced in version 4.4.1 in which OS X v10.8.5 devices could see repeated error messages in the system.log.
  • Fixes a rare issue in which archive maintenance might not finish properly if a new version of a file was created with a timestamp older than the previous most recent version. This typically occurred if the device's time and date were manually changed to a time in the past.
  • Fewer confirmation messages appear when uninstalling the Windows CrashPlan app.

Known issues

  • When the CrashPlan app is installed per user on a Windows device, executing the shutdown command from the CrashPlan CLI requires the user to sign out of Windows and sign in again in order to restart CrashPlan.
  • When the CrashPlan app is installed with user privileges on a Linux device, users may be required to manually start the CrashPlan service after restarting the device.
  • On Windows devices, the CrashPlan service does not start if the user selects the default installation method (for everyone) but then navigates back in the installation wizard and changes to a per user installation. To correct this issue, uninstall the CrashPlan app and reinstall per user.
  • Devices running Windows Server 2012 R2 do not upgrade to the CrashPlan app version 4.5.2 when installed per user. To use the CrashPlan app on Windows Server 2012 R2, use the default (for everyone) installation method.
  • Was this article helpful?