RealtimeSync is waking up Windows 8.1

[schildkroetewd]

Hi

Every time I have got RealtimeSync running, it keeps waking up my Windows when it falls asleep. I didn’t notice this behavior before version 7.0 of FreeFileSync. The thing is, once I close the notebook lid to stove it into my bag, when I take it out of it is running again.

When I query my Windows for the reason it woke, I receive the following output:

C:\Windows\system32>powercfg /lastwake
Wake History Count - 1
Wake History [0]
Wake Source Count - 1
Wake Source [0]
Type: Wake Timer
Owner: [PROCESS] \Device\HarddiskVolume4\Program Files\FreeFileSync\Bin\RealtimeSync_x64.exe
Owner Supplied Reason: generic

C:\Windows\system32>powercfg /waketimers
Timer set by [SERVICE] \Device\HarddiskVolume4\Windows\System32\svchost.exe (Sys
temEventsBroker) expires at 23:22:04 on 26.05.2015.
Reason: Windows will execute 'NT TASK\Microsoft\Windows\TaskScheduler\Regular Maintenance' scheduled task that requested waking the computer.

Timer set by [PROCESS] \Device\HarddiskVolume4\Program Files\FreeFileSync\Bin\RealtimeSync_x64.exe expires at 19:22:39 on 26.05.2015.
Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume4\Program Files\FreeFileSync\Bin\RealtimeSync_x64.exe expires at 19:22:39 on 26.05.2015.
Reason: generic

Is this behavior really intended? If it is, would it be possible to have a configuration item to disable it?

Thank you for your support.

Cheers

Daniel

[wm-sf]

Hi

Every time I have got RealtimeSync running, it keeps waking up my Windows when it falls asleep. I didn’t notice this behavior before version 7.0 of FreeFileSync. The thing is, once I close the notebook lid to stove it into my bag, when I take it out of it is running again.

When I query my Windows for the reason it woke, I receive the following output:

C:\Windows\system32>powercfg /lastwake
Wake History Count - 1
Wake History [0]
Wake Source Count - 1
Wake Source [0]
Type: Wake Timer
Owner: [PROCESS] \Device\HarddiskVolume4\Program Files\FreeFileSync\Bin\RealtimeSync_x64.exe
Owner Supplied Reason: generic

C:\Windows\system32>powercfg /waketimers
Timer set by [SERVICE] \Device\HarddiskVolume4\Windows\System32\svchost.exe (Sys
temEventsBroker) expires at 23:22:04 on 26.05.2015.
Reason: Windows will execute 'NT TASK\Microsoft\Windows\TaskScheduler\Regular Maintenance' scheduled task that requested waking the computer.

Timer set by [PROCESS] \Device\HarddiskVolume4\Program Files\FreeFileSync\Bin\RealtimeSync_x64.exe expires at 19:22:39 on 26.05.2015.
Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume4\Program Files\FreeFileSync\Bin\RealtimeSync_x64.exe expires at 19:22:39 on 26.05.2015.
Reason: generic

Is this behavior really intended? If it is, would it be possible to have a configuration item to disable it?

Thank you for your support.

Cheers

Daniel

Isn't FFS simply doing what you asked it to do and if you want something else you should say so ?

[Zenju]

There is no change between FFS 7.0 and earlier versions that could explain such a behavior and FFS does not set any wake timers. If you have steps how to reproduce this behavior, I can try to find out what is going on.

[chmark]

There is no change between FFS 7.0 and earlier versions that could explain such a behavior and FFS does not set any wake timers. If you have steps how to reproduce this behavior, I can try to find out what is going on.

I second Rotus Natter's problem. Same behavior on a Win7 64-bit machine, same info from powercfg. Really annoying, otherwise a superb software!
More info:
ffs_batch file attached. Both source and target are on encrypted drives (Diskcryptor) if that can be significant.

[schildkroetewd]

Thank you for your response. I attached 3 files I am using FFS with.

I did not notice this behavior before version 7.0 but i am pretty sure I left out version 6.15, so I cannot tell you whether this behavior has been introduced with 7 or before.

I am using FFS to synchronize a local with bitlocker encrypted drive and a CIFS Network share.

[wm-sf]

encrypted drives is the obvious common denominator

[chmark]

encrypted drives is the obvious common denominator

and of course FFS... :)

[Zenju]

and of course FFS... :)

novice users? SCNR :)

[Zenju]

boost is using "CreateWaitableTimer". I bet this is caused by a boost bug or even worse, "feature". Continuing investigation...

[Zenju]

I am not able to reproduce the problem on my Windows 7 system, but it is reproducible in your test cases, right? In this case I could create a test version with a patched boost build and see if this solves the wake up problem.

[chmark]

It's easy enough to test if You make a patched version. Let me know when and where.
(and Yes, I'm a novice FFS user...)

[Zenju]

Here's the new version with patched boost, which should not set wake timers anymore:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_7.1_beta_Windows_Setup.exe]

[chmark]

My problem seems to be fixed. Win7 64 PC is sleeping in peace, no timers active anymore:

C:\>powercfg /waketimers
There are no active wake timers in the system.

Thanks Zenju!

[schildkroetewd]

Here's the new version with patched boost, which should not set wake timers anymore:
[404, Invalid URL: https://freefilesync.org/FreeFileSync_7.1_beta_Windows_Setup.exe]

Hi Zenju

I can tell you too, that there are no more wake timers when running RealTimeSync. So thank you very much for this quick fix.