1 of 1 people found this helpful
I am not from Intel; this is not a situation unique to NUC. The Xbox remote has an ID something like 8, while non-Xbox remotes have default ID 1. Windows by default only responds to ID 1 and a few after that. If you are comfortable editing the Windows registry, you can search the web for how to change a number in registry (try the terms CodeSetNum0 and Xbox), then reboot, and the remote should be recognized (assuming that the CIR driver is installed). I think once you find the registry entry, If you change the value of the CodeSetNum0 key from 1 to 0 then it will respond to all remote IDs, or if you change it from 1 to 8 then it will respond to your Xbox remote but not the default Microsoft remote.