WMDC will not be supported in future versions of Windows 10

Windows Mobile Device Center (WMDC) ) will not be supported in future versions of Windows 10.  We have received a few calls where a customer has updated to a Window 10 computer and cannot connect to a TSC3.  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 you have one available to you.

Update:  The official Microsoft position has not changed and support for WMDC ended in 2012. Official notice of that is here: https://protect-us.mimecast.com/s/ar9LBwFqZ6rt2?domain=support.microsoft.com

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: https://protect-us.mimecast.com/s/2789BWcvaz5c5?domain=junipersys.com

The original solution post is here:  https://protect-us.mimecast.com/s/6RoLBWcmk26cG?domain=social.technet.microsoft.com

There may be other factors that affect whether it works on a particular platform, so while we can suggest the workaround it may not be a fix for all cases.  A second temporary solution was found by a Trimble dealer. They found a temporary solution:

  1. Under Services, select “Windows Mobile-2003-based device connectivity” and “Windows Mobile-based device connectivity”
  1. Go to Log On and change it to Log on as “Local system account”.

What I heard is when you restart the Windows 10 PC, you need to re-do these steps above, so perhaps not an ideal solution.

Work in the Windows Mobile diaspora is continuing and there may be a more definitive solution identified in the next month or so.

You can contact Seiler Support with questions at: [email protected]

Thanks to Steve Grady for sharing the above information.

 

 

Leave a Reply

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