CrashPlan for Windows (32-bit) 歷史版本列表 Page1

更新時間：2017-06-14
更新細節：

What's new in this version:

CrashPlan 4.8.3 (32-bit)
- Corrects a security vulnerability on Windows devices that could allow escalation of privilege

CrashPlan 4.8.2 (32-bit)
- In Code42 environments with child organizations set to not inherit settings from the parent organization, pushing changes to settings in the parent organization incorrectly applies any locked device backup settings in the parent organization to all devices in the child organizations. (Version 5.4.0 only; fixed in 5.4.1)
- The Legal Hold web app columns do not support sorting in version 5.4.
- In Code42 environments with a version 5.3 on-premises master server that also use Code42 cloud storage, the Restore History page may not accurately reflect the user who initiated a device restore (push restore) if restoring from the Code42 cloud destination. Web restores and restores from the CrashPlan app are not affected.
- In Code42 environments with a version 4.3.5.3 on-premises master server that also use Code42 cloud storage, the number of Restores listed in the Device details may not include all restores initiated from the Code42 cloud destination.
- Computer-to-computer backups may stop if one computer upgrades to CrashPlan app version 4.8 and the other computer remains on version 4.7 or earlier. This could occur if one computer is using an unsupported operating system, such as Windows XP (which cannot be upgraded to CrashPlan app version 4.8).
- On a Windows device, after adopting a backup created by an OS X or Linux device, the 4.x CrashPlan app displays 0 MB selected for backup even though files are backed up.
- In organizations with Compliance Settings enabled, Org Admins cannot create child organizations; only SYSADMINS can create child organizations.
- In the 5.x CrashPlan app, if more than one restore is in progress and the user pauses one restore, that restore cannot be resumed until the CrashPlan app is closed and restarted.

CrashPlan 4.8.0 (32-bit)
Fixes And Enhancements:
- Security updates
- Performance and stability improvements
- Removes support for Windows XP, Windows Vista, OS X v10.7.5, and OS X v10.8. Devices on these operating systems will not upgrade to CrashPlan app version 4.8
- Users must now accept the EULA upon account creation instead of during CrashPlan app installation
- Computer-to-computer backups now work properly over UPnP connections
- Corrects a rare issue on Linux devices which could cause the history log to be removed while upgrading the CrashPlan app
- Corrects an issue in which changing the listening port for inbound (computer-to-computer) backups required restarting the CrashPlan app to resume backups
- Changes to network overrides no longer require restarting the CrashPlan service on the device to take effect
- Corrects an issue which could require users with enhanced archive security to re-enter their archive key password or custom key to resume backup activity if the device unexpectedly shut down
- Deactivated computers no longer appear in the list of available devices in the My Account page
- Corrects an issue in which Windows devices could report using the wrong operating system after a Windows upgrade. For example, a device that upgraded from Windows 8 to Windows 10 could still display Windows 8 in the CrashPlan app.
- The OS X admin exclude .Mobile.*Backups/. changed to .MobileBackups/. This change now restricts the exclusion to an exact match on "MobileBackups." Previously, anything containing the words "mobile" and "backups" (for example, "My iPhone Mobile Backups") would have been excluded.
- Changing the language in the CrashPlan app no longer deletes the history log. Now, the history log remains intact and displays each log entry in the language selected at the time the entry was created. This results in a history log with a mix of languages.
- When the CrashPlan app language is set to Automatic, the CrashPlan app now correctly uses the system language in use for the device's operating system. Previously, the CrashPlan app defaulted to use English when set to Automatic.
- Corrects a rare issue in which entering specific commands in the CrashPlan app command-line interface (CLI) caused the CrashPlan app to be inaccessible for users with special characters in their usernames.
- When resetting a password, the error message for entering an invalid answer to the security question now correctly displays "Incorrect answer" instead of "Invalid password."

Known Issues:
- Computer-to-computer backups may stop if one computer upgrades to CrashPlan app version 4.8 and the other computer remains on version 4.7 or earlier. This could occur if one computer is using an unsupported operating system, such as Windows XP (which cannot be upgraded to CrashPlan app version 4.8)

更新時間：2016-05-21
更新細節：

