MCE Remote Plugin error and stopped logging after upgrade to Windows 10

[seth.feinberg]

@kgschlosser Sorry for my absence. I have a small child and finding time to trouble shoot these things is a bit difficult.

the codes seem to be different every time. I thought they were the same, but when assigning them to kodi actions and repressing the keys, it doesn't report the assigned action in the log (like it used to). Any idea how I can get a consistent response from the buttons. On a possibly related or unrelated note, the commands still show up with an 'unrecognized' tag in between 'mce' and the (now much longer) code.

[kgschlosser]

@seth.feinberg

No worries m8, Family is always first.


when setting up an activity on your remote you need to use these settings

Computer - > Media Center PC
Manufacturer -> Microsoft
Model -> Windows Media Center SE

the harmony 900 is an RF remote. it does not send IR from the remote it's self. there is a base station and IR blasters attached to that base station. You also need to have an IR receiver (this I am assuming you already have) What is the make and model of that receiver?

the receiver is going to dictate the way the IR that is sent from the harmony blaster is translated into something windows can use. We need to hammer this bit of it out. once you get me the make and model of that receiver I will do some looking up and see what it's driver set is and I will advise you on what to do from there.

[seth.feinberg]

@kgschlosser thanks for the response (and for forgiving)

So if you look at the previous posts, I actually have an atypical set up. I have that Media Center SE device added, but I actually have 2 PC's connected to the Logitech blaster (one dedicated HTPC and one gaming/everyday/backup HTPC Beast of a PC) and if I use Media Center SE the remote will unfortunately command both devices undesirably. SO I've created 2 'dummy' devices, 2 AVR's that are NOT in the setup. I then use(d) EventGhost to intercept those 'dummy' commands and map them to Kodi commands on each individual PC. This worked perfectly before I upgraded to Windows 10 and through your very helpful direction I was able to get my PC to recognize that IR commands were being sent to the PC, just haven't been able to do anything with them yet. (I did this by uninstalling the old MCE plugin and installing the Vista++ plugin and installing the service in the configuration). The codes though, that show up in the EventGhost log are of the form MCE.Unrecognized.{some code of inconsistent length}

It's been so long since I built this HTPC that I can't fully remember which IR Receiver i used, but I searched my email and found an order confirmation from Inteset Systems. I bought 2, a "IR Receiver w/Cable and a Custom Mounting Bracket for use with ASRock CIR motherboards" and a "USB INternal Infrared (IR) Reciever Only with Cable and Mounting Bracket". I THINK i used the first one. I can confirm tonight.

[kgschlosser]

ok that kind of helps. now I need to know your mother board model number. I am going to let you know that you could be running into an issue by using the CIR on the main board. the one on the board is more for use as an IrDA port in most cases. This is the reason I would like to have the model number of the main board. just to make sure of what it is. I have not come across a built in MCE remote receiver for a main board. Even if it is a purpose built HTPC by one of the main stream manufacturers it is a USB ir receiver it just plugs into the USB header on the main board instead of having the typical USB A connection.

When you get the time to shoot the model number off to me that would be great. Just in case you don't know how to obtain the model number without going hunting for the manual or opening up the computer, start --> run --> dxdiag say no to the checking of the drivers. On the System tab it will say System Model. that is what I need. along with the manufacturer. (we want to make sure this board is for the part you bought).

I will do some poking about to see if I can drum up some information on that IR receiver.

[kgschlosser]

ok so this is what I have managed to dig up.

the onboard CIR is kind of a strange bird. it seems as tho it will make use of 2 different drivers. ones made by Nuvoton and the second is the ehome drivers. now there could have been something that has changed with windows 10 and that is what is causing the issue. I would recommend trying to locate the drivers for the actual CIR chipset. I believe it is Nuvoton. You can also download a program called USBDeview by Nirsoft This will allow you to see all installed USB drivers. even the ones that are not in use. It will also allow you to uninstalll the diver and also delete the driver (be sure not to delete the Microsoft ehome driver). You may need to make sure your system is clean of any drivers that are attached to the CIR port. then install the Manufacturers drivers and whatever else is needed. then from there install the MCE Vista+ plugin. Be sure to download the latest version of the plugin. Or my suggestion would be to go and buy a USB receiver. I recommend the Pinnacle MCE Receiver/Blaster It is only 25.00 USD come with a remote and also has 2 ports for blasters. This receiver I know works. and it works perfect. I personally own one and only had one bump in the road with it and that bump is really easy to fix. (took me almost 2 years to figure out how to fix it tho LOL). That receiver works with every remote and every kind of IR code I have thrown at it. including the Samsung remote codes.

