Teensy 3.2 - Unable to proceed with programming controller

[mrhead]

Edited title as it isn't restricted to Windows 10 only.  Still having no luck as of 6/20.

After some time trying to get Windows 10 to pickup the Teensy controller, I've given up.  Searching the forums and the internet have not yielded any successful tips, so I'm coming to you guys.

When the LED flashes on/off, the controller will show up under 'unspecified' portion of devices/printers area as TeensyduinoRawHID - when I attempt to manually force the driver install it doesn't seem to work.  I'm a computer tech and do know what I'm doing.  It will list it under Device Manager as USB Composite Device - even though it's showing up differently under Devices & Printers.  When I hit the button to reset it, it then redetects (w/o option to select driver) it as USB Input Device.  When I use the zadig utility and try to install the WinUSB drivers it doesn't make a bit of difference either.

I was able to get the Zadig utility to pick up the 'TeensyduinoRawHID (Interface 0)' and 'TeensyduinoRawHID (Interface 1)' but installing the driver selecting either doesn't make a difference.  When I reset the controller, I can choose the USB Input Device and manually install the driver, but it doesn't change anything either.  Basically, my attempts to program/flash are unsuccessful because the utility will not recognize the device.

[mrhead]

As an update, I removed the headers for the rows & columns from the teensy, just so I could eliminate that from the equation.  The teensy comes up with the flashing LED as normal and will respond when I push the button to put it into program mode.  I booted up a Windows 7 machine and the Teensy Loader utility does recognize the controller (not in Windows 10 though).  I am still unable to do the 'reflash.bat' step as it sits at the 'did you forget to press the reset button?' or whatever it says.  I've tried manually installing various drivers, but nothing seems to get me anywhere.

What am I missing?

[PJE]

There have been times with certain devices where the use of USB 2 or USB 3 influenced whether a unit could be programmed. I'm not sure if this type of issue is affecting you...

[Data]

There have been times with certain devices where the use of USB 2 or USB 3 influenced whether a unit could be programmed. I'm not sure if this type of issue is affecting you...

That's a real thing but it's not a problem for everyone.  For some reason it works more reliably to program the Teensy from a USB 2.0 port.

I'd also verify that you don't have a counterfeit Teensy.  Did you buy it directly from PJRC?

[mrhead]

There have been times with certain devices where the use of USB 2 or USB 3 influenced whether a unit could be programmed. I'm not sure if this type of issue is affecting you...

I tried a few different cables, all of which were usb 2.0.  I also tried both 2.0 and 3.0 usb connectors on my computer.  I read the thread a while back regarding this - didn't seem to make a difference.  Thanks for responding!

That's a real thing but it's not a problem for everyone.  For some reason it works more reliably to program the Teensy from a USB 2.0 port.

I'd also verify that you don't have a counterfeit Teensy.  Did you buy it directly from PJRC?

I purchased the teensy from Amazon (through Sports Internet Solutions LLC).  There weren't any negative ratings and everyone who did state theirs worked with no issue.  I didn't think much about the possibility of buying a counterfeit controller until after I received it.  From appearances and labelling, it does appear to be authentic.