Database Info

Fastboot not working with windows 7 beta

I recently crashed my vista hard drive and decided to give windows 7 a try, its working wonders right now. The only problem is that I'm trying to put Nandroid back up on my computer again. I am at the step of trying to get the fastboot loader. It worked on Vista, but now it is saying that the "Driver is not intended for this platform." Is that due to windows 7? Is there a work around for this? Any help would be amazing, thanks.

I used Fastboot on Win7 7100 build yesterday, and it worked fine. Did you set everything up according to this post:
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
This is all that I did, and everything worked flawlessly. Good luck.

hmm..yeah, i did do everything according to the tutorial exactly, do you have email, aim, gmail, etc? could you help me?

use the newest driver in this SDK..
http://developer.android.com/sdk/1.5_r1/index.html
If you dont see the ADB Device or whatever its called in the device manager you need to delete a generic volume and scan for hardware changes.... HTC talks about it here. I had to do it also...
http://www.htc.com/www/support/android/adp.html
Troubleshooting
fastboot.exe (on Windows) doesn't detect the ADP device properly
In some cases, Windows detects the ADP1 bootloader as a USB mass storage device, preventing fastboot.exe from accessing it. To resolve the issue, you can dissociate the USB Mass Storage driver from your ADP1 on your Windows machine and install the proper driver instead, as described in the steps below:
1. Boot the device into fastboot mode, as described above, and connect the device to your machine over USB.
2. Navigate to Start > Control Panel > System > Hardware > Device Manager > Universal Serial Bus Controllers. Observe that the ADP device is listed as a USB Mass Storage Device.
3. Right-click USB Mass Storage Device and select Uninstall. Windows then prompts you with a "New Hardware Found Wizard" message. If Windows doesn't prompt you, you can manually re-detect devices by selecting Action > Scan for hardware changes.
4. Install the USB driver included in the Android SDK, as described in Setting up a Device for Development on the Android Developers site.

thanks southsko, i'll try this and let you guys know how it works.

I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?

When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?

i had the same problem earlier tonight, i figured since i was running win7 i might as well try using the virtual xp out. I started the VM up and the attached the phone using the drop downs and it worked flawlessly.

yup .. it's working fine for me too.. if you are using 64 bit version ... u need to use the 64 bit usb driver too... u can get it here
http://forum.xda-developers.com/showthread.php?t=446274
Also you may have trouble installing it in Windows 7 unless you turn off driver signing at boot menu. Hit F8 and select no driver signing and you should be able to install it no problem... u will also have to disable driver signing each time you plan on using adb/fastbboot

foxlin said:
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
Click to expand...
Click to collapse
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.

trmacdonal said:
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
Click to expand...
Click to collapse
I am in bootloader mode, and I am an admin. It didn't give me the option to install it anyways. That is interesting. I am currently still using the windows 7 beta. I have tried manually selecting the specific driver files. It is still not working, any other ideas?

I finally got it! thanks everyone. The solution was instead of having it search through the files, there is actually an option below it to pick the driver from a list, the list wasnt the right one originally, then i manually changed the directory and it worked. Thanks for the help everyone!

billc.cn said:
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
Click to expand...
Click to collapse
How come when I installed this on Beta I got the message that I could not install a non-digitally signed driver? I was not able to install it myself until I disabled it at boot... maybe the 32 bit version is signed.

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?

Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim

Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?

More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!

Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.

Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck

JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device

I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.

I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.

One thing I forgot. Do not unplug your device between uninstall and hardware scanning.

AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.

rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim

jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!

rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

Samsung Device Drivers?

My pc wont recognize my infuse. I looked for a cd and went to the site and nothing available. Can someone point me to samsung drivers for this device?

I just rooted my Infuse.
I used the SOC pack with the drivers and used those. 0 Problems. If you don't want to root at least you can use the drivers for whatever you need.

Not sure how to intall those drivers on my windows 7 64 bit.
First time with a samsung and I ran soc and it failed saying device not found.
Usb debugging selected etc
Update: Started working..seems that I am now rooted

I used Win 7 32bit. I had to go to device manager and had to do the manually update drivers dance a couple of times to get all the devices installed.

You can also just download the captivate drivers or the samsung update exe.

Just install the latest version of Kies then plug your phone in. All set.

Download & Install Kies here:
http://www.samsung.com/in/support/mobilesoftwaremanual/mobilesoftwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
Once it is completely installed, then plug in your phone. Windows 7 (64bit) will automatically recognize it.
You can proceed with root (superoneclick) from there. Won't work w/o the drivers.

argylesocks said:
Download & Install Kies here:
http://www.samsung.com/in/support/mobilesoftwaremanual/mobilesoftwaremanual.do?page=MOBILE.SOFTWARE.MANUAL
Once it is completely installed, then plug in your phone. Windows 7 (64bit) will automatically recognize it.
You can proceed with root (superoneclick) from there. Won't work w/o the drivers.
Click to expand...
Click to collapse
Thank you, i was looking for this link.

thanks.

Infuse Drivers
Here is a link to the drivers I used to root my infuse. Got them right off of the Samsung Infuse support page (click the software link next to manuals):
http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT

Any official fix for MTP driver installation failed?

I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it

I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2

thats nice but it doesnt exactly do anything for my problem

Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app

This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.