The setup that you have is no longer made by your mainboard manufacturer and it is super difficult to find any express information on how to use it. let alone if there are any issues with it and windows 10.

[seth.feinberg]

hmmm I think i'll have to re-read this a few more times to fully grasp what you are implying/instructing. But to answer some of your questions now that I'm actually in front of the HTPC:

I may have led you on a bit of a red herring. I am still fairly confident that I used the inteset IR receiver on this thing, but after opening it up, it says Inteset nowhere on it. It says TopSpeed M64DX003-D which returns an ebay link as the first hit when i type it into Google and that doesn't seem like a great sign for compatibility (But it fits so nicely in my lowpro case!). Also I was wrong, it is decidedly NOT wired to CIR, but to the top 4 pins of a USB header.

And the motherboard is an ASRock H87M Pro4. I put the command you mentioned into the Run dialog but the DirectX Diagnostic Tool reported "To Be Filled By O.E.M." Did I do something wrong in the build?

[kgschlosser]

nope you did nothing wrong. That can happen sometimes.

The ir receiver is only hooked to the 4 pins on the USB header?? are you sure?? because the CIR header is 4 pins. and I thought USB Header is 2 rows of 5 pins i could be mistaken tho. let me see what i can dig up on that model number you posted there.

[kgschlosser]

ok from what I am reading is that it is connected to USB and USB only. and that it is compatible with windows Vista and newer. so you will need the Vista+ plugin.


This is what i need you to do. You have to do it in this order specifically. I will explain as to why at the end.


Uninstall the Alternate MCE IR service from inside of the vista+ plugin. if you have it installed. You will need to run EventGhost with Administrative privileges. it does not matter if your user account has Admin rights. they are not the same thing.

Download that USBDeview program i mentioned form the other post.. run it. Locate the Microsoft eHome drivers. there may be more then one of them. And any divers with the letters CIR in the name. Right click on each one and click on Uninstall. DO NOT DELETE THEM.

Have any IR remote handy. It has to be an IR remote and not the harmony. one that is not for a device that is in the room where your computer is.

Reboot your computer. as soon as you see the Windows logo point the remote at the computer and start tapping a button.. doesn't matter what button. just keep on tapping it. (don't hold it) Keep on doing that until you here a series of chimes, and then keep on tapping. there are a bunch of drivers that get installed so you are going to hear a bunch of install chimes. this can take a while to happen. so even after the logon screen comes up do not stop tapping. when you feel it has been long enough (typically 1 minute after you see the logon screen) you can then stop tapping and logon.

Run EventGhost with administrative privileges. And install the latest MCE Vista+ plugin. and install the alternate MCE IR service. then save your EventGhost.

Reboot the computer. No need to worry about the remote this time.


That should hopefully fix any issues you may have.


We reset the while eHome set of drivers by using the USBDeview to do the uninstall.
On some of the IR receivers they have a low power mode they go into. this happens if they do not receive IR for a while. this can happen when Windows is installing the drivers, typically the first time you start the system after an install or upgrade of Windows. And the first time you run windows it is pretty much a guarantee that the receiver is going to go to sleep because of how long it takes for Windows to start. the drivers end up getting all messed up because of this. so by pressing the button on the remote we ensure it doesn't fall asleep.

[seth.feinberg]

I will do this asap and get back to you, many thanks!

The ir receiver is only hooked to the 4 pins on the USB header?? are you sure?? because the CIR header is 4 pins. and I thought USB Header is 2 rows of 5 pins i could be mistaken tho. let me see what i can dig up on that model number you posted there.

Yeah, I remember reading this in the IR receiver manual. the USB header has 5 pins on the top and 4 pins on the 2nd row (its a rectangular plug so it looks like 2 rows of 5). And again, it worked flawlessly before the upgrade and sending Microsoft Keyboard keypresses mapped to the Harmony works just fine as well, so I think that part of it is fine.