[logifuse]

Hi all,

Thought this might be helpful if anyone is struggling with an MCE remote on a new install of Windows 10.

I have a new NUC that didn't want to respond to a standard MCE remote (or a Harmony configured as an MCE remote). The remotes worked on my existing HTPC & tested fine on my laptop, but wouldn't work on either of my NUCs, either through the built in eHome Infrared Transceiver, or via a USB one. The key difference that I worked out was that the HTPC & laptop were both upgraded from Windows 7, while the NUCs were straight Windows 10 installs.

After mucking around with ShowKey.exe (program that shows what button presses are registered, available here: http://xbmcmce.sourceforge.net/), I found that none of the specialised MCE buttons (the green button, info, recorded TV, guide, live TV, DVD menu & the colored buttons) would generate an output, even after reassigning them via Advanced MCE Remote Mapper (https://forum.kodi.tv/showthread.php?tid=164252). I compared drivers, devices, etc, but the only real difference I found was this extra registry key on the 'pure' Windows 10 PCs:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f56da which is the "RC6 based MCE and XBOX360 remote"

Underneath that on the 'pure' Windows 10 PCs (but first up on the upgraded ones) is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da which is the "RC6 based MCE remote"

Advanced MCE Remote Mapper & XBMCCustomRegis edit the second (57da), but not the first (56da). I imagine that correctly editing the buttons on the first would fix it, but simply deleting the key & rebooting makes the 'pure' Windows 10 PCs use 57da & it works perfectly.

The only other issue is that the XBMCCustomRegis script has an error as it looks for the (x86) file path for Kodi. Editing the file path in the AHK script file fixes it.

This will probably help with MediaPortal, Emby Theatre, WMC hacked into Windows 10, etc so I'll add them so it's searchable.

Cheers.

[Plantje]

Thanks for sharing this!

[beeswax]

What model of NUC is it exactly and what version of Win10?  It must be specific to one or both as I've done countless clean installs of Win10 on the 2 NUCs in my house and MCE remotes, Harmony remotes pretending to be MCE Remotes and MCE Keyboards have never been a problem.  I've only done clean installs from 1607 up to 1809, maybe it's a 1903 thing if that's what you used?

[logifuse]

What model of NUC is it exactly and what version of Win10?  It must be specific to one or both as I've done countless clean installs of Win10 on the 2 NUCs in my house and MCE remotes, Harmony remotes pretending to be MCE Remotes and MCE Keyboards have never been a problem.  I've only done clean installs from 1607 up to 1809, maybe it's a 1903 thing if that's what you used?

NUC7i5BNK & NUC7i5BNH (basically the same model).

Both were originally installed with 1803 (which had the problem), the BNH is now on 1809 & the BNK is on 1903 (both same problem).

I thought it may have been specific to them too, as I've only found a handful of items in Google that seem to describe the same problem (without identifying the registry key), so it must be a certain combination, but what?

I just had a look at a new Dell laptop with 1809 & it doesn't have the registry key - perhaps it was introduced by 1803?

I might do a clean install of 1903 on the BNK (I'm prepping it to replace my current HTPC) just to see.

[ashlar]

Many thanks for sharing.
Posting a solution instead of a problem, nice!

[logifuse]

Fresh install of 1903 on a laptop (old Panasonic Toughbook CF-53) & there's no HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f56da "RC6 based MCE and XBOX360 remote"

I just don't understand why it would be introduced by a NUC (or these NUCs) specifically? I don't really have time to do a fresh install of 1903 on one of them, but I'd really like to know if it's 1803/NUC7-BN specific.

[gazavant]

Fresh install of 1903 on a laptop (old Panasonic Toughbook CF-53) & there's no HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f56da "RC6 based MCE and XBOX360 remote"

I just don't understand why it would be introduced by a NUC (or these NUCs) specifically? I don't really have time to do a fresh install of 1903 on one of them, but I'd really like to know if it's 1803/NUC7-BN specific.

I'm a bit late to the game here, but may have discovered some relevant information about your question.

I had the same struggle with my NUC6CAYH.  Your solution of simply deleting the 56da key solved the problem (thanks, BTW), but I still wanted to know what the heck was going on.

I'm not sure what made me think of it, but I thought that maybe it had something to do with the Intel CIR driver.  I checked the driver release notes and found this:

Version: v5.3.4.0 for Microsoft v1.5.0 ITECIR
Release Date: 10/24/2017

Merge MCE and XBOX360 into one Registry key

You can find all the details at https://downloadmirror.intel.com/28755/e...20Note.txt

This update affects a multitude of NUCs, not just mine, and I suspect it the cause of the issue we've been experiencing.  It's related to Windows NUCs, and not new installs of Windows 10.

If I'm correct, it probably means the next driver update will simply reinstall the 56da key, but at least we know there's an easy fix.

I have no idea of the logic behind merging the RC6 and XBox keys was, but it doesn't seem to have been helpful.

Gaz

[JeePeCe]

Hello,

On Windows 11 with au Intel NUC, since the deployment of the latest version of the Intel IR driver (v.5.5.21), or because of latest updates of Windows 11 itself, this trick unfortunately no longer seems to work.

Indeed, each time the PC is restarted, the registry key " [...]56da " is now automaticly regenerated each time, partially empty but enough to prevent the "[...]57da" key from having priority.

From then on, in my case it became impossible to use and configure an RC6 MCE remote control.

If anyone has found an alternative solution, please share it.

Thanks in advance.

[jurialmunkey]

@JeePeCe - I think I've found a solution. Been having the same issue past two weeks after I stupidly updated my CIR NUC drivers.

Instead of deleting the "[...]56da" key entirely, my approach is to overwrite the "[...]56da" key with the "[...]57da" version. So far it seems to be sticking after a restart. I'm assuming the driver only cares if the keys exist not the values inside.

I use Advanced MCE Remote Mapper utility for remapping but the following should work regardless of how you remap:

• Apply your remote mapping using Advanced MCE Remote Mapper (or similar)
  
• Open regedit and delete the "[...]56da" key
  
• Right click the "[...]57da" and rename it to be the "[...]56da" key.
  
• Close regedit and then use Advanced MCE Remote Mapper to regenerate your "[...]57da" key (since we renamed it, it will no longer exist -- you could probably just save the key before renaming and reapply it via regedit but I did it this way).
  
• Reapply your remote mapping and restart
  

[baza_dwa]

In my case the ReportMappingTable was overwritten in both 745a17a0-74d3-11d0-b6fe-00a0c90f57da and 745a17a0-74d3-11d0-b6fe-00a0c90f56da branches after each reboot. Nothing seemed to work.

So I reverted to driver 5.5.0.0 (as seen in driver properties), which was located in file named CIR-Win10-5.4.5.0.zip - and the problem is gone.

[Grumpy]

Hello all.
Been racking my brains as to why the upgrade to a NUC i5 11PAH wasn't allowing the MCE Green Button to be recognised.
So long story short, as long as this entry is in the registry ...
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f56da]
all should be fine.
I did the 6da deletion and renamed the 7da as 6da. 
7da is back with very little in it.
Kodi now works being started by a desktop shortcut set to Ctrl-Shift-W, which is the Green Button default key sequence.
WMC not installed on PC, so that sequence is free.
Not too sure about the latest Kodi version and Win11 24H2, some intermittency here and there, but after a restart or two, everything seems to have settled down.
Hopefully the user I am doing this for, won't scream and shout at me, when it all goes tits up...
Cheers