31

Does anyone know how I can get a Windows Mobile 6.5 PDA to connect up to a Windows 10 PC?

Before upgrading the PC from Window 8.1 I was able to use Windows Mobile Device Center to link up to the PDA over USB. This allowed me to access files on the PDA via Windows Explorer, access the internet from the PDA over our network and deploy to the PDA via Visual Studio 2008.

I had to uninstall Windows Mobile Device Center as part of the Windows 10 installation, as it was flagged as incompatible with Windows 10. I can't seem to find an alternative for Windows 10?

Iain Hoult
  • 3,651
  • 5
  • 23
  • 39
  • WMDC is now called "Sync Center" see here http://answers.microsoft.com/en-us/windows/forum/windows_10-win_upgrade/windows-mobile-device-center-compatibility-with/95c017d8-c243-48a1-bbdc-afb77255ca7f?auth=1 – josef Aug 18 '15 at 13:25
  • 1
    If only Sync Centre could actually detect my PDA :( – Iain Hoult Aug 18 '15 at 13:32

7 Answers7

49

Unfortunately the Windows Mobile Device Center stopped working out of the box after the Creators Update for Windows 10. The application won't open and therefore it's impossible to get the sync working. In order to get it running now we need to modify the ActiveSync registry settings. Create a BAT file with the following contents and run it as administrator:

REG ADD HKLM\SYSTEM\CurrentControlSet\Services\RapiMgr /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WcesComm /v SvcHostSplitDisable /t REG_DWORD /d 1 /f

Restart the computer and everything should work.

JonathanReez
  • 1,319
  • 3
  • 16
  • 34
  • This helped me to get WMDC to launch. Didn't install any of the dependencies from the accepted answer. Installed WMDC 6.1 (without altering compatibility settings) and added these keys via an elevated Powershell window. – root Sep 15 '17 at 14:54
  • Brilliant this worked... The only other thing I noticed with my PC was that it kept coming up with "... Default email application is not selected..." now after using this reg hack it is not displaying anymore :) – Gwasshoppa Sep 17 '17 at 21:39
  • Same problem here and worked for me too. Had to restart my PC several times, but now it works, even with "Enable advanced network " checked on the device ! Thanks. – Jean-Daniel Gasser Jan 12 '18 at 09:13
  • I was able to connect using bluetooth as the usb connection didn't even recognize the device. – Ronen Festinger Apr 07 '18 at 09:34
  • For Windows 10 version 1709, Combine this answer with setting local system account for the service by Lee Harris's answer and then a restart got me connected finally. Mind that I have VS2008 and WMDC installed already. – Lionet Chen Apr 24 '18 at 00:13
  • Update: Also succeeded on a fresh PC without VS2008. Just the Registry, Local System account for services, WMDC 6.1 and the developer tool kit. No other settings needed. – Lionet Chen Apr 24 '18 at 00:21
  • Worked for me too. Windows 10 version 1809 – Altivo Apr 08 '19 at 09:26
  • Worked for me too. Windows 10 version 1903 – skaddy Sep 23 '19 at 13:05
21

I have managed to get my PDA working properly with Windows 10.

For transparency when I posted the original question I had upgraded a Windows 8.1 PC to Windows 10, I have since moved to using a different PC that had a clean Windows 10 installation.

These are the steps I followed to solve the problem:

Iain Hoult
  • 3,651
  • 5
  • 23
  • 39
  • 1
    This is not working for me. I guess you did something additional. – mynkow Dec 30 '16 at 09:13
  • 1
    I did find one way to get the devices to connect in wmdc on win 10. If i uncheck advanced network functionality on the pda under usb settings it will connect but when our users try to use the data connection for a download (the reason we use wmdc) the download hangs after a few seconds and then wmdc either crashes or loses the connection. So far we are unable to find any solution that works. – mynkow Dec 30 '16 at 09:21
  • The bad thing is almost all of our users are on win 7 or 8.1 so they will be upgrading soon through automatic updates and they will have no way to use the pdas once that happens. we have a userbase of about 100 pdas so this is going to be a nightmare. SOURCE=> https://answers.microsoft.com/en-us/windows/forum/windows_10/windows-mobile-device-center-compatibility-with/95c017d8-c243-48a1-bbdc-afb77255ca7f – mynkow Dec 30 '16 at 09:21
  • @mynkow it might be a pain with a lot of machines, but fresh installations of Win10 do not seem to have the same problems as upgrading. I have seen several fresh installations just work without any tweaking. – Iain Hoult Jan 10 '17 at 13:19
  • I tried this several times (from a different stack link answer) and it didn't work. – Gwasshoppa Sep 17 '17 at 21:40
10

Had the same problem. Came across an article from Zebra with the fix that worked for me:

  1. Open services.msc
  2. Go to Windows Mobile-2003-based device connectivity
  3. Right click Windows Mobile-2003-based device connectivity and click Properties
  4. Go to Log On Tab
  5. Choose Local System Account

image description

  1. Click Apply
  2. Go to General Tab
  3. Press Stop and wait
  4. Once stopped, press Start
  5. Press OK
  6. Restart your PC
  7. Retry the Windows Mobile Device Center

Original article can be found here

CrunchyBrains
  • 3
  • 4
Lee Harris
  • 484
  • 3
  • 12
9

  1. Install

    • Windows Mobile 6 Professional SDK Refresh
    • Windows Mobile 6 Standard SDK Refresh
    • Windows Mobile 6.5 Professional Developer Tool Kit (USA)
    • Windows Mobile 6.5 Standard Developer Tool Kit (USA)

  2. Control Panel > Programs and Features > Add or remove a Windows component

    • NET Framework 3.5
    • Check HTTP and non HTTP

  3. Reinstall WMDC observing your platform x64/x86

  4. Services.msc > Windows Mobile 2003-based device connectivity

    • Logon > Local System
    • Allow service to interact with desktop

  5. Restart your PC

mathias.horn
  • 209
  • 1
  • 7
  • 11
6

Here is the answer: Download the "Windows Mobile Device Center" for your machine type, likely 64bit.
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3182

Before you run the install, change the compatibility settings to 'Windows 7'. Then install it... Then run it: You'll find it under 'WMDC'.. Your device should now recognize, when plugged in, mine did!

Robert Koernke
  • 405
  • 3
  • 17
  • You cannot write a sentence like "Here is the answer", if this was only applicable to you not being the right answer for everyone. This was not the answer in my case. – jstuardo Feb 14 '17 at 20:52
  • If you notice most of the answers on here are nearly the same, just slightly different styles. Did you make sure that you installed WMDC with windows 7 compatiblity. – Robert Koernke Feb 15 '17 at 21:43
5

Install Windows Mobile Device Center for your architecture. (It will install older versions of .NET if needed.) In USB to PC settings on device uncheck Enable advanced network and tap OK. This worked for me on 2 different Windows 10 PCs.

gcaughey
  • 81
  • 1
  • 3
  • This worked for me. I also needed to add the two registry keys mentioned by another user on this question. – root Sep 15 '17 at 15:19
1

I haven't managed to get WMDC working on Windows 10 (it hanged on splash screen upon start), so I've finally uninstalled it. But now I have a Portable Devices / Compact device in the Device Manager and I can browse my Windows Compact 7 device within Windows Explorer. All my apps using RAPI also work. Maybe this is the result of installing/uninstalling WMDC, or probably this functionality was already presented on Windows 10 and I've just overlooked it initially.

Alex Che
  • 5,438
  • 2
  • 37
  • 48