[QUOTE=..............3. Another user told us we can just change properties in Windows task manager to "Run only when user is online"
I'm going to check out 1 and try 3 I'll post back tomorrow to late for tonight.[/QUOTE]
This DID work for me. Good luck!
Last edited by Clintlgm; 04 Aug 2016 at 21:01.
Glad to report that "Run only when user is logged on" worked for me too, this seems to be the solution.
Still not getting the proper behaviour. I let it wake from sleep to do an incremental backup at 7:00am, after which is should shut itself down after 30min being idle. I checked on it around 11am, it was still awake and it had done two incremental jobs in a row (first one 200 MB, second one 8 MB). So I disabled "Wake the computer to run this task" just now, and just when I'm typing this, it triggered the incremental job again. Maybe the "run immediately when missed" trigger isn't working properly or something. Anyone else experiencing this?
This is odd: I have a system with W10v1607 (14393.10) that's scheduled to run an image every Sunday at 9am, with a "run on next boot if missed". This image did indeed run this morning, and I have not made any modifications to it.
KB update at Macrium UK - Windows 10 Aniversary Update issues - KnowledgeBase - Macrium Reflect Knowledgebase
New Update!!!
Macrium Reflect v6.2.1495
Solved New Macrium Reflect Update - Windows 10 Forums
I downloaded an update for Macrium reflect this morning which fixed the scheduling problem/s.
So Cliff, looks to me like this (but want your opinion):
I have 2 systems not yet updated to v1607, and 1 system on v1607, (but the scheduled backup still ran - figure that one out!).
I have not made any of the interim fixes. Backups are scheduled to run on the 15th, as usual.
So, if I just update Macrium and make no changes to my schedules, they will still run as if nothing every happened, right?
Thanks.
Quote