mikehayton:

I'd leave mcupdate & mcupdate_scheduled disabled for now, and now go into the services and stop the ehrecvr service. Before you put the machine to sleep ensure from task manager (processes tab, showing all processes) that ehrecvr.exe is stopped and mcglidhost.exe isnt running (it should exit when ehrecvr.exe terminates)

If it still wakes at 3am, I'd then try stopping and marking the disabled, the following services: ehrecvr, ehsched, ehstart

Some progress to report.  Last night with the ehRecvr stopped and mcglidhost.exe not running, I only had one RTC wakeup (at 05:51), instead of two (at 03:00 and 05:51).  I have to conclude that ehRecvr or mcglidhost are responsible for the 03:00 wakeup.  

Tonight I'll also stop and disable ehSched and ehStart before sleeping to see if this eliminates the 05:51 wakeup.

@Mike - Thanks for your suggestions.  Hopefully this procedure is required for further diagnostics, as I don't think it's viable as a workaround.

 

it may be a stop gap measure if a bat or cmd file is scripted to stop these processes before hibernate and to resume them afterwards using something like hibernatetrigger

Pixelz:

mikehayton:

I'd leave mcupdate & mcupdate_scheduled disabled for now, and now go into the services and stop the ehrecvr service. Before you put the machine to sleep ensure from task manager (processes tab, showing all processes) that ehrecvr.exe is stopped and mcglidhost.exe isnt running (it should exit when ehrecvr.exe terminates)

If it still wakes at 3am, I'd then try stopping and marking the disabled, the following services: ehrecvr, ehsched, ehstart

Some progress to report.  Last night with the ehRecvr stopped and mcglidhost.exe not running, I only had one RTC wakeup (at 05:51), instead of two (at 03:00 and 05:51).  I have to conclude that ehRecvr or mcglidhost are responsible for the 03:00 wakeup.  

Tonight I'll also stop and disable ehSched and ehStart before sleeping to see if this eliminates the 05:51 wakeup.

@Mike - Thanks for your suggestions.  Hopefully this procedure is required for further diagnostics, as I don't think it's viable as a workaround.

I agree about the above not being a workable solution. From your comments, the 3am wake up time is the periodic scanning kicking. The person I want to talk to about this is on vacation at the moment and back next week. So I wont have any further information on this 3am wake up time until sometime next week.

Can we continue to try and see what the 05:51am wake up is?

 

If you disable the:

• mcudpate
• mcupdate_schedule

tasks in the task scheduler

stop and disable the

• ehrecvr
• ehsched
• ehstart

services

kill the ehtray process

There there's really nothing of Media Center running and if you still get a 5:51am wake up, then I suspect another application.

 

mikehayton:

From your comments, the 3am wake up time is the periodic scanning kicking.

is that the same as promiscuous scanning? something in the back of my mind is telling me about a reg setting that would turn that off from the Australian community...I just cant put my finger on it at the moment.

@mike

ehRecvr, ehSched, ehStart services all stopped.  ehTray killed.  ehShell exited.  mcupdate and mcupdate_scheduled disabled.  It's 01:30 local time and I'm putting the OS to sleep.  I'll post the results tomorrow.

@vengance

I believe you're thinking of opportunistic scanning which takes place whenever you change DVB-T channels to a different MUX.

I installed TV Pack on my notebook so I could watch the shows recorded on my media center.  Dead battery several morninings in a row, and I remembered having this problem when I configured VMC on it.  Went in an change VMC to not do updates, blah, blah, blah.

Still had the problem.  Then I went into the scheduler and disabled everything that had "allow wake pc set", which if memory serves me right was mcupdate and TMN?  So far so good and it hasn't woken up since.  Not sure if its different between a plugged in computer and notebook, but I'm happy the problem went away.

@daler

I think your wakeups were genuine mcupdate events (eg. to update online media spotlight or sports scores).  The problem experienced by gartaud, myself & others is not related to mcupdate or TMM, as it occurs even with these tasks disabled.

@Mike

Latest update:

When I disable mcupdate and mcupdate_scheduled, I still get my two wakeups at 03:00 and 05:51

When I shutdown ehrecvr I get no 03:00 wakeup, but the 05:51 wakeup persists.

When I ensure ehsched, ehstart and ehtray processes are also stopped / killed, I get a good night's sleep with no wakeups at all !

