usbd_hid_generic device error in Windows 10

[SmallerPond]

I have tried this demo (SDK17) on a few different Windows machines and they all give the same error for me.  On plugging in the SDK after loading the demo Windows tells me it is installing, then I get a warning that the device could not be setup properly.  Then I see in the device manager that "Device not migrated" with the following:

Device USB\VID_0000&PID_0008\5&543957f&0&16 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_05E3&PID_0749\000000001206
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: ACPI(_SB_)#ACPI(PCI0)#ACPI(XHCI)#ACPI(RHUB)#ACPI(SSP1)
Migration Rank: 0xF000FFFFFFFF0032
Present: false
Status: 0xC0000719

The other USB HID examples work fine, which leads me to think that I'm missing something.  Is there something I am supposed to do in the code to make this example work?

[SmallerPond]

Okay I had a chance to try this on a third Windows 10 laptop and it worked.  I managed to get it to work on one of the other computers by switching USB ports, and even on the original system by plugging it into a USB hub (?).  Is there any reason for seeing this behavior?  Or is this just one of those Windows things?  I can imagine that my testing the first two computers aren't independent since they are both computers that I maintain here, so they have likely seen nearly identical updates and such - so maybe it is just a problem with my particular setup.

[Kenneth]

Sorry, but not seen such an issue before no. Going back to the previously "bad" ports now also works?

Kenneth

[SmallerPond]

No, there are ports that still do not work, but I can either use other ports or, in one of the cases, the "bad" port works by plugging a powered USB hub into the port first (between the port and the device).  I'm guessing this is a problem with the specific system configuration and not with the DK or demo.

[Kenneth]

Can you provide the detailed chip markings printed on the nRF52840?
See example:
https://www.nordicsemi.com/-/media/Images/Products/SoC/SoCs-dobble-top/nRF52-Series/nRF52840-QIAA.png 

Then I can at least check for any known problems with the silicon itself. An USB analyzer trace could be useful just to check for any issues on the USB interface, however it sounds like an "Windows issue" when it says: "Device USB\VID_0000&PID_0008\5&543957f&0&16 was not migrated due to partial or ambiguous match."