I am starting to lose the plot on this one. I've got an Uno R3 and a Mega 2560 R3, and both are exhibiting the same problem: I cannot get Windows 7 (64 bit) to install the drivers. I know that the Arduinos are OK because I can access them using a Linux VM on the same Windows 7 machine, but the Windows machine itself won't connect to them.
I've tried all of the tips I can find online, I've turned off driver signing, everything I can think of, and it just will not work. The Arduino will be communicating with a .NET program on the PC, so I really need to get it working!
Any suggestions gratefully received while I still have some hair left! TIA.
Thanks for the suggestion, but I’ve manually re-installed the drivers many times without success. It gets right through the install procedure, asks if I want to install an unsigned driver, I click OK, then when it completes it brings up a message saying that it couldn’t install the driver because it wasn’t signed.
That's weird, win 7 x64 should allow unsigned drivers with a warning. Can you try to find a setting for that behavior? like "allow unsigned drivers" but not that boot option, something in the control panel/PC properties.
My installer does not messes with anything, I don't like that too, the only thing I modify is the program files directory + PATH (but it is cleaned upon uninstallation)
That setting is not there by default in Windows 7 64-bit, I had to go into Windows\inf\sceregvl.inf and add stuff to enable it, but that doesn't make any difference. I am currently trying to change the group policy to ignore unsigned driver errors.
A "standard Windows 7 install" doesn't say anything about other (network) policies that may be installed. You had mentioned earlier in the tread that this is a work computer. If there are group policies in place (something that many offices will implement on their machines), than more than likely that's the culprit. A stand-alone, no policies, non-cripled, no bacon, no ice-cream Windows 7 install will allow unsigned drivers to be installed after approving the warning pop up. To me it seems you have a policy installed that's preventing that from happening, regardless of you approving the pop up message.