Salta al contenuto principale

'Calculating Time Remaining' runs for hours in TI 2016

Thread needs solution

Upgraded from TI 2014 to free 2016. Calculating Time Remaining runs for hours. Worked perfectly in TI 2014.

Windows 10 64bit

0 Users found this helpful

During backup process it happens in early minutes of backup process.
But after initial load it will reduce time considerably.
It depends also on how large is backup size.

The accuracy of the % done, or time remaining, of any program is usually inaccurate at the beginning. It is most accurate when it reaches %100.

Peter Ledden wrote:
Upgraded from TI 2014 to free 2016. Calculating Time Remaining runs for hours. Worked perfectly in TI 2014.

Windows 10 64bit

If you upgraded in place, I recommend you start new backup tasks. Note that I successfully upgraded to ATI 2016 from 2014 and 2015 in place, and continued existing backups without a serious hitch. Only on one computer I had to uninstall and reinstall and start new backup tasks because of some unknown stored credential issue. On another computer I had to uninstall, reinstall because the (annoying) login at startup wouldn't log me in...

Same problem here, with a fresh install on a vanilla notebook. It never got beyond the "calculating time" until I rebooted....

Peter, if I understand you correctly, when you start a backup task, you see the message "Calculating time remaining...", and the backup never actually finishes? May I ask you if the problem is still there, or is it gone? What are you backing up? (Entire PC / separate partitions / files ?) How large is the data that you are backing up? Does this happen with all new backup tasks?

Thomas, am I right in understanding that everything is working fine now?

Dmitry,

I believe that one of the problems with an in place upgrade to a new version of the product is that there is no requirement for the machine to be rebooted after the upgrade is performed and this is causing various problems for users. I think this might have been an oversight in development of the product. I have had one instance of the application not behaving as expected when upgrading. That occurred when upgrade from the first release to the HotFix 1. Issues were fixed upon machine shutdown and restart.

Now I no longer run an upgrade. I always do a complete uninstall and reinstall with a machine shutdown and restart afterwards and so far that has proven bullet proof. I am running 4 different installs with which I do this just for your info.

Enchantech,
what do you do with new builds? Do you also cold boot then? Do you run a backup on the system partition before you apply a new build? Do you allow each new build to install, or do you wait and observe whether there's problems coming up? I am asking, because if you have machines running real world stuff, you don't want all these interruptions and that feeling of uncertainty that it might be that very build that blows everything. That's why I am so extremely disappointed that we do not get the according information with TI builds whereupon on could decide to apply / install or rather refrain from doing so this time.

Same problem, Win7, fresh install, goes immediately to same backup process (C: to E:) and stays in "calculating time remaining". Have let it run as long as 26 hours with no change. "stop" doesnt stop it, stop in task manager does. I've tried multiple times, rebooted, no joy. C: is a 250GB SSD, E a 2TB HDD with plenty of space. I have alternate external drives I could back up to if that is potentially the issue. Suggestions?

Thanks

Chris

 

Wireloose wrote:

Same problem, Win7, fresh install, goes immediately to same backup process (C: to E:) and stays in "calculating time remaining". Have let it run as long as 26 hours with no change. "stop" doesnt stop it, stop in task manager does. I've tried multiple times, rebooted, no joy. C: is a 250GB SSD, E a 2TB HDD with plenty of space. I have alternate external drives I could back up to if that is potentially the issue. Suggestions?

Thanks

Chris

 

 

Chris,

I'm in a similar situation as you that I describe in:  http://forum.acronis.com/forum/108631