So, in summary ehRecvr appears to be responsible for the 03:00 wakeup that everyone on this thread has reported, and either ehsched, ehstart or ehtray is responsible for my second nightly wakeup (at 05:51 in my case, but different fixed times for others).

Hopefully, when the right MS people get back from leave we can make more progress.

 

Could part of this issue be related to MCE trying to update the guide data from the ATSC signal? If so is there a way to selectively shut off just that portion of the update? I.E. Continue getting guide data in the conventional manner over the Internet? 

I tested this and there were no more wakeups at night.

I created a bat file like this:

Net stop ehrecvr
Net stop ehsched

TASKKILL /F /PID ehrecvr.exe
TASKKILL /F /PID ehsched.exe

and called it StopServices.

I have MCE standbytool running and you can stop the services and killing the processes with it by placing the bat file in the windows folder and insert the following in the registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Herman van Eijk\MceStandbyTool]

"RunAtSuspend"="C:\\Windows\\StopServices.bat"

 

If you do this the processes and services will be killed each time the pc goes to standby.

 

I think there is another problem with the TV Pack Update!

I just found out that my pc's won't come out of standby for scheduled recordings.

I have a Vista Ultimate running as a server with 4 tv tuner cards so this one doesn't need te wake from standby for scheduled recordings. But I have one pc with only one TV tuner card and I scheduled a recording and it never woke up for recording so I tested this on the Server PC and this one also didn't wake up.

So I started finding out what caused it by uninstalling the latest windows security updates and hotfixes but still no wake up for scheduled recordings.

So my guess is this must be a "bug" in TV Pack update.

Can anyone confirm this or has an idea what caused it?

 

So I had "useless" wakeups in the middle of the night but when it needs to wake up it won't!

 

 

Pino, Thanks for the tip on the "RunAtSuspend" registry key.  I assume you also need to set "RunAtResume" so that these sevices are restarted.

You've also narrowed down the processes responsible for wakeups a bit more than me.  We can eliminate ehtray based on your results, and we're left with ehRecvr causing the 03:00 wakeups and ehSched (or maybe ehStart) causing the other unsolicited wakeups.

I'm hoping someone from Microsoft trawls this thread again soon. 

So far as you're new problem is concerned, maybe I'm missing something real obvious, but surely if you stop ehsched each time you suspend then there's nothing to trigger a wakeup for your scheduled recordings when they fall due during S3 sleep.

 

Runatresume won't be necessary. The services do start automatically when starting MC.

If you only kill the processes they will be restarted automatically so that action will be useless. If you stop the service first and then kill the process it won't be restarted and it solves all wakeups at any time.

When waking up the pc and startup MC the processes will start again.

Yes, MS needs to solve all the bugs in TV Pack real soon.

Have they tested it before releasing it!??

I'm testing my new problem by installing Vista without any updates and the record someting. If it works I will install TV pack without any updates. If recording from standby doesn't work it has to be bug in TV Pack.

For as far as I know it has always worked without TV Pack.

I will come back on this after testing things.

Pino:

I'm testing my new problem by installing Vista without any updates and the record someting. If it works I will install TV pack without any updates. If recording from standby doesn't work it has to be bug in TV Pack.

For as far as I know it has always worked without TV Pack.

I will come back on this after testing things.

I have tested it without TV Pack and no updates, Recordings work fine from standby.

I have tested it without TV Pack with all updates, Recordings work fine from standby.

Installed TV pack without PlayReadyPC and the updates KB950754 and KB951685 and no more recordings from standby. After installing PlayReadyPC and the updates KB950754 and KB951685 still no recording from standby.

Am I the only one?

Pino:

Installed TV pack without PlayReadyPC and the updates KB950754 and KB951685 and no more recordings from standby. After installing PlayReadyPC and the updates KB950754 and KB951685 still no recording from standby.

Am I the only one?

Waking from sleep to make a scheduled recording does still work for me after installing TVP 2008.  Might this problem be related to your MCE Standby Tool configuration?

BTW, Does anyone from MS have an update on the unsolicted wakeups?

Thanks Pixelz, Pino and others for investigating the problem further!

Mike, I believe we have now fully confirmed that the weird wake ups are directly related to the TV Pack. When can we expect additional help from Microsoft?

Is there any hope to get a fix within the next few weeks/months? or is the TV Pack really a beta for Windows 7? :-(

May I also ask again if there is any advanced documentation somewhere on VMC internals and/or how to trace processes that use ACPI-related APIs?

Thank you in advance.