omegabio

I have a similar problem with the same machine. I tried a custom driver install and selected the eHome remote install under the Microsoft section for drivers, I got a big warning that the driver was not for the device and then it still failed to start. I suspect something on the board acts like a USB hub and that fails.

I've installed the Hauppauge drivers as well with no luck. I think the IR blaster is actually on the hauppauge HVR-1800 1850 card and that the card acts like a USB hub for the IR-blaster.

Official Microsoft eHome Infrared Receiver (USBCIR) Drivers download center, download and update Microsoft eHome Infrared Receiver (USBCIR) drivers in 3. I've installed the latest Windows 7 drivers from Diamond for the VC500 - and also disabled my blueTooth adapter. Download Exploring Corporate Strategy. The Device did. Yeah, I've tried both of those and also downloaded the newest drivers from Diamond. 'Ehome Infrared Receiver' refers to a Windows Media Center compatible IR receiver. Ehome infrared receiver drivers download, download and update your Ehome infrared receiver drivers for Windows 7, 8.1, 10. Just download now!

I'll tinker with it tonight and see what I can find. Here is what fixed it for me. Somehow it enumerated one of the USB hubs wrong during upgrade • I uninstalled the device from device manager (the unknown device with the exclamation mark) • Shut down • I detatched ALL usb headers from the motherboard and removed the interface cable to Hauppauge card.

• Booted Started Windows. Checked device manager. No failed devices • Shut Down • I re-attached ONLY the IR Remote receiver usb cable. To force a rededect I attached it to another USB header (it was on header 2 I put it on previously open header 1) • Booted • Windows detected the infrared remote, but but failed on another device (IR blaster?). I suspect it detected it as an eHome Remote not a Transceiver. Even so no failed devices.

And what do you know my remote works! • I wired all my USB cables that I previously detatched • I plugged in all USB devices (Logitech Headset, Portable Media Drive, HP monitor usb hub, Printer) • Booted Started Windows • Everything runs perfectly now J Here is the HP forum link. Ok after millions of attempts trying all sorts of things i finally ended up shoving two headphones into the jack of the usb hub for the MCE remote and vaalla it worked got past the ir hardware detection although it doesn't control my set top box like it used to before in vista I'm satisfied for now till i get around to buying some IR bugs. I hope this helped because it sure drove me nuts Did you read my solution?

Uninstall the device from device manager. Open the case. Disconnect the USB headers. Check that windows does not pick up the device. Connect the USB headers again (I used different ones to force a reload). Driver Monitor W1942tt. Restart and voila! EHome is a windows driver so no install disks needed.

The H-P forums has more on this, but it is a USB enumeration problem. I know it's a bit late, but I have the same problem with an external card reader, using the same software. I'm pretty sure it's just an external version of the same device. Following the solution did not work for me however. When the computer has fully booted, the drivers instantly fail installing. I never needed to install any drivers. Windows just needed to detect the device correctly.