Scheduler2 vs. Windows Task Manager?
I am curious if anyone know the reason Acronis maintains their own scheduling overhead, vs. using Windows Task Manager? I have been unable to find anything on the Acronis site(s) explaining the reasoning.
Maybe cause they port Scheduler2 to different platforms?
I ran onto a problem last summer with a new Dell laptop. I have some older systems that utilize the sleep (S3) method of wake-up and Acronis works fine with this method. But newer Dell system BIOS and Windows have moved to something Microsoft labels 'Modern Standby'.
Search Google for ‘windows modern standby vs s3’ if not familiar. (Sorry, the forum prevented me from posting the url link.)
I found that Acronis 2020 could not wake the laptop and run jobs, since the computer was not really sleeping? If the laptop happened to be running background tasks as described in the link above, my Acronis jobs would run too. But if the laptop/NIC was in standby, Acronis could not get the laptop out of standby to run. Of course, Windows Task Manager could run jobs regardless of the Modern Standby state.
After much searching, I found a registry hack that restored the laptop to the old (S3) method, but I do not know if that will be grandfathered in Windows builds forever??? If this setting is revealed in some way in Windows Settings, I have been unable to locate it. Anyone?
Many are complaining about Acronis app bloat and this is an area where they might cleanup some unnecessary code/services and use Task Scheduler?
Thanks for any insight


- Log in to post comments

Thanks Steve,
Yes, I did have to add the wake timers via a reg. hack to the Dell, but that had no bearing on whether modern standby could wake the computer once set. With the S3 wake approach, I have no problems with the new Dell at this point.
But I am wondering how many people have run into the modern standby issue with new systems? Maybe not too many people use sleep as I do? I, like you, have systems that do not support modern standby, and I am ok with that given my experience with the new Dell. But, this issue may become more important to Acronis users in the future, and the need for a Windows Task Manager implementation.
When I first experienced the Dell wake issues I contacted Acronis support. They claimed to not know anything about modern standby and indicated they would notify the proper group(s). But the ticket was closed of course, so no further follow-up occurred, so I have no idea how far my query progressed.
- Log in to post comments

I would hope that the Acronis developers are aware of modern standby and any associated issues that this may have on the Acronis Scheduler process / service. I suspect that they don't consider this to be high priority due to the limited take up of modern standby, especially if they are not seeing significant feedback from users about issues related to this area.
- Log in to post comments

Link test...
If this works, then maybe it is related to creating a new topic and the url link fails?
- Log in to post comments