United Kingdom
i'm having the same problems, worked fine for the last couple of months, and now it's broken.
the exact problem is that the windows eHome driver seems to be loading on startup, and this somehow takes precedence over the Input Service, or breaks it somehow. so instead of receiving remote commands thru the input service (with all the proper mappings) they are received from the windows driver. this is why U/D/L/R/OK work fine but nothing else.
restarting the input service gets that working again, and brings back the correct key mappings, but doesn't then disable the windows driver, so U/D/L/R/OK are all processed twice, resulting in double-clicks of all those buttons.
the annoying thing is when i had all these troubles the first time i was able to fix them by disabling the media centre services and the HID service. this time i've double and triple checked, and everything is disabled as it should be - and yet the problem persists. i've tried system restore back to when it used to work OK, and it's not helped.
strange - i disconnected and reconnected the IR receiver, restarted the input service, and it seems to have solved it...
the exact problem is that the windows eHome driver seems to be loading on startup, and this somehow takes precedence over the Input Service, or breaks it somehow. so instead of receiving remote commands thru the input service (with all the proper mappings) they are received from the windows driver. this is why U/D/L/R/OK work fine but nothing else.
restarting the input service gets that working again, and brings back the correct key mappings, but doesn't then disable the windows driver, so U/D/L/R/OK are all processed twice, resulting in double-clicks of all those buttons.
the annoying thing is when i had all these troubles the first time i was able to fix them by disabling the media centre services and the HID service. this time i've double and triple checked, and everything is disabled as it should be - and yet the problem persists. i've tried system restore back to when it used to work OK, and it's not helped.
strange - i disconnected and reconnected the IR receiver, restarted the input service, and it seems to have solved it...