[Q] 64 bit driver for win 7 - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Everything was cool on my old 32 bit win 7 computer. I got a new computer, and I can no longer see my Archos 101 G9 in windows explorer. I can get adb to connect fine, but it can be tedious for transferring lots of files. Anyone successfully get this to work on 64 bit windows 7 for anything more than just adb?

---

I hate commenting that I don't have this issue. Do you have the latest media player? At least I remember that media player includes the mtp drivers. If you look at device manager, can you identify the tablet? If yes, you could try removing the tablet driver. After that the next time you plug your archos to your PC it should reinstall the drivers.
You can also Google apps that enable UMS. SGS3 easy ums works on my phone. I haven't tried them on my tablet, though.
Sent from my GT-I9100 using xda app-developers app

---

I wonder if there is some other driver issue. It keeps pretending that it's my GS3 that's plugged in, and I can't figure out how to convince it otherwise. It also doesn't get the MTP part, and AFAIK I have the latest WMP installed, however, that doesn't recognize the device either.

---

ProfLonghair said:
I wonder if there is some other driver issue. It keeps pretending that it's my GS3 that's plugged in, and I can't figure out how to convince it otherwise. It also doesn't get the MTP part, and AFAIK I have the latest WMP installed, however, that doesn't recognize the device either.
Click to expand...
Click to collapse
So your archos appears as GS3? Delete the driver/device from device manager. Maybe it will get right driver after that.
Sent from my GT-I9100 using xda app-developers app

---

That's just it: I tried uninstalling that, and removing the drivers, and it still shows up like that, even after a reboot. I'm going to try to track down the specific files in the S3 driver and remove them manually this evening, maybe that will help.

---

Try a different USB port if possible. Win doze sometimes gets this area wrong.
Sent from my ARCHOS 80 COBALT using xda app-developers app

---

ProfLonghair said:
Everything was cool on my old 32 bit win 7 computer. I got a new computer, and I can no longer see my Archos 101 G9 in windows explorer. I can get adb to connect fine, but it can be tedious for transferring lots of files. Anyone successfully get this to work on 64 bit windows 7 for anything more than just adb?
Click to expand...
Click to collapse
If you can connect with ADB then the device is set to use developer Debug mode.
Go into settings on the Archos tablet and turn off the Debug mode and then it should try to connect normally as a MTP device. You then may need to turn off or reboot both the computer and tablet before connecting it again.
Also, when trying to un-install a USB driver you may need to have it plugged in for it to show up in Device Manager. Then when you select to uninstall the driver you need to unplug the device and reboot the computer to allow it to clear out the old driver first.
Oddly though, on mine, it still works with the tablet set in either mode, but I do not have any ADB driver installed on my Win 7 64bit computer (yet), nor do I have any drivers for a cell/smartphone installed on it either. So, could be some other driver conflicts from other things on your end.

---

win 7 64 bit
I had the same problem, Archos has the wrong info.
[Google.NTx86]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
[Google.NTamd64]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
&PID_1509 is the correct identity for G9 tablets. Thank cajl for providing the fix. Link to post. --> http://www.modaco.com/topic/347961-anyone-got-good-adb-drivers-for-g9-80/

---

stevemp said:
I had the same problem, Archos has the wrong info.
[Google.NTx86]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
[Google.NTamd64]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1509
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
&PID_1509 is the correct identity for G9 tablets. Thank cajl for providing the fix. Link to post. --> http://www.modaco.com/topic/347961-anyone-got-good-adb-drivers-for-g9-80/
Click to expand...
Click to collapse
Not sure what that's all about, but I had just downloaded the ADB USB Driver right from the Archos website and it worked in both Windows XP and Windows 7 64-bit. Here's roughly the same sections as you listed, but from the .inf file from Archos:
[Google.NTx86]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1501
... several other things here
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
... several more things here
[Google.NTamd64]
;Archos Gen9
%SingleAdbInterface% = USB_Install, USB\VID_0E79&PID_1501
... several other things here
%CompositeAdbInterface% = USB_Install, USB\VID_0E79&PID_1509&MI_01
... several more things here
Notice that it has 1501 in the first line of each section, but then has 1509 in the line further down. Don't really know what difference it makes (nor do I really care) because the ADB USB Driver file from Archos worked fine for me.
But the original poster said ADB was working... just could not get a 'normal' MTP connection to work for transferring files. Which makes no sense at all unless they have developer Debug mode turned on in the tablet set. If Debug mode is not on, then both Win XP and Win 7 should just automatically find and install an MTP driver (since that's the crappy file transfer method Microsoft wants everyone to use).
The MTP drivers just auto-magically installed on both of my computers by just plugging in the USB cable to the tablet (with Debug off). So, I have no idea why the original poster (and several other people) have problems with getting that side of things to work.
Good luck figuring out what's going on with that. Sorry I can't be of any help because I've never had that problem.

---

Got it!!!!!
I deleted two files from c:\winsows\system32\
WinUSBCoInstaller.dll
WinUSBCoInstaller2.dll
and, in c:\windows\system32\drivers
I had removed
WUDFRd.sys
(actually, renamed to WUDFRd.bak, but whatever)
and restoring that one file, with deleting the other two, and I can see the stupid thing now!
Thank you for the attempts at help. I saw tons of different things on tons of different sites, not 100% sure which which one caused me to rename that file, but hey, it's working now, and that's the important thing.