Problem is, my HP WMC USB sensor doesn't get recognized by Windows, works fine on Windows 7. Also, I am using MCE Controller as a TCP-IP but the "green button" is not recognized and opens either the start menu or IE. So I am thinking, some service needs to be enables. Using V10, v12 gives me - application blocked by administrator error.
Some water and messages has been floating since the last information about extenders - 360, can we in the nearest future expect to see a version 13 that includes normal extender installation? I have v12 that works smooth but trying to install extender windows 10 and wmc "hangs" just before the third crossbox confirmation. The only way out is Norwegian reset.
I don't have any "First Hand" knowledge of "Why", but I heard rumor Emby is lacking in the Remote Control Department. This might be one reason to install an "Emby Plug-in" inside of WMC. If this true, my "guess" as to the problem of the original poster, is the plug-in is having some difficulty connecting with the WMC "Remote Control" function. I would guess the problem is with the Plug-in App and not WMCv12. If the above is true, I am not sure if it would be advantageous to allow Plug-ins to access the WMC Remote Control Function.
Using a internal ir receiver from Amazon "USB Internal Infrared (IR) Media Center Receiver with Cable & Custom Mounting Bracket" With a logitech harmony 700(add device as Microsoft/Windows Media Center SE). Works great.
Does your "green button" start WMC? My main concern is that I green button command doesn't work with MCE-Cotrller (TCP/IP based control). I thinking it has something to do with the fact that the IR doesn't work. Perhaps, some service isn't properly installed.
That depends. Not being recognized "by windows", means very little. If the driver has no question marks, likely the remote is ready to be used by Eventghost. Just test it, and forgot the WMC internal support. If eventgost recognizes it you are OK.
Thanks for the links. I ran the recovery command which then forced me through setup - I did the custom setup and tried again. But, Media Center is still hanging for me. It occurs after returning from MPC-HC (which I'm using for playback and refresh rate changes). The only thing that gives me access back is to put the PC to sleep and wake it up again, and then killing MC via Task Manager.
Hence that's a problem that has little to do with the usual WMC problems. Likely is a driver problem, try to change the output of MP from its settings, try to launch wmc with the /dx9 switch, try to upgrade/downgrade your VGA driver and so on. Is hard to fix remotely this kind of problems
Thanks again I've already tried a couple of video drivers. I'll give that dx9 switch a go. I tried the V8 uninstaller and then installed V8 - which gave me a plain vanilla WMC. I then installed EMC and it looked to be working for a little while and then I got the same issue again. I noticed that it's ehshell.exe that goes to "not responding".
I guess WMC is off the blame list. Next suspect OS, Sleep and Tasks Google this.... sleep and wake it up again.
I don't think it's sleep related. It crashes from a fresh boot. The sleep/wakeup gets me access to task manager. Tried /dx9 on the command line - same issue
What a relief. I guess I don't need an Optometrist. A lot of that HP stuff is proprietary. If your Win10 wont recognize your device, spend the 15 dollars and confirm that both devices do the same thing, before you start tearing apart your OS. Rosewill cheapo works in 7 and 10 which has been confirmed by myself and others.
You can try installing a fresh W10 copy in a separate partition or (better) inside of a VHD (in dual boot), to be sure it isn't a problem dragged from the upgraded windows. That's unlikely but possible. If your fresh copy has the same problems becomes clear that's a waste of time trying to fix the old one. At least trying to fix it looking at WMC alone.