Macrium Reflect (64-bit)

What's new in this version:

Microsoft Exchange 2019:
- Support has been added for Microsoft Exchange 2019 for backup, restore and granular restore.

Update to TLS 1.2:
- The email option in Macrium Reflect has been updated to include TLS 1.2 support.

Rescue Media Files:
- The driver folders for WinPE/WinRE have been expanded to support multiple architectures and WIM versions.
- Bug Fixes

Changed Block Tracker:
- The CBT communications protocol has been improved. The first Incremental after installing may take longer than normal.

Microsoft Exchange Mailbox Restore:
- During the same restore session if the same file was selected twice a mount error would be reported. This has been resolved.

Microsoft Exchange Backup to GUID path:
- The message "Not enough memory resources are available to process this command" could be displayed when backing up exchange to a volume guid path - rather than a drive letter. This has been resolved.

USB host driver copy:
- USB devices could fail to be recognized if Windows PE/RE if the Rescue Media Builder had copied USB host drivers. This is now an optional setting in the RMBuilder 'Advanced' dialog and the defaulted operation for a fresh install is set to disabled. Please enable this option if necessary if - you are having USB problems in the rescue media.

Rescue Media BitLocker unlock:
- The MS utility 'manage-bde.exe' could fail to run correctly in the rescue media. This has been resolved. If this issue affects you then please - re-create your rescue media after updating.

VSS Log Deletion Error:
- VSS logs could be purged by date incorrectly. This has been resolved.

Technicians USB:
- The technicians license could be incorrectly copied to USB and ISO technicians media. This has been resolved. If this issue affects you then - please re-create your rescue media after updating.

Microsoft SQL Restore:
- Server Plus could crash when attempting to restore the SQL tail log. This has been resolved.

viBoot Backup:
- When creating a backup from within viBoot a password was prompted for even if the base image was not password protected. This has been resolved.