What's new in this version:

- Security updates.
- Performance and stability improvements.
- Corrects a rare issue which could cause unexpected version reduction behavior during archive maintenance if the time and date on a device were manually set to incorrect values and then later reset to the correct date and time.
- Windows 10 devices now display the correct file type thumbnail icon on the Restore screen.
- Corrects an issue in which the title above the destination list on the Destinations > Friends tab could display incorrectly.
- Corrects an issue introduced in version 4.3 in which some Windows devices displayed duplicate CrashPlan tray icons.
- Corrects a rare issue when adding file exclusions in which the Ok button was not enabled until a second exclusion was added.
- Corrects Japanese translations in the CrashPlan history log to now correctly use the abbreviations Kbps and Mbps instead of b KB/s and Mb KB/s.
- Corrects an issue in which changes to the Java memory value were not saved properly if set to a value below the default of 1024.
- Corrects an issue in which some Windows devices were unable to unzip CrashPlan app logs created with the CLI getlogs command.
- In the CrashPlan web app, the version retention settings at Outbound Backup Settings > Versions now include Never as an option. (Never has always been an available option from the CrashPlan app. This change only impacts the CrashPlan web app.)
- Password reset and recovery emails now specify the included link can only be used one time.
- Corrects an issue in which the web restore link incorrectly displayed the file size as 0MB when only one file was selected to restore.
- Corrects an issue in which some metadata was not restored correctly if the file was backed up with Windows Volume Shadow Service (VSS).
- Corrects a rare issue for devices using enhanced archive key security: after upgrading to version 4.5.2, backups paused until the user re-entered the archive key password.
- Improves error message when entering an invalid regex search string on the web restore screen.
- Improves error message during web restores if an archive is temporarily unavailable for search.

更新時間：2016-03-07
更新細節：

What's new in this version:

- Security updates.
- Performance and stability improvements.
- CrashPlan apps installed per user on OS X devices now place upgrade logs in the correct per-user location (~/Library/Logs/CrashPlan).
- Increases the maximum number of wireless network exclusions from 100 to 500.
- Corrects an issue introduced in version 4.4 in which entering the wrong password too many times did not always require you to wait 10 minutes before trying again.
- Corrects a rare issue in which adding a local destination and selecting a custom location for the backup incorrectly placed the backup archive in the default ~/backup/Archives folder.
- Corrects an issue in which adding a file to the backup file selection and then immediately deselecting the file's parent folder could result in the file no longer being selected for backup.
- The Linux CrashPlan app installer now automatically downloads and installs the correct Java Runtime Environment (JRE) if it does not already exist on the device.
- Corrects an issue introduced in version 4.4 on OS X 10.11 devices in which the CrashPlan app would not open from the link in the menu bar app under certain circumstances.
- Corrects an issue introduced in version 4.5 in which deselecting a folder for restore or backup did not always also deselect all the contents in the folder.
- Corrects an issue in which changes to the backup file selection were not immediately detected if a file was removed and then re-added in a different case (for example, changing "My Document" to "my document").
- The CrashPlan app CLI now properly accepts values that contain spaces.
- Uninstalling the Windows CrashPlan app removes all files in C:Program FilesCrashPlan.
- Corrects a rare issue for OS X devices with an apostrophe in the hard drive name in which uninstalling the CrashPlan app could fail.
- On Windows devices, the CrashPlan app now upgrades correctly if installed on a drive other than C:.
- The desktop shortcut icon for the Linux CrashPlan app now correctly appears as the CrashPlan for Home logo instead of the enterprise logo.
- CrashPlan no longer allows you to send email invitations to friends. Instead, to start backing up to or being a destination for a friend's computer, exchange backup codes (listed in the CrashPlan app) with your friend.
- Introduces the CLI command connection.info, which returns the local IP address and ports used by the CrashPlan app.

更新時間：2016-01-25
更新細節：

What's new in this version:

- 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.

Improved or fixed:
- 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
- Corrects an issue introduced in version 4.5 in which manually updating the Java memory allocation in the CrashPlanService.ini file did not persist after restarting the CrashPlan service
- Fewer confirmation messages appear when uninstalling the Windows CrashPlan app

