CrashPlan app version 11.2 release notes

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

For the CrashPlan cloud, see CrashPlan cloud release notes.

Enhancements and updates

  • CrashPlan no longer supports installation on 32-bit operating systems.
  • The ability to self-register from the CrashPlan app has been removed to simplify the end-user experience. Administrators can still register users either manually via the CrashPlan console, or via device deployment.
  • Improvements to logging.
  • Performance improvements.
  • Security improvements.

Bug fixes

Fixed issues where:

  • Deploying CrashPlan on networks using exclusively IPv6 could fail.
  • UI logs would have different timestamps than other log files.
  • Extraneous unrelated errors could appear in the service.log file.
  • CrashPlan could display excessive web socket timeout messages in logs.

Windows

Fixed issues where:

  • Deleting the .identity file in the CrashPlan directory would prevent the CrashPlan service from starting.
  • CrashPlan could completely uninstall during an upgrade.
  • A CrashPlan upgrade fails to complete if there is another install occurring on the device.
  • Using the LaunchService.vbs script would fail to start the CrashPlan service. This script has been replaced with CrashPlanService.exe, located in \%appdata%\Local\Programs\CrashPlan\.
  • Upgrade logs would be incorrectly prefixed with “crashplan” (ie. “crashplan_upgrade_msi” instead of “upgrade_msi”.

Mac

Fixed an issue where CrashPlan would fail to report Full Disk Access status correctly.

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

Articles in this section