2017 build #5554 released today
-
Acronis True Image 2017 for PC (Build # 5554, English, 492.4 MB)2016-09-19Release notes
Build5554Sep 19, 2016
Acronis True Image for Windows
Installation procedure
The installation procedure is straightforward. Please run the downloaded executable file and follow the instructions.
Fixed issues
- A mobile backup reappears in the backup list after it was removed.
- Acronis True Image crashes if an NAS device does not return an IP address.
- Acronis Cloud storage size was not changed in the Acronis Cloud web app, after purchasing additional storage space.
- Cannot start a backup from the Online Dashboard.
- Acronis True Image stops responding when changing a file backup source.
- Files cannot be recovered if the Overwrite existing files check box is cleared.
- An error message about a lost Internet connection appears when recovering from a cloud disk backup.
- An incorrect product name is displayed in the WinPE-based bootable media.
- Acronis True Image crashes when selecting an NAS or a network share as a backup destination.
- The application starts with a 4-second delay.
- Disk recovery does not work after recovery of a deleted file on Acronis Cloud.
- An incorrect product name is displayed in the trial version of the application.
- A cloud backup cannot be created right after creating a new account in the console.
- The silent installation option works incorrectly on the US build of the application.
- The US build of the application cannot be installed with the ext_tracking_id command option.
- After the product update, files and folders selected in a file backup source lose the selection.
- Backup to Acronis Secure Zone does not work.
- Acronis True Image hangs when changing a backup version to recover from in the search dialog.
- An archive size increases when archiving a file that the archive already contains.
- The Bonjour service writes lots of error messages to the system event log.
- On the RU build of the application, text on the Suspend button is cut when the backup name is long.
- The console hangs when several file search requests are entered in a row.
- The text about an expiring subscription is different on the Account tab and on the website.
- An incorrect number of selected files to recover is displayed in the recovery dialog.
- The Add resource dialog does not open when trying to create the first backup of a Facebook account.
- An incorrect translation of the Acronis Universal Restore utility in Chinese Simplified.
- The Russian translation of email notifications is not full.
- The disk backup progress bar shows incorrect information.
- The app uninstaller language does not match the language of the console.
- A backup creation time is not shown fully on some localized versions of the app.
- Starting Acronis True Image resets the Internet connection on some devices.
Known issues
- Backup comments are not visible in the data recovery dialog.
- Comments are not available for nonstop backups.
- The Search dialog does not support recovery of several files from different versions of a backup.
System requirements
Hardware requirements:
- A CPU that supports SSE instructions
Operating systems:
- Windows 10
- Windows 8.1 (all editions)
- Windows 8 (all editions)
- Windows 7 SP1 (all editions)
- Windows Home Server
- Windows XP SP3 (32-bit)
It is possible for the software to work on other Windows operating systems, but it is not guaranteed.
File systems:
- FAT16/32
- NTFS
- Ext2/Ext3/Ext4
- ReiserFS
- Linux SWAP
Storage media:
- Internal hard disk drives
- External hard disk drives with any of the following interfaces: USB (including USB 3.0), eSATA, FireWire (IEEE-1394), and SCSI
- Solid State Drives (SSD)
- Networked storage devices
Same here: Upgraded from 5534 to 5554 from within the app with no problem.
I see the same thing on the "Backing Up" and "Caclulating time remaining" though...
I included an image of my first backup after the update. See the image: Same song, same verse, what is it really doing, Calculating OR Backing up..... Surely with all the time it is taking, it is once again, trying desperately to calculate the time required for the backup. Smiling, I give up, they will never get rid of that .... As long as the backup is ROCK SOLID...We are happy !
Steve
Perdido Beach, AL
#5554 did not fix all NAS-problems.
The window with credentials for NAS-login pops up but connection is always refused.
On every new TI version we have these network-problems ;-)
All,
Please clear all network sessions and try logon again. If you are using Windows 10 with Hibernate/Fast start enabled select reboot from the power options. If using other versions of Windows do a complete shutdown and restart of your machine. These actions will end all net sessions and thus require reconnection to athenticated accounts. This should solve any issues that remain for failed logon connection.
Steve,
I hear your desire for a more realistic backup time display. In that light however it is necessary to understand some of what the app is doing in the background that causes the issue.
As you are probably aware TI uses Windows VSS to create shadow copies of data on disk for use in creating backup images. The way this works is complex but in general the Windows Shadow Copy Service limits storage space for these shadow copies to roughly 20% of available disk space. So for example if you have a 256GB disk that has say 60GB of free space then about 10 GB of that would be a maximum allocation space for shadow copies. If you are creating a backup image of say 100GB then this disk space that the Shadow Copy Serivice uses would need to be deleted and rewritten 10 times during the backup process.
That process cannot happen until all existing data in the copy is written back to disk by the application. This process adds to the time required to complete a backup. Another factor in this is that the whole shadow copy process is done at a block level. A block may contain large chunks of data or small chunks of data. Blocks containing many small chunks of data require more time to process than do a few large chunks.
Additionally, machine hardware plays a role as well, the faster the machine hardware the faster the process. If the data on disk is of a non compressable type this to will add to tihe time for a backup task. Add to this the fact that TI does not fully utilize the resourses of the PC while creating backup images so that a user can continue to use the machine during backup creation and hopefully you will begin to see why this "Calcutating time remaining" seems to never go away.
Eventually it does disappear however and then the time displayed is still effected by all of the above. I believe a different algorythm coule be used for time remaining calculation but I am not confident it would be any better than what is used now and in fact may be even worse. So as you say, as long as the backups themselves are good, be happy!
Cheers!
Enchant,
Thanks for the reply. That was very informative !
I suppose I should not let that little issue annoy me.... however, it still does but the bottom line still is the rock solid backup and restore.
If that works, then we are all very happy.... I'd still love to see those two messages that are shown concurrently go away or at least not be shown at the same time. But, as you pointed out, there are a lot of things going on behind the scenes and if the backup image is good and a restore test works then we are all happy campers !
Have a great day Enchant !
Perdido Beach Steve
Just to add some good news to this post, build 5554 has fixed the cable modem reboot issue and also the inability to write to the ASZ - both now fixed in this update. It also looks to have fixed the install problem that some users were having as far as I am aware.
I performed an upgrade install and it is working great. My plan is to perform a clean install and validate multiple NAS logins.
n8active... try some of the suggestions in
https://forum.acronis.com/forum/126528#comment-393681
I'm connecting to 3 different network devices without issue. If connection is refused, it could very well be your NAS refusing the connection for some reason, (like forgetting to use nasname/username as the username or Windows not allowing you to connect to a single NAS device with more than 1 credential at a time - if using multiiple NAS credentials such as one stored in Windows credential manager, but a different NAS account for backups).