New build is 6581 release October 26th
https://www.acronis.com/id-id/support/updates/changes.html?p=38724
What’s new?
- Full support for high-DPI screens.
- Custom text labels in the subject of the email notification messages that simplify monitoring backup statuses.
- Timing of the product notifications has been coordinated.
- An option to limit the upload speed when you back up data to Acronis Cloud.
- When creating a WinPE media, there is no need to download Acronis Media Add-on because it is included in the product installer.
- An option that allows a user to force or to delay a computer shutdown while a backup is in progress.
- Switching between UI elements has been accelerated and improved.
- NVMe drives and eMMC drives are supported in both the normal and standalone (bootable media) versions of Acronis True Image.
- Different issue fixes, increased stability, and performance improvements.
Fixed issues
This release includes the following issue fixes, increased stability, and performance improvements:
- Episodic crash while closing application
- Acronis True Image 2016 disables Windows 10 fast startup
- The message about terminating current operations prevents a computer from shutdown
- Under bootable media, Acronis True Image 2016 (build 6027) doesn't see the internal disk on Microsoft Surface 3 and Microsoft Surface 4
- The error "Cannot create a database" appears when starting Acronis True Image 2016
- The default subject of email notification messages is changed to the computer name
- A disk cloning operation fails, and the computer boots directly to Windows
- The default sync was deleted after the product update
- Only the first custom backup scheme is saved correctly
- The current Try&Decide changes are discarded after you select to keep them when the computer restarts
- A P2P sync fails when you join this sync on the second computer
- The product sends a lot of requests to the server, which can lead to instability of the Online Dashboard
- The product turns off the Windows 10 Fast Startup function every time the computer starts
- A backup fails if it contains a folder that has a space or a period symbols in its name
System requirements
Operating systems:
- Windows XP SP3 32-bit *
- Windows Home Server
- Windows 7 SP1 (all editions)
- Windows 8 (all editions)
- Windows 8.1 (all editions)
- Windows 10
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
Steve, the main Acronis web site does not show this in my account yet, but if I go to the older version of the site at https://www.acronis.com/en-gb/my/products/index.html then I see as shown in the screen shot below:
The new build was only released yesterday so may take time to perculate to the various different Acronis sites.
Update: I just tried to download this latest build from the old download site and was given the following error:
Download file request
- We are very sorry but service is unavailable now. Please try again later.
Thanks Steve,
I don't even see that option on old products URL, guess I have to be more patient and wait a couple days...
Now downloading AcronisTrueImage2016_6581.exe from the old products site at 480MB and the latest Rescue Media ISO AcronisTrueImage2016_6581.iso at 537MB.
New site doesn't show any Installation File or Bootable Rescue Media ISO but does state that 6581 is now the latest build, so is catching up gradually.
My copy of ATI 2016 checked for updates at startup this morning and prompted me to download version 6581. Update succeeded.
Hi Yes Mr. impatient (ME) got the notification today and upgraded just fine to the new release.
Can't make rescue media automatically to USB flash drive?
Can't make rescue media automatically to USB flash drive?
No, you must have the updated version installed first and then use the rescue media builder from within the Acronis app to make a USB flash. The alternative is to download the .iso from your account and then you can use a tool like RUFS to transfer the .iso to a UsB flash drive. Only the embedded rescue media builder is officially available/supported by the Acronis True Image Application though.
56610: Acronis True Image 2016: Creating Bootable Media
I installed the update over the existing version when the notification came in about the new version. Selected some icon on the left which took me to media builder. USB flash was not listed. Just two lines of ISO and then DVD.
I gather I can make bootable flash from ISO using Yumi or universal something I once used or what you propose.
But on the last version it went directly to the flash and that's how I would like to do it. Unless I'm making it up and forgot how I did it previously :)
I see that K0LO is here :) :) the skilled surgeon who rescued my computer I think still in the wilders days!
Hello, 256egd:
You need to have a USB flash drive plugged in when starting the Bootable Rescue Media Builder application in order for it to show up in the list.
Mark, the USB flash is plugged in before I start AtI. Explorer can see it. ATI does not. Strange.
Aha, it was something wrong with a Sandisk cruzer flash. I normally have no issue with those.
Anyway, a junky Lexar flash just worked. Rescue made. Image using rescue is done, and even validated correctly (a rare occurence in ATI2016 for me).
Yup, check disk management to see if your Sandisk cruzer reports as a "removable" device or a "fixed" disk. There were a batch of Sandisks that were shipped as fixed disks (like an internal drive or a USB external hard drive) when Windows 8.0 first came out in an attempt to be compatible with Windows 8 "Windows 2 Go" feature.
Acronis will only allow you to create recover media on a removable disk so that you don't accidentally overwrite your main drive or other data drives.
Also, check to make sure that the Sandisk is formateed as FAT32 as that is another requirement. If it is "removable" and "FAT32" and not detected, do a full format on it (not just a quick one), make sure it's plugged in before you launch Acronis and can try to build it again and see how it goes after that.
Interesting. A can of worms.
How can you tell which is removeable and which is fixed?
I googled and can't find an answer.
Plugged in: Toshiba(ATIv11) and Lexar(ATI2016) have ATI boot rescue on them and work fine.
Sandisk isn't visible to ATI boot recovery maker.
aLL 3 are FAT32, slow format, and started before AtI client runs.
Device manager properties of all 3 are identical to what Sandisk displays.
Device manager list of 3 drives offers me no clue either.
I'm having a rough go here.
I'm getting a generic fail when trying to update my Acronis True Image 2016 to this build.
I wanted to reinstall from scratch, but add/remove programs says there is nothing to remove under my Acronis True Image 2016.
I found the KB article and it mentions first removing recovery manager, but the article doesn't match the options I get so I see no way to remove it.
In short,
New version - fails to install, old version non-removable from my PC. I'd really appreciate some help.
Oh - btw attempting to clone a drive also fails now so basically I have a very corrupt/nonfunctioning install that I can't remove or upgrade. I got a BSOD one time (when trying to clone my current boot drive to a same size drive I use as a backup) and after that it just fails and doesn't seem to attempt to run.
thank you,
Neil
How can you tell which is removeable and which is fixed?
I finally found the answer. Looked harder :) Clear as daylight. It's from properties as displayed by windows 10.
How can you tell which is removeable and which is fixed?
I finally found the answer. Looked harder :) Clear as daylight. It's from properties as displayed by windows 10.
Correct. You can also check in control panel >>> administrative tools >>> disk management which actually says if it's removable or not.
This morning I updated ATI 2016 to latest build. All seems to be working well so far.
Do I need to create a new Bootable Media Builder CD or will my prevously created CD work fine with the updated ATI?
Thanks
Jerry
I would in this case since it brings better driver support for eMMC flash drives and PCI NVME hard drives (which are becoming more common now). Acronis recommends that when you do upgrade, that you do create bootable media though. Typcially, it's only really needed for major version changes, but whenever updated drivers are included, that's another good reason to take advantage of the newer rescue media too.
Hi Steve,
One of the (for) most important supposed fixes in 2016-6581 (vs, I suppose any/all prior 2016 builds) was listed as:
** A backup fails if it contains a folder that has a space or a period symbols in its name
Can you shed any further light on this point? Not to put to fine a point on the question, but I'm just wondering on the following:
- In the context of this not, Can anyone detail what "Fails" means? Does a IMAGE backup "bomb", crash or report an error during the baclup, or just (e.g. SKIP) those folders, or (?) and, (then) just missing upon a Rescue?. I would suspect that a large(?) number of users might be caught by this and be relying on potential time bombs should disaster strike and all such defined "folders" be lost!
- Is this bug Win Ver related (e.g W7 vs W10)
-Lastly, might this apply to BOTH Image Backups made using the Windows application as well as those made under the Linux and or WinPE environments?
Ok, I know you are NOT Acronis, but perhaps have better connections than most of us, and in the past, my queries of such questions direct to Acronis have generally been met my little or no reliable answers...
Hope you can shed some light on this or perhaps reach out for the group
Thx
Bob
Bob, I would only be guessing in trying to answer your question about this particular issue listed as being resolved in build 6581 for ATIH 2016.
In terms of folders with spaces in their names, all current versions of Windows have this with the Program Files folders and I have not seen any problems being reported in these forums for any users having backups fail when backing up these folders.
The same applies to folders with a period character (.) in the name, this again is fairly common with applications that show their version level in the folder name - I can see examples of both these being used on my own system, i.e. Microsoft CAPICOM 2.1.0.2 folder in C:\Program Files\ path.
So there must be more to this issue than the simple description given in the new build release notes, i.e. perhaps it also involves the degree of folder nestings - some applications like Steam create very long folder paths? (Just my speculation!).
I have sent a PM to one of the Acronis Support engineers asking for a response to your question.
Hello Robert,
>A backup fails if it contains a folder that has a space or a period symbols in its name
We are going to change this line in the release notes to reflect the fact that space and period must be at the very end of folder`s name for the issue to reproduce.
Try opening a Windows Explorer and create a new folder with a space or period character at the end of the name, e.g. "New folder " or "New folder." You may be surprised that Windows Explorer will automatically trim the file name without notifying you about it. The resulting name will be "New folder", without the trailing space/period.
However, Windows still exposes a way to get space or period at the end of file/folder`s name although these are very rare situations. Acronis True Image 2016 on any Windows version was unable to handle them (backup interrupted when it got to the file/folder with the unusual name), now it can.
The issue affected only file/folder-level backups (to any destination) and disk/partition-level backup to Cloud. As the problem was in core backup/restore components, it reproduced both in Windows and under Linux and WinPE-based medias.
Disk/partition backups to any destination except Cloud were not affected by that issue.
Regards,
Slava
About installing 6581 on ATI 2016.
I had been running 6569 for more than a year when 6571 came along. It would not install on either of my Windows 10 machines. Support told me to uninstall/re-install but that I would have to manually restore each of my settings and backup chains after the installation (they would be lost in the re-install). So I postponed 6571. One day 6569 stopped sending emails. During the support process to resolve this problem, we wound up doing a "clean" uninstall and installed a fresh 6571. As previously promised, I had to re-build each of my backups manually and re-configure/rescue the previous backup chains on my backup media. Some of that is still a work in progress as the fathers and grandfathers cycle through.
My question: if I successfully install 6581 over 6571 will I again have to go through the manual reconfigure and rescue of my orphaned backup chains? If anyone who's done the update (or the upgrade to 2017) can give me the benefit of their experience, please reply.
The manual reconfigutation is necessary if you unistall ATI and run the cleanup tool - unistalling without running the cleanup tool leave the configuation files behind. You can install ATI 2017 without uninstalling ATI 2016. In most cases this goes without any problem. Occaisionaly things can go wrong - several times over the years I have lost my configuations (sometimes while testing beta ATI). This is unusual. Normally you just need to do a manual recongifuration - although once I had to do a unistall, run the cleanup tool, then reinstall.
The most reiable way of installing a new build or new version of ATI is to uninstall the existing version, reboot the PC, then install the new version. This process retains all the backup specifications.
This is the approach I take when I do not wish to run the risk of things going wrong - particualarly to the backup task specifications.
Ian
Thanks for quick response. It sounds like you've been down this path before. It's too bad there's no save/restore settings function to backup the backup tools. You've given me the confidence to try another update. I'll make sure that I'm backed up and try the install over old version first. If that goes amok I'll do the uninstall, reboot, install procedure. If all else fails, I've documented all the options for my existing backup cycles and I know all the steps to reconfigure/rescue my backup chains. Now all I need is a quiet evening to give it a try.
Jeff
Jeff, whilst there is no option in the ATIH GUI to backup your task settings, you can save the task configuration data by saving the C:\ProgramData\Acronis\TrueImageHome\Scripts folder and contents - this contains a set of .TIS files which contain that configuration data in an XML text format.
Now that's interesting. It's not as easy as a save/restore button, but it does document the settings. I'm not sure it would work as a restore function because it looks like a new GUID is saved each time options are updated since I have more GUID files than current backup cycles. I'd also expect the GUIDs to have a link in the service db which could get broken if I did a restore. It does give a historical record of settings, though. Thanks!
This might help me diagnose some other problems I've been having with reconfigured/rescued backup cycles. I've had unexpected file name changes occur in some backup cycles - screen shot attached. I'm guessing that each backup has a GUID somewhere in the metadata so that it doesn't matter what the actual filename is on backup media. The backup cycle still validates OK but the name change is disconcerting.
Also, I've had a couple of recovered backup cycles spontaneously begin spewing error messages in notifications and retrying at 10 minute intervals with failures indicating: "Cannot access the path: F:\Test Backups\Test backup to F_full_b7_s1_v1.tib" even though the file is visible in Windows Explorer and in the "Open Location" command from the GUI (same thing, actually) at the path indicated. The GUI clearly knows where the file is, but the backup service can't seem to find it. My pragmatic workaround is to re-define the "Custom Destination" to the identical path and the service picks it right up and completes the backup successfully, including validation. I think the metadata is getting goofed up, but finding the problem is a puzzle unsolved. I was going to open a thread on this one, but now I may dig a little deeper.
Just to keep this thread on message, I should probably post results after I've installed a new version. Metadata may still be goofed up and my problems above may persist.
Jeff
So my ATI build 6571 finally went belly up with the dreaded "Cannot create a database". I have downloaded 6581 and installed over 6571. My backup settings appear to have survived the install over, but all of my previous backup chains have been orphaned. The orphans appear to be intact and in their expected locations, but each of the backups in the GUI indicates "Last Backup: Never Performed". This may be an uncharacteristic outcome of an install over because of the database failure.
To complete the thread, my experience is that an update installed over an earlier version will retain the settings but orphan all existing backup chains.
I'm going to wait for tonight's daily backup to run and see if a new full or an incremental is created. That should indicate how much metadata has been retained, if any.
Hello Basementboy,
I've added your feedback to the existing feature request (Import\Export information about backup plans).
Thank you,
Hi Steve,
The NVMe support does not seem to work when booting from an updated USB recovery on my Dell XPS 15. It has a Toshiba thnsn51t02du7 NVMe boot disk. Are there any BIOS changes needed to make the disk visible to TI? Also SecureBoot is turned on. Could this be having an impact?
Thanks
Steve
Archway, most likely, your system came with a RAID setup in the bios SATA mode. The work-a-round is to temporarily switch to AHCI in the bios and then boot the recovery media... and upon restoring an image, go back into the bios and change back to RAID first.
Alternatively, build WinPE based recovery media - try out our MVP WinPE media builder tool as it greatly simplifies the process. You shouldn't need any other special drivers as we include the Intel Rapid Storage Technology (IRST) drivers by default in the MVP tool.
Links below for the PE builder tool as well as links to Microsoft ADK which needs to be installed first to create WinPE with Acronis True Image mediabuilder.
I've been using Acronis TrueImage for many years, on three 64-bit PC's with Win 8.1 . I bought the 2016 edition in March of this year. I just now (7 Dec 2016) downloaded the latest update and it appears to have installed correctly, however when I told it to do a simple backup of my C system drive (including Verify) to external HD drive E:\MyBackups folder (which the previous version regularly did with no problems), it insists that it completed the task in less than 2 seconds. I would have expected it to take 20-30 minutes. It didn't create any files in E:\MyBackups.
When I click on the Checkmark between SOURCE and DESTINATION, it says that the backup was successful, when it definitely wasn't.
I deleted that backup task and re-created another identical one, and get the same result. A CHKDSK of Drive E shows no problems. Drive E has about 600GB free, and the backup should be about 200GB in size.
Is this a biggie, or am I missing a simple fix? I'm using the same Vipre antivirus that has worked with TrueImage up til now.
I'm pretty busy today, and I'm not a happy camper.
OldCurmudgeon hard to say withotu more info to go on. Grab the logviewer app in this post (down below) and look at some of the recent service.logs with it. You can also post a few of them here for additional review. Hopefully they may shed some more light on the issue.
FYI, Acronis extended the support from 30 days to 2 years from the product release date, so that means you have full technical support with chat/email (I'd recommend chat if you go that route) to help identify the issue as well.
CHAT techincal support
Acronis Consumer Products Support Lifecycle
| Products | Release Date | Mainstream Support EOL | Extended Support EOL | Latest update |
|---|---|---|---|---|
| Acronis True Image 2017 | August 22, 2016 | TBD | TBD | # 5554 / # 5573, 2016-09-19 |
| Acronis True Image 2016 | August 17, 2015 | September, 2016 | September, 2017 | # 6571 / # 6077, June 02, 2016 |
| Acronis True Image 2015 | September 30, 2014 | October, 2015 | September, 2016 | # 6613, July 20, 2015 |
| Acronis True Image 2014 | August 28, 2013 | September, 2014 | September, 2015 | # 6688, August 20, 2014 |
| Acronis Disk Director 12 | May 27, 2014 | June 2015 | TBD | # 3270, December 29, 2015 |
| Acronis Disk Director 11 Home | April 05, 2010 | May 2015 | May, 2016 | # 2343, November 17, 2011 |
Build 6581 fails on attempting to clone my SSDD Win 10 system disk - BUT worked fine before I upgraded to 6581.
Is this a known issue? When will it be fixed??
Is there a work around??
Here is the problem in some detail:
58827: Acronis True Image 2017: Cloning Fails with "A specified authentication package is unknown"
Applies to:
Symptoms
- In Windows, you start Acronis True Image and select Clone Disk.
- Cloning fails with this error:
Failed to run the task.
Failed to execute the task script. 0x10002 Error #1364.
A specified authentication package is unknown 0xFFF0.
Error 0x00640067+0x0009FFFF
Cause
Issue in the product.
Solution
- Help us investigate the issue: send system report from the affected computer via Feedback form within product interface. Acronis developers need to analyze this diagnostic information to find the root cause of the issue and to release a fix for it. This article will be updated as soon as the issue is fixed.
Martyn, this topic was created purely to announce the availability of the new ATIH 2016 build 6581.
Please click on the New topic button at the top of the forum page and raise a separate topic for your issue with cloning. You should also open a support case directly with Acronis as per the information you posted above in the Solution section of the KB document: 58827: Acronis True Image 2017: Cloning Fails with "A specified authentication package is unknown"
Hi Steve,
Will do as suggested. BTW I have found an (untested) workaround. See my new post.
Martyn
I keep getting installation failed on the new upgrade. Knowedge Base says another program is still installing. I have no such installations running and have rebooted the PC. I checked MSIEXEC.exe and everything is fine. Could Kaspersky anti-virus block installation?
Gregory, welcome to these user forums.
I would suggest doing a clean install of the latest ATIH 2016 build 6581 update. To so uninstall the current software normally using the control panel, then download the Acronis Cleanup Tool (link in my signature below) and run this as Administrator then restart the system before attempting to reinstall ATIH 2016.
Note: using the cleanup tool will remove all your backup tasks and task history which you will need to recreate unless you make a copy of the C:\ProgramData\Acronis\TrueImageHome\Scripts folder contents - this folder holds the script .TIS files for each of your backup tasks.
Agree with the cleanup as well. The cleanup tool in Steve's signature and mine has the tool, but I've also put together some more outlined steps that may help. In particular, after cleaning up, check for leftover folders as described in the link below. A few people have reported that there are leftovers and when they try to delete it, they can't. Not sure why, but in those cases, they have to take ownsership of the folder first, then give themselves full access and then delete it. Those are usually the files that prevent the installation from being successful - happens rarely, but does seem to happen for a handful of people.
Bobbo's Cleanup tool recommendation: https://forum.acronis.com/forum/126092#comment-391779
If there are files leftover that you can't delete: Take Ownership of a File or Folder