Related
Since upgrading to AS 4.5, I can no longer install applications on my htc Touch.
The error message reads:
"Application Manager cannot intall this application on your mobile device due to an error in the setup file. Reinstall and try again"
Happens with all .exe files and I have re-installed AS4.5 several times and tried "Repair".
Don't think it's an issue with programs that weren't designed for WM6 because I can't install the Sprite and spbGPRS programs from the htcTouch CD
I'm running XP Home SP2 and log on with Administrator privilages
The files install OK on my work PC which runs XP2 Prof SP2 with no Administrator privilages.
Any ideas anybody?
Anybody else...
...having this problem?
http://support.microsoft.com/kb/256020
http://www.google.com/search?source...an+error+in+the+setup+file&btnG=Google+Search
maybe
Been there, done that
no answers anywhere I can see.
The Microsoft site only applies to specific programs, like the Media Player one you pointed to or Powerpoint.
Only thing I can find is possibly the .ini file doesn't have the correct version notation for instance it states version 1 instead of version 1.0
That still doesn't explain why they all install on the PC at work though.
Both PCs running AS4.5, both running Windows XP
i dont really thing activesycn is good at cleaning up after itself when reinstalled and or uninstalled
i've seen lots of files in it's dir
and lots of registrys it leave behind
a good cause would go and hunt them down and make sure
that a reinstall is really a reinstall
Windows Mobile 6 SDK refuses to uninstall. I had previously installed MSVS 2008 and Windows Mobile 6 SDK. I, apparently, did not uninstall the SDK, but did uninstall MSVS. I reinstalled VS08 and tried to repair Windows Mobile 6 SDK. The repair would almost complete then an error would pop saying that the Cellular Emulator is in use on COM4. I uninstalled the Device Emulator and VS2008 and this error persists. I don't think that I have anything running on COM4 and I have no way of checking. Please help. This is driving me insane.
Try uninstalling from the safe mode. Also, use Revo Uninstaller as it can clear out leftover regkeys and files (best to run it from the safe mode as well). Finally, get the Windows Installer CleanUp Utility to remove any leftover MSI databases of VS/SDK/etc. Reboot.
Btw, Process Explorer can help you track down and close those pesky processes, in-use files and dlls.
--
This is one of the reasons why I prefer using portable apps. No install/uninstall/conflicts. PM me if you're interested in a portable WM6 SDK.
Thank you for your help. The Windows Installer CleanUp Utility did the trick.
please close device emulator if it is running
i am not able to install wm 6.0 sdk, the error is
"COM4 is in use please close device emulator if it is running and then retry"
could some one help me doiong this...
thanks in advance...
thanks
Prashanth
I am experiencing this same error when trying to install the WM 6.5 standard emulator. Did anyone figure out a solution for this?
i have this problem too
Remove WM6 SDK problem
I know this tread is a little old, but i just had the same problem and found the solution, maybe others with the same problem come accross this thread as i did.
source: h t t p : / / faqs.edujini-labs.com/55_12_en.html
# Go to your device manager. My Computer -> Properties -> Hardware -> Device Manager
# Go to the entry of "System Devices"
# Towards the end, you will find an entry "XPVCOM" (XP Virtual COM Port, I guess). Uninstall it.
You will see this entry only when you get the error "COM<X> in use, please verify".
# Now, go to the folder where you have the Cellular Emulator. The default location is "C:\Program Files\Windows SDK 6 Professional\Tools\Cellular Emulator".
# You will find a utility InstallXPVCom.exe. At the command prompt, execute the following:
InstallXPVcom.exe Install
# Try uninstalling again, it will work.
Thanks!
[email protected] said:
I know this tread is a little old, but i just had the same problem and found the solution, maybe others with the same problem come accross this thread as i did.
source: h t t p : / / faqs.edujini-labs.com/55_12_en.html
# Go to your device manager. My Computer -> Properties -> Hardware -> Device Manager
# Go to the entry of "System Devices"
# Towards the end, you will find an entry "XPVCOM" (XP Virtual COM Port, I guess). Uninstall it.
You will see this entry only when you get the error "COM<X> in use, please verify".
# Now, go to the folder where you have the Cellular Emulator. The default location is "C:\Program Files\Windows SDK 6 Professional\Tools\Cellular Emulator".
# You will find a utility InstallXPVCom.exe. At the command prompt, execute the following:
InstallXPVcom.exe Install
# Try uninstalling again, it will work.
Click to expand...
Click to collapse
This worked for me, thanks a bunch. I had tried uninstalling XPVCom but didn't realize re-installing it would make it work.
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.
Has anyone else using XP had any issues installing the USB Driver for the Magic? I've tried every possible method to get it to work and it just will not install. A method that appears to work for some is in this link-
http://www.mail-archive.com/[email protected]/msg09692.html
Although this did not work for me. There was also a suggestion of copying the inf file and renaming certain strings by one digit. Any suggestions?
I used the latest SDK with the included driver. Set the environment paths. Nobody has any other suggestions?
renaming the inf file solve the prob for me.
radonsg said:
renaming the inf file solve the prob for me.
Click to expand...
Click to collapse
What did you rename it to? I renamed it to android_usb_Magic.inf like the linked post said.
Hi Gimpeh
This worked perfectly for me. The issue was once it installed the Windows drivers there was no way back. However, follow this
So you plugged your Android phone into your Windows machine having forgotten to switch on USB debugging…
Menu > Settings > Applications > Development > USB debugging
Then Windows detected your device as a USB-Mass storage device and won’t change the settings, regardless of how many times you uninstalled the device. Thread on it here.
This solution worked for me and didn’t require editing the registry settings (I don’t know if the reboot is unnecessary).
(1) Plugin phone
(2) Uninstall any drivers that mention “HTC Android Mobile USB Device”
(3) Unplug phone and restart
(4) Install and run USBDeview
http://www.nirsoft.net/utils/usb_devices_view.html
(5) Using USBDeview find the Android device (for some reason Windows hides uninstalled drivers instead of deleting them), right click on it and uninstall.
(6) Follow the official instructions to the letter this time.
http://developer.android.com/guide/developing/device.html
Click to expand...
Click to collapse
http://blog.zedray.com/2009/06/16/when-adb-won’t-detect-your-android-phone…/
Good luck!
This is pretty close to the instructions I followed earlier. No resolution. All HTC device drivers have been removed. Although there is a composite USB device installed (not labeled HTC). I know sometimes if windows does not recognize a device it will show it as a composite.
Install HTC Hotsync - http://www.htc.com/sea/SupportViewNews.aspx?dl_id=573&news_id=169
Have your phone plugged in first then install the app. You don't need the additional drivers it list. Just the Hotsync program.
That did the trick for me.
edit the inf file under the x86 folder inside the usb driver.
replace the vid_0bb4&pid_0c02 with vid_0bb4&pid_0c03
cos somehow my htc is recongnise as vid_0bb4&pid_0c03 instead of vid_0bb4&pid_0c02.
Hotsync didn't work and neither did replacing the string from 02 to 03. I got it to recognize at work on a Vista machine but since then it will not recognize on my home XP or any other Vista machine. When I select Have Disk and select the INF file it says something to the effect of There is no driver information for this device.
Additional Note: Although the device was recognized on that one vista machine, it would not recognize when it was in HBOOT mode.
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
radonsg said:
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
Click to expand...
Click to collapse
CTRL+F Put in that key and found nothing.
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Cheesebaron said:
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Click to expand...
Click to collapse
How would you go about flashing the recovery.img in Ubuntu. I didn't see any drivers for linux.
Driver
http://developer.android.com/sdk/1.5_r2/index.html
Additional work for linux(add rules)
http://developer.android.com/guide/developing/device.html
I finally figured the damn thing out. For some reason windows recognized the ION as a Video device and installed it as such. I figured it out after I got irritated and just uninstalled everything that wasen't plugged in.
woa.
TT is strange. Which version of windows? vista or xp?
Its XP Home on a HP Mini. I'm glad I finally have it figured out. I've probably spent 20 hours on this issue alone. I even went to Ubuntu since Windows was being...well windows.
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