ATI Home 2013 Unable to create volume snapshot

At this point, I would try to run the TI Cleanup utility which includes some special text instrructions in section 6 of the cleanup utility.

Before doing anything more, I would boot from one of your 2010 or 2013 user created CD's,
and perform a new full and complete backup before making any further changes.

Problem solved. It was caused by my NOT changing ATI Home's scripts when I added an SSD to my system over a year ago. I will explain the events and solution below in case someone else receives the misleading error.

Initially my system used a single 1 TB HDD without partitions and ATI 8.0 worked fine.

Then I split the HDD into C and D partitions and ATI 10, 11, 2009 Home, and Home 2010 worked fine.

Last year I added an SSD as C and the HDD became F (old C) and D BUT I did not modify Home 2010 scripts. NO errors were reported even though ATI did NOT make usable images

Now I finally upgraded to ATI 2013, wrote a script similar to the one used for 2010, and receive the "volume snapshot" error.

The solution is to use two scripts since there are two devices, SSD and HDD, to image. The ATI program appears to know that one script for two devices would result in not being able to use the image to restore the system.

Darn it.

I posted too soon.

When this problem started, i. e. trying to image C and D with one script, it gave a "snapshot" error for D.

I am now able to image D only with one script BUT an identical script for C only produces the "snapshot" error.

A sfc /scannow produced no changes and the error for C remains

Very confusing.

Create two new tasks.
One task for the Disk image to include both partitions.
Figure 4 and 5 at this link
https://forum.acronis.com/forum/28705
-----------------------------------
Another new image but this to be a partition image with only the C partition.
Figure 3 at the preceding link.

Let me know the results.
If you have any more failures, try checking the disk for file errors
chkdsk c: /f

All scripts are identical except for designation of partitions: C is Boot SSD, D and F are partitions on HDD

1. Already did CHKDSK D: /r and CHKDSK C: /r  with no changes made.
   
2. Tried most scripts with VSS Automatic, Manual, and Disabled.
   
3. Repair install of ATI no help.
   
4. Malwarebytes is installed but NOT running.
   
5. Script image D only works without error
   
6. Script image C only gives "snapshot" error
7. Script image C and F gives "snapshot" error on F.
   
8. Script image F only works without error
9. Script image D and F works without error

If you have any applications running even in background while attempting backup they have the potential to cause VSS errors. Exchange, SQL Server, and Quick books are known to not register themselves as writers and if running will cause VSS to fail.

Thanks for taking the time to make suggestions.

But then why would the scripts for D and F singly and D and F together work but not C by itself under the same circumstances.?

C is SSD Boot while D and F are the only partitions on a HDD.

I will now try to run ATI:

1. With everything I can manually shut down including my internet connection
   
2. In Safe mode
   

Any files that need Windows to run will reside and run on C even if the application is installed on D or F.

I had similar problems (TI 2014 won't create an image of my system partition) trying to create images of a partition on an SSD but have not quite experienced the inconsistencies that you are experiencing.

After trying pretty much everything you did, I was told by Tech Support to try running a trial version of TI 2015. That worked.

So there was nothing wrong with my disks/partitions. And there is likely nothing wrong with yours either - just some other-wise valid characteristic that TI versions before a recent TI 2015 build cannot handle - at least that's my guess.

I was also told that my problem must be some sort of low level driver problem. I don't know about that. It is reminiscent of some (so-called driver) problems I had many years ago that were ultimately fixed in a (year and a half) later build of a new version.

I never did find out what TI 2014 thought was wrong with my partition.

A faster way, for me, of determining whether I was going to have a problem, was to check View current state of your disks found with, or in, Drive Cleanser in TI 2014. If my backups failed (or were going to fail) then the particular partition had a little red X on it. If not, it didn't.

In my case TI 2014 also failed, in the same way, to create an image backup when trying to back up using an external Rescue Media Disk, so no Windows OS interference on which to blame the failure. My guess is that this too would fail for you just as your backup from within Windows has failed.

Good luck.

Unless something else happens this will be my last report on my situation.

Every night an unattended overnight batch is run for temp cleaning, data backup, and "anti" scans. ATI runs Saturdays about 2 AM.

This week I had a problem that required reload of C (SSD) from the previous image made by 2010 on Feb. 7.

Last nights run, Feb. 14, using ONE script with ATI 2010 completed OK imaging C (SSD) and D (part of HDD).

Here is my thinking on things I have learned as I worked thru this:

On using 2010:

1. Using ATI Reload is confusing because it does not accept my numerical keypad inputs, only main keyboard.
2. One image script including BOTH C (SSD) and D (part of HDD) works OK which means the disks are without errors.
   
3. ATI reload can select just C BUT the MBR must be included.
   

I have decided to stay with 2010 and NOT try 2013 again.

If I upgrade to Win 8, 10, or beyond then I would probably have to upgrade to the then current ATI.