CrashPlan app version 11.3 release notes

This page lists new features and bug fixes for CrashPlan app version 11.3

For the CrashPlan cloud, see CrashPlan cloud release notes.

CrashPlan app 11.3.1

Bug fixes

April 12, 2024

Fixed an issue where local backup destinations would fail to back up files.

CrashPlan app 11.3.0

New universal sign-in experience

April 9, 2024

Beginning in 11.3.0, the CrashPlan app will redirect to the CrashPlan console to complete the sign-in process.

  • After signing in to the CrashPlan console, the app will open as the signed-in user.
  • This new sign-in experience applies to existing CrashPlan console sessions, so if you sign in directly to the CrashPlan console, the installed app on the device will recognize that session.
  • A server URL is no longer required for most users - if a given username exists in more than one server, the browser will ask for the desired server URL. 

For more information, see our article on signing in to CrashPlan

Enhancements and updates

April 9, 2024

  • For Windows and Mac devices, added the option to pause backups on low data networks in the CrashPlan console, replacing the existing wireless exclusions setting. If this setting is enabled, CrashPlan will automatically pause backups whenever a low-data/metered connection is detected.
  • Removed versioning and retention settings from the CrashPlan app to simplify experience across different product plans. This setting can still be configured via the CrashPlan console.
  • Due to Electron updates, CrashPlan can no longer be installed “per-user” on Linux devices. To continue backing up on affected devices, simply uninstall and reinstall the CrashPlan app in the default location using our step-by-step instructions.
  • In CrashPlan app settings, the “set CPU usage” setting has been renamed to “limit performance” to better describe the effect of the setting on backup performance.
  • Logging improvements.
  • Security updates. 
  • Performance improvements.

Bug fixes

April 9, 2024

Fixed issues where:

  • Administrators were sometimes unable to deploy CrashPlan when using a proxy URL in their deployment policies.
  • Incorrect links appeared in the CrashPlan Professional installer README file.
  • The CrashPlan uninstaller would occasionally fail to stop the CrashPlan service on Windows devices.
  • Some visual elements in the CrashPlan app would not display correctly.
  • The “Retry upgrade” button that appears during the app upgrade process was non-functional.
  • The CrashPlan app would sometimes crash on Linux devices without input peripherals (such as a mouse or keyboard) connected.



Was this article helpful?
0 out of 0 found this helpful

Articles in this section