MCE remote has stopped working (1 Viewer)

[beatnut88]

Hi
MCE remote has stopped working suddenly. Not just in MP1 either - e.g. the volume control doesn't work. The remote lights up and the receiver also lights up. Literally it was working and then wasn't. Logs attached.
Any help appreciated

 

[Helios61]

I have noticed the same issue 1 hour ago after the new Windows 10 update (KB4016240 ?). The receiver wasn't recognized proper in device manager. After completely turning of the HTPC and restart now all is working fine.

 

[beatnut88]

Thanks... the cause is probably the same....but the receiver is recognised. Turning off the PC did not help. Using the keyboard is a pain. Dunno what to do next.
Neil

 

[mm1352000]

Neil,
When you say "turning off the PC..." did you:

1. Windows shutdown then press power button to turn the PC back on, OR...
2. Windows reboot.

I ask because since Windows 8 there are important differences. In short: (2) is preferred.

 

[beatnut88]

Did a shutdown and reboot from cold. I think you mean 1 is preferred.
Neil

 

[mm1352000]

I think you mean 1 is preferred.

No, I don't. (2) is preferred because of hybrid shutdown. Basically: when you think you've turned your PC off it's actually hibernating, and when you turn it back on it just resumes (which means drivers and hardware aren't reinitialised - critical).

...so if you haven't already, try a Windows restart.

 

[Helios61]

That's the shotcut for a complete shutdown-> shutdown.exe /s /t 0

 

[beatnut88]

Well, went the whole hog and unplugged the PC last night and plugged it back in and switched it back on this morning. Unfortunately this hasn't helped. I can't be the only one in this predicament but I dunno if a note to Bill Gates would necessarily get them off their bums to fix this - esp as the MCE would be regarded as a legacy device. Should I look at getting another remote? The keyboard is no solution obviously.
Neil

 

[mm1352000]

I can't be the only one in this predicament...

Yes, you really can.
As of right now, to the best of my knowledge you're the only person to report such a problem recently (say in the last year or so).

...but I dunno if a note to Bill Gates would necessarily get them off their bums to fix this - esp as the MCE would be regarded as a legacy device.

There seems to be a huge assumption (that you have the same problem as Helios61) wrapped up in this statement. Have you checked that assumption? If yes, how?
Note I'm not saying that you're mistaken. Rather, I'm just very conscious that assumptions can so easily lead investigations down a completely wrong track which wastes a lot of time and/or money. I'm trying to help you avoid that.

Should I look at getting another remote?

If it were me I wouldn't be even thinking about this yet.

I'd check the basics first. For example:
1. Have you tried replacing the remote's batteries? I know it might seem inconceivable, but just because the receiver lights up doesn't mean that the command signal is intelligible. Low battery is just one possible source of unintelligible commands.
2. Have you checked whether the Windows update mentioned by Helios61 is actually installed? ...and if it is, have you checked what happens if you remove it? If your assumption is correct, the update has been installed, and uninstalling it should solve the problem... but this should be confirmed.
3. Have you checked your Windows system event log?
For example, I don't see any references to the aforementioned Windows update.
For example, I see that a driver for an AVerMedia A825 USB dual DVB-T tuner was installed on the 15th of April. As part of that installation, an HID (read: potentially a remote control receiver) driver was installed. Such drivers can conflict with MCE receiver drivers.
[collapse]
"4/15/2017 8:27:19 PM";"Service Control Manager";"(0)";"Information";"A service was installed in the system. Service Name: AVerMedia A825 USB Dual DVB-T Service File Name: \SystemRoot\System32\Drivers\AVerAF35.sys Service Type: kernel mode driver Service Start Type: demand start Service Account: ";"1073748869"
"4/15/2017 8:27:19 PM";"Microsoft-Windows-UserPnp";"(7005)";"Information";"Driver Management has concluded the process to add Service AVerAF35 for Device Instance ID USB\VID_07CA&PID_0825\0000000000000 with the following status: 0.";"20003"
"4/15/2017 8:27:20 PM";"Microsoft-Windows-UserPnp";"(7005)";"Information";"Driver Management concluded the process to install driver avera825.inf_amd64_dc014f59d25d75e7\avera825.inf for Device Instance ID USB\VID_07CA&PID_0825\0000000000000 with the following status: 0x0.";"20001"
"4/15/2017 8:27:20 PM";"Microsoft-Windows-UserPnp";"(7005)";"Information";"Driver Management has concluded the process to add Service HidUsb for Device Instance ID USB\VID_045E&PID_00DD&MI_00\6&1FD32C77&0&0000 with the following status: 0.";"20003"
"4/15/2017 8:27:21 PM";"Microsoft-Windows-UserPnp";"(7005)";"Information";"Driver Management concluded the process to install driver itpcdless.inf_amd64_1aa42dd65e45afbb\itpcdless.inf for Device Instance ID USB\VID_045E&PID_00DD&MI_00\6&1FD32C77&0&0000 with the following status: 0x0.";"20001"
"4/15/2017 8:27:22 PM";"Microsoft-Windows-UserPnp";"(7005)";"Information";"Driver Management concluded the process to install driver type64.inf_amd64_9a0444c897e589f8\type64.inf for Device Instance ID HID\VID_045E&PID_00DD&MI_00\7&32F0ABD9&0&0000 with the following status: 0x0.";"20001"[/collapse]

For example, did you check whether/which updates were installed immediately prior to the remote control stopping working.

 

[beatnut88]

Duh! Batteries. Di replace them but obviously the replacements were duds too.
Thanks a bunch
Neil