CrashPlan for Windows 歷史版本列表 Page3

更新時間：2018-09-10
更新細節：

更新時間：2018-09-09
更新細節：

What's new in this version:

- OTF support, OpenType Fonts with PostScript outlines

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

What's new in this version:

- OTF support, OpenType Fonts with PostScript outlines

更新時間：2018-09-05
更新細節：

更新時間：2018-08-30
更新細節：

What's new in this version:

- A good number of bug fixes
- New file extension: .birdfont replaces .bf. You can still open your font in older versions of the editor if you change the extention to .bf

更新時間：2018-08-07
更新細節：

What's new in this version:

- Adjust underline thickness and position in a font
- Run faster on Windows
- Export large (CJK) fonts
- Fix parsing of TTF fonts

更新時間：2018-08-01
更新細節：

更新時間：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)

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

What's new in this version:

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

CrashPlan 4.8.2 (64-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 (64-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.