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.
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
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.
I unistalled HTC sync and when I try to reinstall I get the message "1152: Error extracting C:\Users\Dada\AppData\Local\Temp\{1B4A9E0 PC Suite.msi to the temporary location" (the #'s and characters after temp are always different)
Anyway I've tried:
1) Running the installer as administrator just in case.
2) Right clicking the install file and installing it using the 'troubleshoot compatibility' option. Same error code.
3) Searching for any remaining files using windows search for 'htc' yet no results.
4) Searched other threads and heard repairing the file or deleting it will fix the problem yet I can't find the above folder, specifically looking in the 'dada' folder for the 'appdata' folder, not there. Then searching using windows search for 'appdata' yet no results found
I am using Windows 7 64-bit and HTC sync 2.0.40. My user account "Dada" is set as the administrator. Using a rooted EVO4g with freshevo 3.4.0.1(not that my phone should matter). Rooted perfectly with this method, since been outdated but not when I rooted. http://forum.xda-developers.com/showthread.php?t=765496
HTC sync and the root worked fine the first time, so I know its compatible with my computer. Something must have happened when I uninstalled it using uninstall programs under control panel.
Obvioulsy I'm not a computer programmer, can anyone figure this out. Thanks.
1152 HTC Error FIXED!!!
I encountered the exact same problem w/ my new HTC Aria when trying to install the HTCSync.exe file. I went to CNet and downloaded a free registry cleaner. Once downloaded, run a 'FULL SCAN' then click on the 'FIX ERRORS' tab for them to be repaired. Once they're repaired, goto HTC, then whichever support area depending on country and select your phone type and GO' ,to the right of the drop-down,. Next, open the 'DOWNLOADS' tab and enter your Serial number from your HTC phone and submit. Below your Serial number a 'DOWNLOAD' will be available. Click it, either open or save the file. Once downloaded, try again reloading the HTCSync.exe file snd it should resolve all your problems. G'day
All about the registry cleaner
Worked like a charm. Thanks.
What's frustrating is before I even posted the original question I tried using a registry cleaner and then reinstalling htc sync. I used C Cleaner. The registry cleaner you recommended was more in depth and obviously worked better.
Eusing free registry cleaner
download.cnet.com/.../3000-2094_4-10521691.html
Thanks again,
Kutt
I had the same problem, thanks
But if like me--doing the Eusing registry didn't help try to scan registry in "safe mode" and repair. Then, shut down and restart normally. Try to download HTC Sync
again(doesn't matter if you use the previous installation) and it should work. Cheers
I have installed .NET Framework 4 full version, then installed Windows Phone Device Manager on Windows 7 64bit using Standard User Account, however it fails to show in Program Files, it only shows in "Uninstall a Program". What am I missing?
Cheers
Writing to Program Files requires admin privileges (unless you changed the permissions on that folder). Therefore, it may have installed to a user-writable location instead.
Alternatively, WPDM is not a 64-bit app. Did you check in "Program Files (x86)"? That's probably where it would install by default.
I installed with Admin Privileges, and checked the x86 folder, nothing there.
Cheers
EDIT: I found where it is hiding: C:\Windows\WPDeviceManager
So now it errors when starting: "Windows phone SDK 7.1 is required."
I have a HTC HD7 with the latest Windows installed: 7.10.8107.79
The phone is plugged in via a USB cable.
Suggestions please
EDIT: Found it through Google.
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!!