UPDATE:

I got it to work! I booted the computer up with disabled Driver Signature enforcement, went through the control panel, and updated the driver through there...like I guess it's supposed to be done. Thing is, I went back to Windows 8, then back to 10 and this was the first time trying to load the driver since switching back to Windows 10. I selected to browse for a driver myself, then bypassed all the warnings Windows gave about the drivers and such. I dunno. I got it to work.

This problem was a nusiance to me, too - I had to use a WIndows XP laptop to do all my SRAM backing up, etc for quite a while using an ancient old laptop.
Anyway, disabling driver signature enforcement on Windows 10 works for installing it, and it is sometimes required for using it as well, which is unusual and frustrating and seemingly random so far.
Anyone else had anything similar?

I got it to work! I booted the computer up with disabled Driver Signature enforcement, went through the control panel, and updated the driver through there...like I guess it's supposed to be done. Thing is, I went back to Windows 8, then back to 10 and this was the first time trying to load the driver since switching back to Windows 10. I selected to browse for a driver myself, then bypassed all the warnings Windows gave about the drivers and such. I dunno. I got it to work.

I've had similar problems when using a usb 3 port. Switching to a usb 2 port fixed it for me. I guess you could also try to disable usb 3 in bios.

Well shit I am sorry. All I can say is I have a Win 10 x64 Partition and have no problems with either the 3.0 or 2.0 ports on my computer. I know I had to install the drivers separately for each type of port though.

I'm sorry to hear you are having so many troubles. I know it was a bitch to get working in Win 8.0 for me, and had a similar issue, but eventually one of the driver signing steps fixed it for me.

I'm having problems with this, too. I made the switch to Windows 10 last night and have been regretting it because of this stupid problem. When I first got Windows 8 it gave me similar problems then magically started recognizing the USB cart. I've tried disabling the driver signature enforcement through the settings->reboot process that DropMontage mentioned - the same way I did it in Windows 8 - but it didn't make any difference. Gonna check out that Android app.

The android app is great! allowing you to dump saves and transfer, taking your handled experience on the go even more so. I'm sorry you're experiencing trouble with the pc, again I rarely do these operations, mainly only when I patch kits on  a new lsdj udpdate

You can open cmd as an admin and try this:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

and then try and install the drivers

EDIT: There is also this guy to sign the drivers.

http://www.ngohq.com/?page=dseo

Which you can follow this guide:

http://www.hkems.com/files/EMSlink/64bi … _Guide.pdf

Its listed on Kitsch's page

I just tried both of these methods, nothing.

It's not a signature issue, it just isn't even recognising that the drivers are there.

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

and then try and install the drivers

EDIT: There is also this guy to sign the drivers.

http://www.ngohq.com/?page=dseo

Which you can follow this guide:

http://www.hkems.com/files/EMSlink/64bi … _Guide.pdf

Its listed on Kitsch's page

I put up a quick tut for 8.1 and 10, this only temporarily disables driver signature enforcement, so you'd need to do this any time you wanted to link up. you can disable them permanently and run your PC in test mode, but this isn't entirely recommended. http://chipmusic.org/forums/topic/17108 … indows-10/ I'm usually only doing this when patching samples, other times I'm using the EMS link on Android.

Yours is the tutorial I followed!

Yeah I'm going through device manager.

http://chipmusic.org/forums/topic/17128 … ows-howto/