I was just working through this issue the other night. What I found (in my situation) was that the driver that Win10 is auto-updating for the USB-->serial/consult cable is not correct for the actual chipset in the cable itself. I am at work right now, so I can't recall all the names and such, but yeah, I had to download and install and outdated driver for the cable, and then everything worked perfectly.