The problem may not be that of Philips.

When The machine boots and the OS comes into operation. It is going to look for the USB devices that it thinks belong to it like an IR receiver, a keyboard, a mouse. In Microsoft's eyes It comes first ahead of anyone else (So what is new) . It then initializes registered drivers which grab those devices they think are theirs.

Sooner or later Philips gets its chance to grab its device if it can find it which means some one else has not taken it (mistakenly) as their dvice. If some one has, then the HID message will be issued.

So what can Philips do about it. Not really anything. There is no API to say "HEY, you took my device and I want it Back!!" I am not sure but perhaps they could tell you which driver has their device but I am not sure there is an API for that other then perhaps a registry search.

The real culprit is Microsoft with just bad software. A very poor enumeration and allocation mechanism for installable device on the USB bus.