Share via

Windows Mobile Device Center on Windows 10 (1703)

Anonymous
2018-01-29T16:53:28+00:00

As of last week, I have been able to connect to our RF guns using the Windows Mobile Device Center (WMDC).  We are running Telnet CE on the guns and we program them through the WMDC in combination with ActiveSync on the guns. 

After upgrading to Windows 10 (1703), I had a difficult time getting WMDC to connect with the guns.  After much research I was able to come up with the steps below to get it to work on a regular basis:

  1. Uninstall Windows Mobile Device Center in this order:
    1. Windows Mobile Device Center Driver Update
    2. Windows Mobile Device Center
  2. Reinstall the Windows Mobile Device Center
  3. Right click on Start (Windows)
  4. Left click on Computer Management
  5. Expand Services and Applications.
  6. Left click on Services.
  7. Scroll down to and right click Windows Mobile-2003-based device connectivity.
  8. Select Properties.
  9. Select the Log On tab.
  10. Check “Local System account” and check off “Allow service to interact with desktop.”
  11. Click apply
  12. Scroll down to and right click Windows Mobile-based device connectivity.
  13. Select Properties.
  14. Select the Log On tab.
  15. Check “Local System account” and check off “Allow service to interact with desktop.”
  16. Click apply
  17. Close the Computer Management page.

  ***Note*** The settings above may change when you disconnect from a device or reboot your computer.You will have to redo the settings if it does. ***Note***

  1. Open a command prompt as an administrator.
    1. Left click the Start (Windows) button.
    2. Type in cmd
    3. Right click the command prompt application
    4. Select Run as Administrator
  2. Type in (or copy and paste from blow)

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

  1. Exit the command prompt and reboot your computer.
  2. On the handheld, tap on Start > Settings > Connections > USB to PC icon, uncheck the “Enable Advanced Network Functionality” checkbox, tap OK, and then connect the cable.

Now that I have received: 2018-01 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4056891), it has stopped working again.  I ran the same steps that I used to get it with the initial rollout of 1703. Since this worked with the initial 1703 update, I was hopeful that it would fix it.  No luck.  I have multiple locations that we have to be able to program these RF guns. These locations are not anywhere close to each other, I.E. Puerto Rico, Florida, Texas, California to name a few, so it is not like I can just walk to them to fix them.  Ohio to Puerto Rico is quite a walk.

I am remiss to update them to the 1703 version without a fix.  It is bad enough I have 10 RF guns in my office that need reprogrammed but can't be because I cannot connect to them through their dock. If I cannot find a fix soon, production and distribution of product will become a major issue.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

  1. Anonymous
    2018-02-09T12:50:04+00:00

    So, went through official Microsoft channels and this is what I get:

    "I have reviewed the issue details and this WMDC error is known scenario after fall creators update on windows 10. Unfortunately, WMDC is out of support since 2012 and hence Microsoft does not have any avenue to provide support for this product. Here is link to WMDC’s support lifecycle for your reference.

    I would suggest

    • Testing this scenario with Windows 10 compatibility mode
    • Contacting OEM of the mobile devices/guns for additional support. OEMs are aware about this scenario  and usually can suggest alternate approach.

    I understand this is not ideal update from Microsoft. However, since WMDC is out of support for last 5 years, we support engineers do not have any investigating capabilities for it."

    After asking for an alternate program to connect to the RF Guns, I get:

    "Unfortunately, Microsoft does not have any alternate product for syncing mobile devices to desktops. That is why I was suggesting contacting OEM of these mobile devices as they might have their own approach for it."

    So, there we go.  Thanks to Ian for the assistance.  No, it was not Ian that gave me the response.  That was a sincere thanks. 

    I am working with the distributor to figure out what they recommend to use instead of WMDC.  If anyone has a suggestion, please let me know.

    30+ people found this answer helpful.
    0 comments No comments

8 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-05-04T00:08:24+00:00

    My problem is with my Medion GPS and interfacing with Windows 10

    I have paid for expensive map updates using Medion GoPal Assistant which relies on WMDC and ActiveSync to connect to the PC and synchronise.

    Worked fine up till recently………….

    Since the latest Falls Update nothing works, GPS will not connect so no update.

    Update subscription is due to expire.

    Micro$oft are no longer interested in legacy stuff and Medion are now defunct so will not be issuing updates or fixes.

    So if anyone has any ideas…………….?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-02-23T03:08:57+00:00

    The problem is best addressed by understanding the general life cycle of devices and the retirement of WMDC many years ago.

    You will need windows 7 to run most of the legacy devices.

    Some of these devices *may* run on windows 7 on Hyper-V, but the gotcha here is that if the device is not recognised by wmdc to start with there can be no device passthrough to the best of my knowledge. Only a device seen as a disk drive can be manipulated as a passthrough device for hyper-v.

    So for wmdc users with specification applications, such as data analysis software, install win7 on a standalone PC/laptop. This will be a workaround for some devices which rely on wmdc for the interim until the device vendors create a new model for windows 10 connectivity.

    Let us know how you get on.

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-02-10T21:10:29+00:00

    Glad to be of assistance, Scott. Do let me know if there's anything else you need and we'll assist you with all that we can.

    All the best.

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-02-02T23:58:24+00:00

    Thank you for this information, Scott. During this time, have you already resolved the issue? What I advise you to do next is to uninstall WMDC completely, restart your PC and plug in your device. This way, Windows will look for the appropriate drivers to use on your device.

    I'll be waiting for your updates.

    1 person found this answer helpful.
    0 comments No comments