Sync Center is still there in Windows 10 (Windows key + X > click Control Panel)
Windows Mobile Device Center Compatibility with Windows 10
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Is or will Windows Mobile Device Center be compatible with Windows 10? There are some legacy devices that require sync with WMDC and then there are security personnel that do not allow devices to connect to their Wi-Fi but rather connect them via USB using WMDC. I was able to get WMDC to work successfully on Windows 8 and 8.1. So far I have not heard any news in regards to Windows 10. Looking forward to hearing results and or news regarding this. Thx everyone.
* Moved by the moderator to the appropriate forum category.
Windows for home | Windows 10 | Install and upgrade
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.
Answer accepted by question author
Anonymous
174 additional answers
Sort by: Newest
-
Anonymous
2015-10-26T15:08:46+00:00 This is great if you can't connect your PDA to the computer.
My problem, and I believe many others as well, is that connection is made and you are able to browse the PDA but cannot synchronize Outlook email, calendar, contacts, and tasks between the two devices.
I was made aware of a problem with Windows 10 that prevents synchronization and that the Windows staff were aware of it (see previous thread) but as of yet no hot fix, patch, or update has been released to correct the situation.
-
Anonymous
2015-10-26T00:08:07+00:00 Additional Information on this procedure above - your may have to try multiple times. The problem is intermittent. I have found if I repeat the procedure, it will almost certainly connect within 5 tries.
When the Windows Mobile 6.5 Professional device is cradled or connected, first a Marvel RNDIS appears in other devices, then Microsoft Windows Mobile Remote Adapter device appears under Network adapters, then the Marvel RNDIS device disappears, and if working correctly, the device appears under Portable Devices. You can then open Windows Mobile Device Center, if it does not open automatically, and it will connect to your device. When this operation fails, the device under Portable Devices never appears. Complete installation of the necessary drivers fails..
This requires disk accesses. However, I checked my disk drive and it is 7200 RPM, so I would not expect disk speed and timeout to be the problem.
Again, hope this helps someone.
Derek
-
Anonymous
2015-10-24T15:39:50+00:00 I don't see how that's helpful. We're trying to install WMDC 6 or better in 10
-
Anonymous
2015-10-23T05:23:25+00:00 Folks,
I corrected a problem in Windows 10 (upgraded from Windows 7 Ultimate) with Windows Mobile Device Center 6.1 connecting to a Windows Mobile 6.5 Professional mobile device (Ashtech MobileMapper 100 GPS Receiver).
Connection worked on my Windows 10 laptop (Sony Vaio upgraded from Windows 8.1), but not on my desktop (Dell OptiPlex 745C upgraded from Window 7 Ultimate). Microsoft support hacked on the desktop problem for over 1 hour. Bully effort for them, but to no avail.
On the laptop which worked correctly, with the device plugged into USB, under Network Adaptors appeared "Microsoft Windows Mobile Remote Adaptor", and under Portable Devices appeared "Ohanapecosh MobileMapper 100 One", which is the name of my device. On the desktop, however, on the Device Manager Control Panel appeared "Microsoft Windows Mobile Remote Adaptor #2" (OK), but nothing under Portable Devices appeared at all (not good).
Reference the procedure here:
https://support.microsoft.com/en-us/kb/931937
Under Troubleshooting Tips - Device will not connect, I followed steps 1, 2, 3, & 5. (I did not follow step 4 because no Mobile Device node appeared in my Device Manager Control Panel). The problem is describe there as a driver not installed successfully.
After following the procedure (uninstalling the "Microsoft Windows Mobile Remote Adaptor #2" driver and plugging in the device to reinstall), on the desktop computer that formerly failed, I saw under Portable Devices appearing "Ohanapecosh MobileMapper 100 One", and it connected correctly with Windows Mobile Device Center 6.1.
Hope this helps someone.
Derek