Windows 10 not recognizing Arduino Micro or Leonardo as HID

[cyborg5]

If you have an Arduino Micro or Leonardo running a sketch that does mouse and keyboard emulation, it will not work under Windows 10 after any reboot. You can unplug and replug the device and it will work but if it is left in during a reboot or an initial power on, it is not properly recognized.

Looking at the device manager after a reboot, Windows 10 detects it as a USB COM instead of for example Arduino Micro. Apparently that is why it does not see it as a Human Interface Device. If you upload a sketch with mouse and/or keyboard libraries the device manager then correctly identifies the device as Arduino Micro or Leonardo and the HID features work okay.

This problem is critical for many disabled people such as myself because we rely on specialized Arduino powered devices to assist us in accessing a PC. I don't know anything about USB drivers or HID USB protocols but apparently Windows 10 is sending some sort of different query than previous versions of Windows used and thus it is not fully identifying the device's capabilities.

[NicoHood]

Windows10 uses its built in drivers if no other driver is installed. This could be a problem.
IDE 1.6.6 Added Pluggable HID which also causes problems if the device suddenly changes from Mouse to Keyboard. This is a known issue of Windows.

Maybe this helps?
https://github.com/NicoHood/HID/wiki/Troubleshoot-FAQ#switching-the-hid-core

[cyborg5]

I read the troubleshooting link that you sent and really didn't understand most of it. Uninstalling and reinstalling the device doesn't help. Even if I tell Windows to remove the driver and then reinstall it, the problem persists after reinstalling. This has occurred on two different PCs that were working fine under Windows 8.1. One of them has a device that is an Arduino Micro and the other is an Arduino Leonardo. Upon every reboot of the PC the device is identified as a USB serial device. Reloading a sketch, unplugging and replugging the device, or pushing the devices reset button each can get Windows tend to properly identified as Micro or Leonardo. Somehow Windows 10 is querying the device differently than it did in 7 or 8.1 on the initial boot up.

[NicoHood]

USB2 or 3 Host? With usb hub and what USB version (2/3) is the hub? (yep this is a serious problem/question).

Oh I think I know why. This might be a problem in the USB-Core. A problem that was always ignored.
#3640 (comment)

The correct way is this:
https://github.com/NicoHood/HID/blob/2.2/avr/cores/hid/USB-Core/USBCore.cpp#L99-L115
https://github.com/NicoHood/HID/blob/master/avr/cores/hid/USB-Core/USBCore.h#L117-L135

[NicoHood]

Try this fix (change your arduino core file manually with the new)
master...NicoHood:patch-5

Program your arduino ALWAYS with an HID device then. If this works we need to patch it properly so it changes the ID flexible if CDC is used or not.

Edit: you need the nightly IDE for this! 1.6.6 from the download section.

[cyborg5]

You are assuming a level of sophistication on my part but unfortunately I do not reach :-) To answer your previous questions, both devices were plugged directly into the PC not through a hub. I believe that they are USB 3.0 because both machines are relatively new but I'm not sure if either my desktop or laptop have a combination of USB 2.0 and 3.0. I know some of my ports are 3.0 maybe all of them. I'm not sure where I would apply the patches that you have suggested. And if I understand your reply correctly it means that these devices would always have to be programmed with a sketch wherein they are HID devices. While 99% of the time my particular devices would only be in that capacity, I don't want to make any patches that would limit the usability of these devices for other purposes. I'm not the only person who has experienced this problem. There are other reports in the Arduino forums so this problem should be easily reproducible by someone who is more knowledgeable than I am about USB protocols.

[NicoHood]

For testing. Its only for testing that you should use this patch, to ensure the patch works, because the patch is made for HID devices, not without. If it works we can make the patch better to work with all kind of settings. You want a fix, you need to test it since I do not have windows. I am also no Arduino member, I am just trying to help you with my knowledge, nothing more.

Go to arduino.cc and download the latest arduino nightly build as zip. Extract it.
Replace the file in Arduino/hardware/arduino/avr/cores/arduino/USBCore.cpp with this file:
https://raw.githubusercontent.com/NicoHood/Arduino/9cc7dadb86e92bab817c924c0c6e0a7c5fb6a53a/hardware/arduino/avr/cores/arduino/USBCore.cpp

Restart the IDE, upload an HID program and test if it works.

[cyborg5]

I did not mean to leave the impression I was ungrateful for your help. I can however follow these instructions. I just didn't know what to patch or how. This I can do. I will back up previous file so that I can easily reverse it if necessary. I will report back soon.

[NicoHood]

Since you need to download the nightly IDE there is no need for a backup. After all tests you can just delete the nightly IDE (use the non install zip), use the stable 1.6.5 again and you are fine.

(it would be nice if you, or someone else could remove this email overhead of your comments on github)

[cyborg5]

Great news! I downloaded a daily build this afternoon and recompiled my keyboard and mouse sketches. I had to add

#include <Mouse.h>
#include <Keyboard.h>
#include <HID.h>

in order to get them to compile. But other than that they compiled and now they work correctly. This was tested on my laptop using Arduino Micro and on my desktop using Arduino Leonardo. Both machines were originally Windows 8.1 recently upgraded to Windows 10 which was causing the problem. The problem is now resolved on both machines. Presumably once IDE 1.6.6 goes live this will be permanently fixed. For now the recompile is doing just fine.

Many thanks for all your help.

[NicoHood]

Without my fix???
That is weird. @facchinm have you changed anything that could have fixed that?