[RESOLVED] Operations are in progress, please wait
I have a scheduled backup every morning at 2:00 AM. If my computer is off during that time, which is rare, I get this message the next time I log on and shutdown. I have looked everywhere for a solution, but cannot find one for True Image 2013. It is rather annoying, and risky, for me to continue to shut down the PC because I cannot get control of it.
I am running Windows 7 Ultimate. Please let me know if you need further information.
Issue resolved here.
No. It basically says please wait until the operations are done. If the scheduled backup is missed, True Image tries to perform the backup and if I don't manually shut the process down and I shut down Windows, I get this message and there it stays.
I am using Windows 7 Ultimate 64 bit SP1
This is normal behavior, and the computer should shut down. Many users report that the computer actually does not shutdown. Some users have set up the backup to happen only when the computer is idle, so when a backup is missed, it has to run, but has to wait until the computer is idle and that might until it shuts down.
I personally avoid this case by disabling all advanced options in the backup or validation scheduler.
I have 2 computers running W7 and TI 2013 and both have the problem of not shutting down because of the Operations in Process message. Yesterday, I did the 2nd Tuesday Windows Update and got the message when the update said to restart the computer. I always wonder if the update actually got installed correctly and it seems to make no difference on the time of day when it happens.
I've tried everything people have mentioned in these forums and nothing works for me. I don't understand why Acronis can't fix it after all this time. I'm ready to go to another backup app.
I just installed it, too, so we'll see if it works. I thought it was interesting, after downloading and starting the install, it hung up with the message "can't install as operations are in process."
I had to open msconfig, stop all Acronis processes and restart the computer, after which the install went properly.
I guess it is 'fingers crossed' time. I hate this sort of error. No one seems to have a definitive answer about what triggers it or what can cure it for sure. All I have seen is 'try this.' We will never know for absolute certain that it is no longer a problem simply because it doesn't happen. The only thing we will be absolutely certain of is that it still is a problem if and when it does happen again.