CE waking Win 7 computer from sleep

  • 1
  • Problem
  • Updated 4 years ago
I just upgraded from an old CE version (4.5 ?) to 7.2.0. Now I notice that my computer is automatically waking from sleep about a minute after I put it sleep. This has happened several times. I am running Windows 7. The event viewer indicates that the WakeTimerOwner that is brining the device out of sleep is \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService. Is this a known problem? Is there anything I can do to circumvent it?
Photo of TC

TC

  • 9 Posts
  • 4 Reply Likes

Posted 4 years ago

  • 1
Photo of Gerry Simmons

Gerry Simmons

  • 36 Posts
  • 5 Reply Likes
You should be able to go into Win 7 Power Settings and change what is allowed to wake the system - like Ethernet Traffic. Check there. There really shouldn't be anything in S/W that can do this, only hardware related things interrupting the system's sleep.
(Edited)
Photo of TC

TC

  • 9 Posts
  • 4 Reply Likes
Thanks, Gerry. That pointed me in the right direction to mitigate this. I'm changing Power Options->Sleep->Allow wake timers->Plugged in: Disable.

A little more googling led me to run the following from the command line:

C:\Windows\system32>powercfg -waketimers
Timer set by [SERVICE] \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService.exe (CovenantEyesCommService) ex
pires at 1:38:21 PM on 9/1/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService.exe expires at 1:37:12 PM on 9/1
/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyes.exe expires at 1:36:30 PM on 9/1/2016.
  Reason: generic

Timer set by [SERVICE] \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService.exe (CovenantEyesCommService) ex
pires at 1:38:16 PM on 9/1/2016.
  Reason: generic

Timer set by [SERVICE] \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService.exe (CovenantEyesCommService) ex
pires at 1:36:46 PM on 9/1/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyes.exe expires at 1:36:26 PM on 9/1/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService.exe expires at 1:36:25 PM on 9/1
/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyes.exe expires at 1:36:25 PM on 9/1/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyesCommService.exe expires at 1:36:25 PM on 9/1
/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyes.exe expires at 1:36:25 PM on 9/1/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyes.exe expires at 1:36:25 PM on 9/1/2016.
  Reason: generic

Timer set by [PROCESS] \Device\HarddiskVolume1\Program Files\CE\CovenantEyes.exe expires at 1:36:25 PM on 9/1/2016.
  Reason: generic

I am curious as to why exactly CE needs all these timers... Perhaps a developer can chime in?
Photo of hoops

hoops

  • 1 Post
  • 0 Reply Likes
I will just add that I too have had the exact same issue as the original poster. Fortunately, this thread provided me with a suitable workaround. Thanks.