DISE Programmer application sometimes won't use the correct handle to access the HID Keyboard.

[shaise]

DISE Programmer application sometimes won't use the correct handle to access the HID Keyboard.

[shaise]

I just can't reproduce this issue on my PC. No matter what usb port I use, it always recognize the device.
Can you advise how to reproduce this issue?
What windows version do you use?

[CJGuirao]

I'm using Windows 11

Using devmanview64 I can see the two installed devices (look for the device with VID 0483 PID 573e) :

HID Keyboard Device	(Standard keyboards)	kbdhid	Keyboard		HID\VID_0483&PID_573E&MI_00\a&4482ba4&0&0000		0x000000a0	0x00000000	No	No	07/02/2023 4:15:39	07/02/2023 4:15:39		{7fa5de54-2ab7-5446-97a0-875568c42bd5}	{4d36e96b-e325-11ce-bfc1-08002be10318}	07/02/2023 4:15:39	07/02/2023 4:15:39	10/02/2023 4:17:55	10/02/2023 9:45:07	HID Keyboard Device	10.0.22621.1	keyboard.inf	HID_Keyboard_Inst.NT	21/06/2006	07/02/2023 4:15:39	


HID-compliant device	(Standard system devices)		HIDClass		HID\VID_0483&PID_573E&MI_01\a&177847e2&0&0000		0x000000e0	0x00000000	No	No	07/02/2023 4:15:39	07/02/2023 4:15:39		{7fa5de54-2ab7-5446-97a0-875568c42bd5}	{745a17a0-74d3-11d0-b6fe-00a0c90f57da}	07/02/2023 4:15:39	07/02/2023 4:15:39	10/02/2023 4:17:55	10/02/2023 9:45:07	HID-compliant device	10.0.22621.819	input.inf	HID_Raw_Inst.NT	21/06/2006	07/02/2023 4:15:39	

I had the issue twice , just by plugging the device while testing it. I used different ports on different hubs and it happened.

To force this issue It may work to unplug the device, uninstall the entry that is detected as a keyboard with devmanview and plug it again so windows reinstall the device driver.

That may switch the order of the devices.

[shaise]

Do you have an access to a windows 10 machine, to see if you have the same problem?

[CJGuirao]

No right now,
I'll find one to test it.