Direkt zum Inhalt

"Operations are in progress" at shutdown

Thread needs solution

Over the last few weeks I have had this message appear at shutdown when I turn off my machine.

The hard drive is definitely showing some vigorous activity, so I leave it to continue these 'operations' over night.

When I get up in the morning the same message is on the screen, yet the hard drive activity is less vigorous.

The only way I have to use my computer is to press the restart button and wait for my machine to go through its diagnostic cycle.

I had the same problem with previous versions of Acronis True image and now the same thing is happening with this version - I only upgraded in the vain hope that this bug was resolved.

The best part is that my 'support entitlement' seems to have expired!

Has anyone manage to solve this issue?

0 Users found this helpful

Graham,

Some users of 2011 have been plagued with the issue and no recommendation from other users seemed to fix it.

This message shows up when ATI is running a task that is not finished (a backup or a validation).

My take on it didn't solve it for some of the users, but feel free to try. My assumption is that ATI is set to run a backup or a validation at shutdown, and/or you have elected to run a validation or backup only when the computer is idle. In the latter case, it is possible that ATI never finds the computer idle and waits until shutdown to finally run the waiting task.

I would:
- uninstall ATI, reboot, and create new tasks,
- for each task, uncheck all options in the scheduler setup, advanced settings section.

I had the same issue with ATI 2011 as well.
The support team told me to do the same thing as you suggested (uninstall, reinstall, reconfigure backups).
Although I am happy to do this if it permanently resolves the issues, my patience is wearing thin since reconfiguring causes me a lot of pain, plus the same issue occurred again in the new 2012 version.

So to be honest, I'm more likely to buy another piece of software - I work for Symantec, so I might give Norton Ghost a whirl instead.

On another note, it took me three hours to upgrade to the latest build. The installer kept failing and when it did eventually install successfully the software insisted I should install the new version...again. The UI of ATI looks great in 2012, but there are still some significant issues with the software itself.

Graham

Pat L wrote:

Graham,

Some users of 2011 have been plagued with the issue and no recommendation from other users seemed to fix it.

This message shows up when ATI is running a task that is not finished (a backup or a validation).

My take on it didn't solve it for some of the users, but feel free to try. My assumption is that ATI is set to run a backup or a validation at shutdown, and/or you have elected to run a validation or backup only when the computer is idle. In the latter case, it is possible that ATI never finds the computer idle and waits until shutdown to finally run the waiting task.

I would:
- uninstall ATI, reboot, and create new tasks,
- for each task, uncheck all options in the scheduler setup, advanced settings section.

If you are doing backups prior to this problem, you might want to consider trying this solution. It may or may not work. No guarantees. I use it for all my backups on my Win7 Asus Laptop.

I only have ATI2010 but it exhibits this problem when a backup error occurs and when ATI is waiting for a user response. I have this exact problem at the moment because my backup target has a hardware failure and no longer exists on the network. When ATI attempts to run, a file operation error pops up briefly, and if I shutdown the PC it show Operations In Progress infinitely with continuous hard disk activity. If prior to shutting down I run Acronis then I see a "cancel/retry" option. If I cancel and make sure no backup tasks are active then the PC shuts down correctly.

Have you tried changing the task to "not scheduled". If the target does not exist, why run the backup?--or maybe I am not understanding correctly. If you have a replacement disk, then create a new task pointing to the new disk.

Yup thx, I'm just responding to the initial poster who had the problem; you get the same thing happen when the target disk is full.