Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Possible fixes for IR receiver or remote problems after installing Update Rollup 2 for MCE 2005

Possible fixes for IR receiver or remote problems after installing Update Rollup 2 for MCE 2005

There have been a few reports so far from customers who have installed Update Rollup 2 for Media Center 2005 and have had problems getting their infrared (IR) receivers or devices such as remote controls or wireless keyboards to work correctly afterwards.  Update Rollup 2 setup installs an updated set of IR drivers (also shipped independently as KB888795) that have caused some sporadic issues.  Here is a list of the workarounds we have seen be successful so far to resolve IR receiver/remote control issues after installing Update Rollup 2:

1.  The IR receiver appears to be installed correctly but pressing buttons on the remote does not do anything

In this scenario, it is possible that the remote control has been configured to broadcast on a channel range that was supported previously but has since been removed.  You can use the steps that I previously posted here to reconfigure your remote control to broadcast on a different channel to resolve this issue

2.  One or more of the IR drivers is configured incorrectly in Device Manager

In this scenario, if you look in Device Manager (by going to the Start menu, choosing Run and typing devmgmt.msc), you will see yellow exclamation points next to one or more items in the Human Interface Devices category.  The following steps will resolve this issue in most cases:

  1. Go to the Start menu, choose Run and type devmgmt.msc
  2. Expand the Human Interface Devices category
  3. Right-click on each of the items with eHome Infrared Transceiver in the name and choose Uninstall
  4. Unplug the IR device from the computer and wait for approximately 30 seconds
  5. Plug the IR device back into the computer and wait for Windows plug-and-play detection to kick in and re-install the device

3.  Some remote control buttons (number keys, arrows, enter) fail to function, while other buttons work as expected

We have not yet been able to reproduce this scenario in our test lab, but we have seen this set of steps resolve this issue on some customer machines so I wanted to post it here in case someone runs into a similar problem:

  1. Delete the file named %windir%\inf\keyboard.pnf.  Please note that the correct file to delete ends in PNF - do not delete keyboard.INF.
  2. Go to the Start menu, choose Run and type devmgmt.msc
  3. Expand the Human Interface Devices category
  4. Right-click on each of the items with eHome Infrared Transceiver in the name and choose Uninstall
  5. Unplug the IR device from the computer and wait for approximately 30 seconds
  6. Plug the IR device back into the computer and wait for Windows plug-and-play detection to kick in and re-install the device

4.  If none of the above suggestions work

There are some cases that we have seen where none of the above suggestions work.  A customer posted a comment indicating that it sometimes helps to short the Media Center remote control to forcibly reset it.  You can see more information about how to do that in this blog post.

<update date="12/29/2005"> Added a link to a new post I created with a description of how to short a remote control </update>

 

  • I am haveing a promlem geting the 2 IR buds that come with the MS remot control to work.  The red light on the main remote sensor does not even come on when using the IR bud as the sensor and any button on the remot is pressed.  The IR buds are pluged in to the main sensor.  Any ideas?

    Thanks in advance.
  • hello I have a version OEM and want to buy the remote and receiving control, like or where I can buy thanks.
    vori00@terra.es
  • Hi Vori - You can check out the web page at http://www.microsoft.com/hardware/mouseandkeyboard/ProductDetails.aspx?pid=065 for options and pricing information for remote controls that work with Windows Media Center.
  • Hi Jake - I have not heard of this issue before.  Can you please try some of the other workarounds that I have posted for IR issues (listed in the "Remote control and IR receiver errors" section of http://blogs.msdn.com/astebner/articles/487537.aspx)?  Also, can you try to install the latest IR hotfix rollup from http://www.microsoft.com/downloads/details.aspx?FamilyID=b39d53f1-0ac9-433b-b488-4cab82f31dc8&DisplayLang=en and see if that helps in this scenario?
  • I have a problem where my remote appears to work (during setup, the numbers appear correctly on the MCE TV screen) but my Direct TV receiver does not change channels, or only "catches" one of the  three digits and subsequently doesn't change channels.  I have tried adjusting the "speed" of the IR signal, "relearned" the channels from my settop remote, the IR rollups 1 & 2, changed the broadcast channels (tried channels 1-4 as per the workaround), and checked my device manager (no yellow exclamation marks).  It appears that the MCE gets the info fine from the remote, but the settop reciever is struggling to understand what is being emitted from the emitter.  Any suggestions?  Thanks!
  • I have fresh install of MCE 2005 on a new Shuttle xpc and everything works perfectly except the remote.  I've installed all updates and tried all fixes mentioned here and elsewhere - ALL of them - and nothing works, I get no remote functionality.

    The remote is broadcasting, the receiver is receiving and shows up as functional in the hardware device list, the channels match up, everything should work.

    Any ideas that have not already been mentioned?
  • Ok, I have a slightly different problem. The remote works fine once MCE is running. I just can't get MCE to start using the green button. Any ideas?
  • "3.  Some remote control buttons (number keys, arrows, enter) fail to function, while other buttons work as expected"

    This was my problem and your solution worked PERFECT. Thank you!Thank you!Thank you!
  • Hi,

    I seem to be having a slightly different IR problem to those that have been reported so far.

    When the PC is rebooted MCE doesn't always have focus, probably 2 reboots out of ten (MCE is set to run when Windows starts and always be on top),consequently none of the keys on the remote appear to work until the Green Button is pressed which appears to return focus to MCE, everything then works perfectly.

    This is proving to be quite irritating for some customers. This also seems to be quite a recent problem. We are running all the latest updates (express & custom) Is it possible one of these has caused the problem?

    Thanks
  • Hi Chris - It sounds like you have already enabled the item called "Media Center window always on top" in Settings | General | Startup and Window Behavior, but if you haven't can you please make sure that is checked?  If this still happens even with that checked, I am not sure what could be causing it.  Are there any other programs that are launched when your machine boots that could be "stealing" the focus away from Media Center?
  • I have installed all updates from Windows update.

    I have problems that the Microsoft remote controller doesn't work after being in S3 standby. It only happens if LiveTV have been accessed. Hope you have an idea what to do?!
  • Any idea how to get two trancievers working at the same time in MCE 2005?  I have one monitor and speakers in one room, and another set in another room on a KVM USB extender. It works great, except that I can only plug in one tranciever at a time, or my other one stops working.  They both work, just not at the same time.  Any suggestions?

    -ted
  • Hi Ted - This scenario is not supported.  The IR driver only listens for the HID commands sent by the remote control on one of the receivers.  You may want to try out IR blasting devices for this kind of scenario.
  • Why are the comments from Jellybean Cowboy and Thomas (even though he's only got the problem after live tv) ignored in this blog?

    I've got the same problem, USB disconnect- and connecting sounds while resuming from S3, and after that a not-responding remote.. I haven't got a clue what's causing it, I'm guessing that all USB-devices (it appears also my videocard) are 'refreshed' and for USB that doesn't work like it should.. devices aren't 'found' again until you force a reboot or disconnect the USB-plug and reconnect it..
  • Hi Kristian - I haven't been ignoring the comments from Jellybean Cowboy or Thomas.  The problem is that I don't have any suggestions to try to solve this issue that I think would be useful.  I decided it would be better to post nothing rather than post ideas that are nothing more than guesses.  I'm sorry I'm not able to be more helpful here.
Page 4 of 7 (102 items) «23456»
Leave a Comment
  • Please add 7 and 3 and type the answer here:
  • Post