更新時間：2015-12-12
更新細節：

What's new in this version:

Fixes And Enhancements:
- Security updates
- Performance and stability improvements
- 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

更新時間：2015-10-03
更新細節：

What's new in this version:

- Critical security updates
- Corrects an issue in which upgrading to version 4.4.0 of the Windows CrashPlan app could cause logging on the device to stop

更新時間：2015-07-09
更新細節：

What's new in this version:

- Security updates.
- Performance and stability improvements.
- The CrashPlan app now uses dynamic port selection when connecting to the Code42 cloud and computer destinations. If necessary, you can review our tutorial to identify the ports used by the CrashPlan app.
- Corrects an issue that prevented users from restoring a previous version of a file from the CrashPlan web app when the filename contained an apostrophe.
- Corrects an issue that prevented users from using the CrashPlan web app on OS X and Linux to restore files in a folder with restricted permissions.
- Adds a filename exclusion for Windows devices to not back up files or folders ending with .tmp.
- Corrects an issue introduced in 4.1.6 in which the critical backup alert email for a computer not backing up (sent after 7 days by default) would not always send. The warning backup alert email for a computer not backing up (sent after 3 days by default) was not impacted.

更新時間：2015-05-12
更新細節：

What's new in this version:

Fixes And Enhancements:
- Incrementing the version number of the CrashPlan app from version 3.7.0 to 4.2.0 to unify with the Code42 cloud version.
- Better handling of individual files selected for backup with large amounts of metadata (over 1 MB per file).
- Fixed issue with version 3.7.0 of the CrashPlan app that prevented adding multiple filename exclusions at one time.

Security updates.
- Improved labels for CrashPlan archive encryption key security options on Settings > Security screen.
- If Require account password to access CrashPlan desktop application is enabled from Settings > Security, then the CrashPlan app must be able to connect to the Code42 server to verify your password.
- Changes To Friend Destination Restore:
- The recommended steps for restoring a large number of files from a Friend destination, formerly known as Guest Restore, have changed. Specifically, the Guest Restore button has been removed from the CrashPlan app. The Guest Restore button previously allowed you to restore files via your friend’s CrashPlan account when physically situated at your friend’s computer.
- To recover a large quantity of files from a friend destination, you can copy the backup archive directly from your friend’s computer to a portable storage device. Then, follow the steps in Restoring Files From A Friend's Computer to attach the archive to your computer and restore files. For large restore tasks, this method is faster than restoring from your friend over the Internet.
- Files backed up to Friend destinations can still be restored from the Restore tab of the CrashPlan app installed on your computer. This method is recommended for small to medium restore tasks.

更新時間：2015-01-15
更新細節：

What's new in this version:

- The CrashPlan service is now digitally signed.

更新時間：2014-07-24
更新細節：

What's new in this version:

- Corrected an issue preventing an administrator from moving a user to an organization that has a locked encryption key security setting
- The stop server script now gracefully shuts down the PROServer process in situations where the stop script must wait before shutting down the process
- Corrected an issue occurring in some situations where information fails to display in the console
- Push restore now correctly honors "full path" option
- When selecting a subset of files to restore via push restore, the push restore now respects the selection and only restores the chosen subset of files
- Corrected the link to the Code42 product documentation in system generated emails so the link now points to http://support.code42.com
- CrashPlan PRO and CrashPlan PROe public cloud customers may now include in the backup file selection iOS device backups that have been saved to a computer
- Corrected an issue preventing some expired archives from being removed from disk
- Users or devices that were deactivated and then reactivated now correctly show up in counts on User and Organization lists
- In push install situations where auto-registration populates the user's first and last name via a script, attempting to perform a new registration from the CrashPlan app no longer clears the user's first and last name from the account
- Archive owner can now be queried via the RestoreRecord API resource, making it possible to view all restores for files in a specific user's archives
- Improved API documentation for WebRestoreJob, WebRestoreJobResult, and BackupArchiveTimestampRange resources
- Improvements to the sync process for environments in a hybrid or provider configuration
- Addressed a memory issue experienced in some very large environments during the storage server sync process
- General performance and stability improvements
- Security fixes