Windows Mobile Device Center will not be supported in future versions on Windows 10

Windows Mobile Device Center will not be supported in future versions on Windows 10 

We have received a few calls where a customer has updated to a Window 10 computer and cannot connect to a Geo7x.  This is a known problem with Trimble.

Per Trimble Support – “We have heard of this issue and our Mobile Computing Systems team is working on it vigorously.”  Right now, it looks like it is the Windows 10 Creators Update (KB4015583) that will not function with Windows Mobile device Center. If you are able to remove that update specifically, and/or revert back to the older version of Windows 10 OS, the Windows Mobile Device Center and in turn Data Transfer Utility will work properly once again.   We don’t think this should be an issue with Operating Systems other than Windows 10, so it may be worth trying on another computer if one is available.

Update:  The official Microsoft position has not changed and support for WMDC ended in 2012. Official notice of that is here.

While it did work OK with earlier versions of Windows 10, it seems that a change in 1703 has been fatal.  The best workaround so far suggested is to change some registry values that affect how Windows 10 handles running the WMDC services in the background.

Juniper Systems FAQ does a good job of summarizing the issue, and the workaround, here.

The original solution post is here.

Here is the workaround per Trimble. 

We had a similar case before which was solved (workaround) by this link information:

https://protect-us.mimecast.com/s/pVq8BwC4rmgHE?domain=stackoverflow.com

Here is the summary which worked for that other case: We are able to get Windows Mobile Device Center (WMDC) to install, but not fully run. Installing required manually enabling the .NET Framework 3.5 similar to as described at the following web page.

https://protect-us.mimecast.com/s/LLOGBxi315zUY?domain=answers.microsoft.com

After install, you must right click on Start, and then click on Computer Management > Services & Applications > Services. Scroll down to right-click on “Windows Mobile-2003-based device connectivity” to select Properties > Log On. Switch to “Local System account” with checking “Allow service to interact with desktop” then click OK.

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.

WMDC never shows connected, but ActiveSync on the handheld does, and you can at least open File Explorer on your PC to “browse the contents of the remote device” for transferring files. We are not sure how much this limits RAPI functions.

These Services settings changes must be re-applied every time you Restart your PC.

If you have any further questions please feel free to email us at [email protected]

 

 

2 thoughts on “Windows Mobile Device Center will not be supported in future versions on Windows 10

  1. this is a problem for Wisconsin DNR. we are in the process of install Win10 over the next few months. please let me know when there is a better fix for this problem.

Leave a Reply

Your email address will not be published. Required fields are marked *