I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Thank you!!
dm871 said:
I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Click to expand...
Click to collapse
thank you sooooo much, my sons Eken T10 crashed and was in a boot lock months ago and i had gone through every thread i could find on the web over the livesuite not working unyil i read this!!! Worked a treat
It's alive!
dm871, thank you so much!
I would just add, I had already unpacked version and this was ruining all installation process; I didn't know, where to find that LiveSuitPack_version_1.09_20111101.exe package.
Thats why I'm posting packed version here, it's from Ritmix site. May be someone can't find proper file too.
Windows 7 Pro SP1 x64, now all works well.
Thanks for the directions on how to install the driver on windows 8, I was having lots of issues, because windows 8 does not tell me that is blocking the install of the drivers. I didn't know that windows 8 had the option to reboot into a mode where It would accept unsigned drivers. (This is actually really helpful for me, because it seems I have plenty of other instances where I need to be installing unsigned drivers at work also for lesser known random devices.)
Thank you everyone!
My fault Ainol Novo 7 Legend finally recovered.
doz10us said:
dm871, thank you so much!
I would just add, I had already unpacked version and this was ruining all installation process; I didn't know, where to find that LiveSuitPack_version_1.09_20111101.exe package.
Thats why I'm posting packed version here, it's from Ritmix site. May be someone can't find proper file too.
Windows 7 Pro SP1 x64, now all works well.
Click to expand...
Click to collapse
Thanks!
dm871 said:
I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Click to expand...
Click to collapse
Thank you!!!
My GoClever is alive now! Thanks!
Tank you muchly
dm871 said:
I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Click to expand...
Click to collapse
Thank you so much for the heads up on win8 foibles. I have now managed to get my Scroll Extreme into a 'usable' state
i have done that and the device appeared in device manager but it giving error "code 10 cant start the device "
i am on windows 7 32bit .
My keyboard does not respond when I get to startup settings screen. I tried a command with command prompt and did not help
Related
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.
Like others I have also Black Screen Problems. This is not happening to all apps but especially in games like Temple Run , Temple Run Oz, Drag Racing Bike Edition even Twitter. For Games I can hear sound but nothing is visible in my eyes! I think my Bluestacks is latest (0.8.2.3018), I even make a new windows setup (Windows 8.1 is my OS) but problem still continue. So now anyone can tell me, what next I can really do to solve this weird problem?
Troubleshoot Incompatibility
allursolve said:
Like others I have also Black Screen Problems. This is not happening to all apps but especially in games like Temple Run , Temple Run Oz, Drag Racing Bike Edition even Twitter. For Games I can hear sound but nothing is visible in my eyes! I think my Bluestacks is latest (0.8.2.3018), I even make a new windows setup (Windows 8.1 is my OS) but problem still continue. So now anyone can tell me, what next I can really do to solve this weird problem?
Click to expand...
Click to collapse
I think it's because of Incompatible driver software and/or other Windows Incompatibility issue.. Try to troubleshoot the app and Run under Windows 7 environment with Administrator Privileges or consider updating your driver software for your Video Adapter.. If nothing else works, You can always use Virtualization Softwares like Oracle Virtual Box or VMWare or any other to Create Virtual Environment and Install Earlier version of Windows i.e. Windows XP/Vista/7 or 8 .. Hope it helps..
How did you install Bluestacks on Windows 8.1? I've tried numerous ways and attempts but they all fail during install.
You might be right, I will try to follow your suggestion. Thanks
LossyDragon said:
How did you install Bluestacks on Windows 8.1? I've tried numerous ways and attempts but they all fail during install.
Click to expand...
Click to collapse
Nothing improvising but you will get an error if you don't install Motherboard graphics driver.
How can i backup bluestack data on my PC
How can i backup bluestack data on my PC. any one help me
allursolve said:
Nothing improvising but you will get an error if you don't install Motherboard graphics driver.
Click to expand...
Click to collapse
My motherboard does not have a graphics card in it, but I have the latest driver for my GTX760.
LossyDragon said:
How did you install Bluestacks on Windows 8.1? I've tried numerous ways and attempts but they all fail during install.
Click to expand...
Click to collapse
I've seen many people reporting issues installing apps and other softwares or repacks and kernel dll error.. If this is your case, consider refreshing your windows installation of you've installed 8.1 update from store.. Otherwise you can just perform a fresh OS install.. Hope it helps with you..
Sent from My Canvas 4.. Via XDA premium 4 app
Troubleshooting BlueStacks Black Screen Issue
I would say this problem is most certainly caused by incompatibility or/and outdated graphic card drivers.
You can troubleshoot this issue with a program that comes with BS: C:\Program Files\BlueStacks\HD-GLCheck.exe
Run the program and save the output to a text file for easy reviewing later.
Code:
cmd> "C:\Program Files\BlueStacks\HD-GLCheck.exe" > GLCheck.txt
Open the output log and scroll to bottom to check for errors such as any missing GL_EXTENSIONS.
If you see any missing extension, you probably will be getting a black screen if the app or program required that GL_EXTENSIONS to runs.
A missing extension does not necessary mean your graphic card does not support that extension, it could be as simple as the driver is outdated or does not have the GL feature built-in.
Your can try to update your graphic driver by visiting the links provided below, use the 'Auto Detect GPU' feature whenever the site support it.
Drivers from GPU OEM should be newer than the one provided by your PC OEM.
* Recommend to use Internet Explorer for GPU detection; Java might be needed.
Code:
[url]http://www.intel.com/p/en_US/support/detect[/url]
[url]http://support.amd.com/en-us/download/auto-detect-tool[/url]
[url]http://www.geforce.com/drivers[/url]
[url]http://www.nvidia.com/Download/Scan.aspx[/url]
Good Luck!
Heart_Robber786 said:
I've seen many people reporting issues installing apps and other softwares or repacks and kernel dll error.. If this is your case, consider refreshing your windows installation of you've installed 8.1 update from store.. Otherwise you can just perform a fresh OS install.. Hope it helps with you..
Sent from My Canvas 4.. Via XDA premium 4 app
Click to expand...
Click to collapse
codelover said:
I would say this problem is most certainly caused by incompatibility or/and outdated graphic card drivers.
You can troubleshoot this issue with a program that comes with BS: C:\Program Files\BlueStacks\HD-GLCheck.exe
Run the program and save the output to a text file for easy reviewing later.
Code:
cmd> "C:\Program Files\BlueStacks\HD-GLCheck.exe" > GLCheck.txt
Open the output log and scroll to bottom to check for errors such as any missing GL_EXTENSIONS.
If you see any missing extension, you probably will be getting a black screen if the app or program required that GL_EXTENSIONS to runs.
A missing extension does not necessary mean your graphic card does not support that extension, it could be as simple as the driver is outdated or does not have the GL feature built-in.
Your can try to update your graphic driver by visiting the links provided below, use the 'Auto Detect GPU' feature whenever the site support it.
Drivers from GPU OEM should be newer than the one provided by your PC OEM.
* Recommend to use Internet Explorer for GPU detection; Java might be needed.
Code:
[url]http://www.intel.com/p/en_US/support/detect[/url]
[url]http://support.amd.com/en-us/download/auto-detect-tool[/url]
[url]http://www.geforce.com/drivers[/url]
[url]http://www.nvidia.com/Download/Scan.aspx[/url]
Good Luck!
Click to expand...
Click to collapse
I attempted codelover's method, failed miserably. I get so close to completing it and it fails (Screen capture: http://puu.sh/5AlZo/2065d2082a.jpg ). I guess I can do a system reload to windows 8, install it along with everything else and update to 8.1.
LossyDragon said:
I attempted codelover's method, failed miserably. I get so close to completing it and it fails (Screen capture: http://puu.sh/5AlZo/2065d2082a.jpg ). I guess I can do a system reload to windows 8, install it along with everything else and update to 8.1.
Click to expand...
Click to collapse
See the post title, i was referring to the 'Black Screen' issues.
For your situation, you can try use the Offline Installer to install.
Also check the windows temporary directory for latest BS setup log, the log can tell why the installation failed in the first place.
Why i have black point and quadrate, when i running clash of clans? please help to fix it...
Hello.
I recently purchased Nexus 5 and would have to say it is one of the best phones I've ever owned.
I use Bluetooth 4 on my computers and decided to join my N5 to my computer. I was going through my Device Manager looking for this WiFi adapter I plugged in and noticed I was missing a driver for something. Come to find out, it was for "MAP SMS" which is 'Message Access Profile' for what I believe is to allow me to send SMS with my computer.
At work, I use Lenovo computers and noticed they allowed me to do this kind of thing already on my old Galaxy S3... but I am using Windows 8.1 Pro and my main computer is custom built and not OEM so I appear to be missing such drivers and functionality.
Does anyone know of any drivers that are particular to MAP SMS on Windows 8.1?
Code:
BTHENUM\{00001132-0000-1000-8000-00805f9b34fb}_VID&0001000f_PID&1200
I would normally grab certain parts of the HW ID and go to pcidatabase.com to find drivers but I am not sure how to proceed.
I also did search xda-dev forums for MAP SMS and did not find anything from the built in search. I did do a Google Search for Hardware ID and saw a bunch of unhelpful comments from MSFT staff.
I have Nexus S and on Windows 8.1. Looking for the driver too. I have the same Hardware ID as the one you posted. Please let me know in case you find it.
Need same driver
Though i got an Motorola MotoX
MrDjonez said:
Though i got an Motorola MotoX
Click to expand...
Click to collapse
Hi, I know this is a very late answer, but this worked out for me :
RomanDE replied on March 8, 2014See post history
Close
For Windows 7 64 Bit - testet and works fine on Sony Vaio VGN-TT11WN
Windows requires two important files to install the device - "BthMtpEnum.sys" be found in the directory [root]\Windows\System32\Driver and "bth.inf" be found in the directory [root]\Windows\inf. Before you can install the driver makesure the two files are properly installed on your computer and the Versionnumber is at least 6.1.7600.16385 for "BthMtpEnum.sys" and 6.1.7601.17514 for "bth.inf" . If not then try following: Download the file "BthMtpEnum.sys" from the Internet. I don't remember the adress where i found the file, but i am sure you can find the file quickly with google. Because this is a system file and must be registred as driver from Windows and therefore you must copy and paste the downloaded "BthMtpenum.sys" to your system directory. By default for Windows 7, this is: C:\Windows\System32. If you use a 64-bit version of Windows, you should also place BthMtpEnum.sys in C:\Windows\SysWOW64\. Make sure overwrite any existing files (but make a backup copy of the original file). Finaly reboot your computer. Sometimes it is possible that Windows shows a error message after the reboot. Then try following: 1. Open Windows Start menu and select "Run...". 2. Type CMD and press Enter. 3. Type cd (your root letter, e.g. C or D etc.):\Windows\System32 (example: cd C:\Windows\System32) and press Enter. 4. Type regsvr32 BthMtpEnum.sys and press Enter. When it's done we continue with the 2nd important file. Go in to your Windows\inf directory. Look at the file "bth.inf". If you find the file then go to my install instruction below else if you can't find the file you can manually copy the file taken from another source. You can found and take the file also from Windows 8/8.1 Version wich works fine under Windows 7. Only important is the samebus architecture(32/64) from the Version of Windows you use and the Version of Windows you want to use the file. I had success with the "bth.inf" from a Windows 8.1. You find the filein the same directory as in Windows 7 (windows/inf). Finally, copy this file manually in your Windows\inf directory (e.g. with a usb-stick). Reboot your Computer. When it's done you can install the device with the following instruction :
Install:
1. go in the Device Manager
2. select the Device and right click on it
3. select Update Driver Software
4. select "Browse my Computer... - Locate and install driver manually"
5. select "Let me pick from a list...."
6. unselect "Show compatible hardware" and than click on "Have Disk..."
7. Navigate to your Windows/Inf Directory and select the file "bth.inf"
8. On the left side "Manufacturer" select Microsoft and on the right side "Model" select Bluetooth-MTP-Deviceenumerator and click next to install the driver.
9. Done, enjoy.
P.S. 1. Possible in Step 8 Manufacturer can also named Generic. 2. Before last step to install the driver is possible that Windows show's a warning-info "driver is not digitally signed" - you can ignore this, click yes or next to install this driver anyway - it works fine.
Attention: This is my Interpredation the solution of this annoying problem because I had nowhere found a workingsolution in the internet. The approach has worked for me with the above-mentioned hard and software works. I can not guarantee whether this solution also works with other components. For safety please make a backup of your system beforeyou applying this solution way.
Thank you, i hope i can help somebody
Roman
Click to expand...
Click to collapse
Look for user´s RomanDE reply.
Regards.
Awesome advice, thanks a lot!!
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
Read carefully, this is about the installation of Windows 10 ARM32 on the Surface RT1. Previously tried the Elektrohax tutorial (video on youtube and also posted at Alexenferman.com) but I was unlucky on my attempts.
This is the mentioned tutorial:
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
I followed the instructions but failed twice. Now I know what was wrong. The tutorial IS FINE, it works. The thing is you have to first apply a patched version of Windows RT8.1 and run some scripts, that was fine, now the specifics:
Don't "RUN" the scripts, do not double click, this was the issue on my side. It doesn't matter if you run the script as "Administrator", I repeat, in my case this was the problem, DO NOT RUN or just double click.
INSTEAD, open a CMD window elevated to Administrator privileges. Move to the location of the scripts, this means get into the specific folder, only then run the script.
This means, if you placed the script on a folder named "whatever", right clicking with administrator rights and then execute does-NOT have the same effect as getting inside the folder as in "CD\whatever" and then "name-of-the-script".
I tried several times and I can confirm this is the thing that failed on my attempts.
- - - - - - - - - - - - -
Being that said, that website has all the instructions and links. Follow the tutorial carefully step by step. Keep the files on a safe place, who knows how long those will be kept on the web.
After my failed attempts I tried the chinese tutorial posted on Youtube by cong cheng on his channel. It worked, it even has some scripts working as installer, yes it works BUT after taking a deep look it's a method that applies a set of files made for some Nokia device, while it works, it is in chinese, has some broken things and it is SLOWER than Alexen Ferman method.
In short:
- Chinese - applies an already customized W10 version, way slower
- Alexen - it is an installer, you end up with a much better version
Good luck.
So what did you follow? The forums here seem to contain loads of broken links. Love to try W10 on my Surface since it's only collecting dust in my closet.
Thread edited and updated above and below.
Regarding Windows 10 on the Surface RT (CHINESE TUTORIAL)
I have no idea what's the risk on using a chinese modified pack. This one is different to the one at Alexen Ferman website, here I didn't need to apply all those patches (extras, after finishing the install), instead it worked out of the box. It's the same release as far as I know, but it's been customized.
My experience, what works:
o Edge works, better than IE11
o MyTube works (Youtube works amazingly well on this APP)
o System not as fast as W8.1
o I just clicked "Activate Windows" the usual way and it worked
o Cameras work out of the box (front and rear), no patches needed
o Can run ported apps (Paint.net, Halite, etc).
o YES, you gain access to some other apps on the STORE but hey, read below
X Office was in chinese (preinstalled) and slower, couldn't change it
X Removed it and installed the Office package provided by Alex Ferman
¬ After reinstalling, Office now is FASTER (tested and confirmed)
X No alternative browsers (just some but it's just IE with skin)
X Was kind of tricky to remove chinese (there are still some traces)
X Store doesn't fully work, just allows installing whatever is in my library (owned)
X VLC is way slower and ugly, worked way better on W8.1RT
- XX The Brightness control is kinda broken. You have to disable automatic changes and use only manual (via button), only there you can apply diff real levels of brightness to the screen, BUT, it won't work forever, after a while it will get stuck and you would have to reboot and set it right after going to the desktop.
- XX I'm still exploring this, I don't fully like it to be honest. The touch keyboard works, yes but in my case at times stops making sounds, and also stops working. Unplug and plug again fixes this but... meh.
It wasn't that great, I was actually considering going back to Windows 8.1 RT.
Now the final install I have (Alexen method):
Everything works, you just have to follow the tutorial and you will actually install W10, it's not an out of the box ready image, it is an installer. The only broken thing so far is the brightness control as explained above (it's an issue with the release so it won't go away), and the store didn't work for me, but there is an alternate method to install apps described at Alexen website.
Other than that EVERYTHING is better, it's fast, decent. I'm keeping my RT1 with Windows 10.
Read carefully, follow each step and don't give up. That's all I can say.
I did manage to get this working on my Surface 2 myself, was an interesting experience I don't really have any need for this thing anymore, but I have been pissed about buying a locked out piece of equipment for 8 years, so more just to principal of the thing! Thanks to Alex for all the work.
How do you install office from alexenferman? I tried running setup, but it says this app cant run on your pc. Also have you found a program to un pack .7z packages?
Has anyone written a guide on how to go back to windows rt 8.1?
Kolyei said:
Has anyone written a guide on how to go back to windows rt 8.1?
Click to expand...
Click to collapse
here you have
Alexenferman [OLD] - How to go back to Windows RT on the Surface RT
⚠ Warning:
old.alexenferman.com
does anyone knows if it is possible to put google chrome book on W RT?
Haven't visited the thread until today.
xnappo said:
I did manage to get this working on my Surface 2 myself, was an interesting experience I don't really have any need for this thing anymore, but I have been pissed about buying a locked out piece of equipment for 8 years, so more just to principal of the thing! Thanks to Alex for all the work.
Click to expand...
Click to collapse
Great that you got it working, now that you mention that you don't have any need for the Surface anymore, consider selling it to one of the member of the team working on modifications, unless you change your mind now that your surface works differently. In case you decide to move on, consider posting here on the Discord community
Join the Open RT Discord Server!
Check out the Open RT community on Discord - hang out with 5,903 other members and enjoy free voice and text chat.
discord.gg
mickeyx323 said:
How do you install office from alexenferman? I tried running setup, but it says this app cant run on your pc. Also have you found a program to un pack .7z packages?
Click to expand...
Click to collapse
I simply downloaded the package and ran the Office Installer on the Surface (now with Windows 10ARM), your comment makes me think perhaps, you don't actually have a Surface with Tegra processor, please check. .7z? search for 7zip, that's the program to extract the files from the compressed package .7z
Kolyei said:
Has anyone written a guide on how to go back to windows rt 8.1?
Click to expand...
Click to collapse
Yup, the link was posted by another forum member above.
bikrtoursportugal said:
does anyone knows if it is possible to put google chrome book on W RT?
Click to expand...
Click to collapse
Nope, impossible. They didn't create a binary (executable app) for the platform and the way it's built (the source code) seems unlikely for someone else to do it.
Anyone interested please check the Discord link posted on this message.
ricky4695 said:
here you have
Alexenferman [OLD] - How to go back to Windows RT on the Surface RT
⚠ Warning:
old.alexenferman.com
Click to expand...
Click to collapse
I just got around to reading this. Thank you so much! I'm back on windows rt 8.1. One problem: Secure Boot is still disabled. Is there a way to re-enable it?
Kolyei said:
I just got around to reading this. Thank you so much! I'm back on windows rt 8.1. One problem: Secure Boot is still disabled. Is there a way to re-enable it?
Click to expand...
Click to collapse
You should repart the drive using the official image downloaded from microsoft's site. If you want to come back to completely stock you have to re-install windows using the standard procedure, not the installation through wim file
im having an issue at the installing the wim using the dism. says system cant find the path specified. i verified the drive labels and all any ideas?
can some help me, after successful installed and load windows 10 on surface RT... when i want to run CMD as administrator. it gave an error "The Parameter is invalid".
Looking for some help, I got to the Win10 install stage and keep getting 0xc000000f blue screen error on Win10 boot. From the guide, it says I didn't choose to not copy system files when creating my recovery drive, but I didn't have any other options. I unchecked the only box available. Not sure what is wrong or how to fix. I can't reset, it asks me for my recovery drive, it doesn't accept the drive I created.
Edit: I ended up creating a new recovery drive from my Win10 PC, unchecked the box to copy system files, downloaded the Win RT recovery zip file from MS, copied the contents of that folder into the new recovery drive, copied the Win10 .wim from Alexen to the flash drive, and retried step 4 (I had already installed the hacked RT image and disabled secureboot, etc.). It is now booting, at least getting farther than it did before, after flashing the Win10 image.
Running into an issue right after the installing the patched image I get to the Region and Language select after the reboot and cannot select anything. After a bit the display just goes black. What can I do?