Acronis TI 2016 will not stop running
My Acronis 2016 ran fine all during 2015, when I purchased it in September. Recently reviewed backups and noticed none were completed for 2016. I manually started the backup for files and folders with only 1.3 Gig database to see if it was working. Acronis started running and ran for hours. I tried to manually stop it but the system converted to a "processing" note and still kept running. My external hard drive does not show any response from Acronis, although acknowledged by the program. I checked the hard drives for errors on the computer and external drive and all are fine.
I went into Windows 7 control panel and hit "repair' for the Acronis program, said it was repaired and still it continues to run. Other than removing and reinstalling, anyone have the similar problem and if so, are there any magic fixes?
What are your backup schedules? Are you using non-stop backup - if so, Acronis will run all the time as that would be by design. I don't use non-stop backup though and haven't had an issue with this on the 3 Windows 10 x 64 systems that ATIH is installed on. If you have set backup scripts, Acronis will also have to run th e Acronis Sceduleer Helper Service at logon. You can disable this so it doesn't start automatically by using "msconfig" and disabling the service, but then of course, your scheduled backups wouldn't run as scheduled.
If you're not using Acronis Nonstop Backups, I'd also recommend going into computer managment / Services and Applications / Services. Look for "Acronis Nonstop Backup Service" , stop it, then change the startup type to "disabled" Once you do that, the nonstop backup service won't be able to run without you re-enabling it again... and if you aren't using the nonstop backup service, it will probably increase peformance and reliability in Acronis and give your system back a few extra background resources in the process.
Once you Proceed with a created back up task you should not attempt to stop or pause the task. Doing so will result in the behavior you describe. I suspect that had you been a bit more patient when you stopped the back up task and allowed TI to work through that request your outcome would have been much different. The actions you took likely introduced corruption to the backup database thus creating more issues which necessitated the uninstalls/reinstalls.
The reasons behind this are the processes used in the creation of a backup which are not True Image specific as all backup apps that I am familiar with use the same ones thus such corruption and behavior could be expected with those products as well.
Many thanks for the input as I thought stopping the process was not going to cause a problem. After the second re-install, I left everything run its course and all is now fine.