Acronis True Image 2016 Errors Out with “Unable to create volume snapshot”
This was an issue in TI 2015 and was corrected by an update. My TI 2015 was working just fine util I upgraded to TI 2016. Then I got this error. I spent over an hour on chat with ACR Support. I was able to find a workaround for now, by going to "Backup source -> Full partition list" and unchecking the EFI and recovery partitions. For the life of me, I don't understand why companies release buggy builds to the public and expect us to pay for them, especially this one, because it was already corrected in TI 2015. BTW, the original KB was 48686 for TI 2015. Don't waste your time with that article talking about the MS VSS service, because it has nothing to do with it and doesn't fix a thing.
I had this issue under ATI 2015 (second most recent build). It only related to one backup task (backup to Acronis Cloud). Acronis tech staff suggested my be disk errors on the drive being backed up. I checked and there were none; I could backup to local HDD without any issues. I successfully created a new backup task to backup to cloud and created new backup. A few days later the problematic backup completed without issue (not sure if that was after loading the latest version of ATI 2015). I was running Win Pro 8.1 64 at the time.
If I recall correctly there is another report of this issue under ATI 2016 on the ATI 2016 beta forum.
So, may I suggest you create a new backup task and see what happens when you try to run it.
Ian
Guys. I have already commented that this version should not have been release. It is flawed and full of untested bugs. Just how can you trust a program in this condition with real data.
Until then i would not pay for it. Yes i will test it but only for testing data. Otherwise i will stick with 2015 version
For those that want free software that works (Acronis sorry to say this), then try a backup package called "Reflect"
Not as good as Acronis 2015, but at least it works without having to download this that and the other if using windows 10
I guess hope "springs eternal"! I keep hoping Acronis will learn from their past mistakes! As a customer for 8 years, I should have known better.
Hi Everyone,
please download and install the new build we've released today.
If the problem persists, please contact our support for investigation: http://www.acronis.com/support/contact-us.html
Thank you,
Same problem recovery partition cannot recognized (NONE) with Acronis True Image 2016 build 5576
The none refers to the formatting of the partition, not that there isn't one. There is and it is 0.4GB or 450MB in size.
Actually i was using ATI 2015 and i installed 2016 build 5576 everything was normal. NONE parition recognized as NTFS. Then i activated Acronis Startup Recovery Manager and Ntfs partition changed as NONE and now i cant take a backup on this partition. This partition isn t empty. From another programme i atteched a picture.
Updated to true Image 2016 AND latest hot fix from 2 days ago. Windows 10 pro. 8mg ram. Cannot backup whole PC - keep getting "Cannot create volume snapshot". CAN backup documents, picture files, etc. Just not whole PC. Am backing up to external USB Drive. Glad this was "fixed" in 2015 - but not so much in 2016.
Edward,
How much total data is your entire PC backup? How many disks are there that would be included in this backup? What is the total capacity of your C: system disk and how much available space is on that
disk?
Grrr!! what are Acronis playing at? I had a problem with 2015 re not recognizing external USB drive from Boot CD, which took nearly a year to fix, when eventually they fixed it, they released version 2016.
So i moved to ver 2016 and Now i cant do a backup to my Seagate 1tb USB drive, as i get the following error - "Unable to Create a Volume Snapshot" This also creates the same error when trying to backup to a hard disk partition - so its not the USB drives fault - its Acronis's YET AGAIN!
Going back to Version 2015 until they fix it!
Same problem with 2016 (build 5620). Never had any problems with previous versions. Can back up my D: drive (Data); but not C: drive (System). It seems they don't have a solution!
To go back to 2015 I'll have to uninstall 2016 first.
Hey, Thylacine, your picture looks like a koala rather than a Thylacine! I doubt that they could climb trees ... but then, anything is possible in the wilds of Tasmania.
Ian
Hello,
Acronis True Image 2016 NL build 5620
Operates Windows 10 32 Bits
“Unable to create volume snapshot” to USB harddrive or an internal extra harddrive.
It only creates volume to the cloud but that takes 11 Hours so that is not an option.
What is the solution?
Acronis True image 2013 works fine.
Hi IanL-S. Hope you prefer the new avatar. I liked the Koala because he seemed so laid back and content.
Hi IanL-S. Hope you prefer the new avatar. I liked the Koala because he seemed so laid back and content.
Yes, that is true about the 'laid back and content'. Could it be something to do with not being extinct? (I know for time to time there are unconfirmed reports of seeing one. If there are any left they would be vigilant rather than laid back. I have definitely not see one on any of my numerous bush-walking expeditions to Tasmania or in the 6 years I lived there.)
Ian
Hi All,
I could not complete a partition image with Build 5620. The program just froze up, while the operating system was humming along. Going back to previous Build 5586.
Hi All,
I could not complete a partition image with Build 5620. The program just froze up, while the operating system was humming along. Going back to previous Build 5586.
Did you tried again or only once ?
Hi All,
I could not complete a partition image with Build 5620. The program just froze up, while the operating system was humming along. Going back to previous Build 5586.
Did you tried again or only once ?
Hi akshay_ht,
Since using Acronis True Image 2016 Build 5586 and have it complete the Backup, just running it once, I tried it just once as well, also with Build 5620.
Like when I installed Build 5586, I manually uninstalled Build 5586, first. Rebooted and then I installed Build 5620, so it a Clean install.
Build 5586, worked fine, so I would suspect that Build 5620 would work, but did not. The program just sat there The Computer was Lockdown, meaning created a Firewall Rule to block all Inbound and Outbound communication and disabled Real-Time Windows Defender scanning.
The program was activated.
Hi again,
I was having a few issues with my PC, and ended up resetting Windows 10 which lost me most of my apps. Then, after reinstalling True Image 2016, I was able to complete the backups with no problems!
I also invested in wiping my old upgraded Win 10 installation in favor of a clean install. Acronis 2016 works as advertised
I have installed my WIN10 64Bit on a fresh SSD and have the same Issues.
Hi All,
I am always thinking. and I found a major bug in Windows 10 Pro Insider Preview 64-Bit Build 10532. When you want to check the partition for errors, it states that you don't need to check the drive for errors, because it found none. When you manually force it to check for errors, it found the File System had errors and recommends that you Schedule Check Disk at boot. Other times, it doesn't find any errors.
Best to error on the side of caution. Run Check Disk, before creating a Drive or Partition Image.
I can confirm, if i disable the Recovery Partition in the Backup, it worked.
But i'am confused, the UEFI Partition ist also without an Filesystem (NONE in Filemanager) but it can included in the backup.
Hi Karl Heinz,
thank you for the info, there is more interesting stuff.
Here is one more potential cause for this problem.
I had created an NTFS Volume mount point at C:\temp pointing at an older, smaller SSD.
Once this volume was deleted and the C:\temp shortcut replaced with an actual folder the backup proceeded without the "unable to create volume snapshot" error occurring.
Here is an article from Microsoft about these mount points.
https://technet.microsoft.com/en-us/library/cc938934.aspx?f=255&MSPPErr…