I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..

I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything

I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2

Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck

I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS

Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite

How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:

Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps

[FIX] USB Tethering lags/freezes on windows 8.1

Everytime i tried to use USB Tethering with my Xperia U on my Windows 8.1 (Bing's single language Edition [Genuine Licence]) have always lags or even freeze the taskbar and some other tool settings on my operating system. After some testing and googling a little bit i found a solution for this Microsoft Issue: Update your NDIS 5 Driver to NDIS 6.x.
Verify if your device is using RNDIS 5 driver (1):
Open Device Manager from Control Panel and expand “Network Adapters.”
Plug in your device and enable USB Tethering so that the device is detected as Remote NDIS based device.
This should now create a Network Adapter named as “ [Your Device Name] Remote NDIS based [internet Sharing/network] Device.”
Right-click the Adapter and select Properties.
Select the Driver tab and then click Driver Details.
You can see the driver files if the files are named usb8023x.sys and rndismpx.sys you are using RNDIS 5 Driver.
Updating your driver:
Option 1: Update your driver NDIS driver manually by selecting the driver's list option on windows wizard driver's update. Unselect show all compatible hardware option, you will get a Microsoft's driver list. You should seek for a RNDIS 6 USB device and click next. This should work on 32bits or 64bits edition.
Option 2 (64 bits only)(2): Just Download and update your NDIS driver from the attachment below. On Driver's Wizard installation must go through selecting the driver from a list.
Sources:
http://support.microsoft.com/kb/2923775 (1)
http://www.driverscape.com/download/remote-ndis-compatible-device (2)
https://msdn.microsoft.com/en-us/library/windows/hardware/dn449742%28v=vs.85%29.aspx. Microsoft says NDIS 6.4 is included on Windows 8.1, don't know why windows chooses RNDIS 5 over RNDIS 6 on my laptop.

Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards

MHP2013 said:
Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards
Click to expand...
Click to collapse
Try this before installing the NDIS 6 driver:
http://www.tomshardware.com/faq/id-2165451/dont-windows-windows-automatically-download-device-drivers-icons.html
If above didn't work try to disable driver signature verification:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/

Perfect, Thanks for this fix! Didn't need the driver as RNDIS6 driver is already included in Windows 8.1
NDIS Compatible works without huge driver lockups, but RNDIS6 USB Adapter also works like a charm. (Nexus 5)

Facing the same problem, here.
Tried both options, still facing the same problem..
Any ideas?

I am having the same issue in Windows 10 64-Bit.

Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.

Ano59 said:
Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.
Click to expand...
Click to collapse
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?

DubleJayJ said:
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?
Click to expand...
Click to collapse
As OP said, manually select the proper driver.

Windows 10 best solution: rename the RNDIS5 .inf file
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver

Something is not logical in this tutorial :
The content of the inf file in the attachment is rndiscmp.inf; but this file is already in Win8.1 system (C:\Windows\Inf). Hash are similar
This could explain why windows refuses to install it again and says "the last drivers is already installed"
Renaming extension of wceisvista.inf doesn't work for me in Win 8.1
Maybe you could tell us the name of driver files when using RNDIS 6 Driver ...

This thread is also important for resolving playability issues with the game XCOM 2, so thank you very much for the fix to a problem completely unrelated to Android You guys are awesome!

Thanks, worked for my Galaxy S6.

You can use one of the below drivers from that list. One of them may work, try them all:
USB RNDIS Adapter
USB RNDIS6 Adapter
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device > this was the one that worked for me

inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank You :good:

Thx! Worked!! Windows 10 64 bit.

Hi guys, i get some issues here where it looks like i have only NDIS 5 on my windows 10.
I tried manually select driver, but i can only see this one : Remote NDIS based Internet Sharing Device
i tried inkaine's method, usb8023x.sys is still there but rndismpx.sys is missing. So i think i'm still using this annoying NDIS 5.
I don't understand why it's so hard to update this driver.. :silly:

inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank you so much. This issue has been bothering me for years and your solution along with OP's solution helped me. Thanks

Hey ive been having this issue for a while now and im using a htc one m8 to tether with but for me it wont let me manually update the drivers or modify the wceisvista.inf im using windows 10 pro as well.

Windows 10 fix - Worked for me
Hello all,
None of the steps worked for me, however i followed one more set on steps that i found on the net (unable to post links yet )
anyways, the steps are
Open Device Manager (right click on Computer > Manage > on the left side, under System Tools choose Device Manager)
Choose the problematic device in Network Adapters (for me it's called HTC Remote NDIS based device)
Right click on it and choose Update Driver Software...
Click Browse my computer for driver software
Click Let me pick from a list of device drivers
Uncheck the box Show compatible hardware
For the manufacturer, choose Microsoft Corporation
Now you will have two options:
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device
I chose the second one and it solved the problem, but if it doesn't work you could try the other one. In my case, the driver that was being used was neither of these, but a special driver from Android SDK ADT bundle.
Pick one and click Next.
If a dialog comes up, confirm by clicking Yes.
Wait a few seconds for the connection to restart. If it doesn't work, try disabling and reenabling USB tethering on the phone, or reconnect the USB cable.
PS: Microsoft Corporation or Microsoft Inc. or Microsoft might be present in manufacturer. search among the three