I have windows 10 and it won't correctly recognize my gadget II. It keeps showing up as a disk drive, not an I/O device

How exactly did you install the driver and which driver?

You should be able to manually install the device driver through device manager from the Program Files\ETC\HighSpeed_Pipeline_Drivers location. If you need assistance with this process, just ask.

I've installed ETC Nomad 2.5 software. I tried doing the manual driver install that you refer to. When I go into the windows device manager the Gadget is recognized as a disk drive called "FSL FREESCALE MSD USB Device". Windows will not recognize the device drivers in the folder and will not let me pick a driver that is not a disk drive device driver.

Are you sure that's the gadget? If you unplug the gadget, does the disk drive disappear from list? If it doesn't you are not looking at the right item.

Can you post here a photo of the entire Hardware Manager List ?

it is definitely the Gadget. It disappears from the list when I disconnect/unplug. The drive shows up in explorer named as BOOTLOADER with one file on it named READY.TXT

Here are screenshots of explorer and the entire device manager list

If it means anything, the Gadget also mounts as a disk when connecting to a mac. Same name BOOTLOADER

Your Gadget is in bootloader mode and likely needs firmware loaded to continue. This can happen if a firmware update on it gets weird. Copy C:\ETC\nodesbin\14d5.0114_Gadget_II_v1.1.0.9.0.4.S19 to this drive (right click, copy, then right click, paste when inside the drive). Once that is complete, unplug and replug the Gadget.

Edit: you can also use v1.0.0.9.0.10 if available on your computer instead of 1.1.0

Let us know how that goes!

Ok, did that, no change. It still connects a a drive.

It's likely time to give your local ETC Tech Services office a call. It should recover after a firmware reload. In the US, that would be 800-688-4116 and ask for phone support.

Sorry we couldn't solve it on the forums!

Thank you.

I've used Hans' method to resolve the same issue while updating firmware from Windows 10 on at least two Gadget II devices; it worked for me.

Also, worth mentioning that the same "Stuck in Bootloader" problem can occur when updating the firmware on an Eos Programming Wing, and the same general solution worked for me in resolving it.  However, the Wing requires a different .S19 file from Nodesbin, in my case 14d5.0115_IO_Kinetis_4port_v1.2.0.9.0.7.S19.  This may be worthy of note because unlike the Gadget, it isn't clear from looking at the list of file titles in Nodesbin which is the correct one for this device.

Can't confirm whether all hardware versions of the Wing require the same Kinetis 4 port S19 file, so contact ETC Tech Service if you're unsure.  The module once updated shows up again in Shell > Maintenance > Firmware Updates as "Four Port I/O Board H/S".

Hope that helps.

Ric