Skip to main content

Scheduled Backup no longer shuts down PC

Thread solved

Same Backup task been running every night for months, now does not shut down after backing up until I open ACPHO which has the 'Waiting for Shutdown' countdown box. I know I could use a Post command, but any ideas as to what might be happening anyone?
 

ACPHO Build 40173 on Win 11 21H2

0 Users found this helpful

Have you checked the log files associated with the backup task?

Yes, I have, and there is nothing untoward save for the greater than normal duration between 'Operation: Backup" and "Shutdown attempt (by scheduler)" lines.  It is still the scheduler that shuts down the machine, but it doesn't seem to come to life until ACPHO is active.  

If nothing has changed on the Win 11 side, has this backup been successful since the new #40173 ACPHO build was installed or did this issue start after the update?

There's quite a lot changed with the Windows installation now, but this problem appeared long before, and as far as I can remember just after the update to 40173.

Also seeing an error in Event Log relating to Acronis Scheduler:
Scheduler failed to run task with GUID '1A7779C8-8294-4740-8160-E7D888EB3738' because of error 3 (The system cannot find the path specified)

Error logged at 10:52 but there is no task scheduled for 10:52 - which log would I find this in?

Now on Windows 22H2 with a new user profile in response to Windows issue. Thinking reinstalling ACPHO might be the best option.

 

I get the scheduler failure after e very update. So I decided to always use the cleanup tool before updating to a new Version. All given hints with “taskzap” and so on are useless. 
Maybe you could try the following: deinstall atih, then use the cleanup Tool. Afterwards create the Backup Job new  

I hope this will help you I don’t trust Acronis any longer and switched to macrium  

 

I would suggest trying the Acronis Scheduler Manager tool before doing a reinstall of ACPHO (link in my signature).

Make a note of any of your scheduled tasks then run the tool to do a 'task zap' which will clean out all obsolete schedule entries etc which should address the issue from the event log.

After running the tool, reset the schedules for your task.

Thanks Steve, task zap, then reinstated schedules, now all good.