Windows Mobile Device Center Compatibility with Windows 10

EDIT: I think this may be a problem with my code - I can step into the scanner call but it is freezing when I return from a service call. I'm still leary

Is this still working for you? I was doing great until last early December 2016. Running 6.1.6965 connecting to a Symbol MC32N0S (also have an MC9090 but left my cradle at a customer site so can't test with that until I get a replacement).

I can still deploy new code but am freezing any time I attempt to debug. Not fun having to debug the tools all of the time :(  Going to see if I can uninstall some updates.

Is anyone able to synchronise Office data such as calendar, tasks or contacts.

I noticed that WMDC is now visible in the network and sharing centre, but I can still not share properly. I can copy and paste in explorer and computer.

When I synchronise I get an error that I am unble to update through a server.

This DOES NOT WORK!!!! LOL

Split from this thread.

We've recently encountered this same problem with Windows 10 workstations. Prior to upgrading from Windows 7 to Windows 10, we had no problems with Windows mobile devices (running Windows Mobile 6.1, 6.5, and earlier versions of 5.x prior). These devices when connected to the workstation would be detected and the WMDC would activate. In the Windows XP days, this would work equally with the MS ActiveSync Mgr tool.

Now, with Windows 10, it works the first time, but after disconnecting the mobile (handheld) device, and subsequent reattachment of the mobile device would do nothing.

At first we thought that this may be a USB connection issue and/or USB driver, USB device, etc.

Then we compared a Windows 10 workstation side-by-side with a Windows 7 workstation similarly equipped and configured.

What we learned was that unlike Windows 7, the Windows 10 OS was crashing the WMDC tool. If we manually launched WMDC again on Windows 10, it would detect the mobile device connected via USB and activate accordingly. However 98% or the time after disconnecting the mobile device, WMDC would go away, but never come back (unless manually launched). In the case of Windows 7, the WMDC would also "appear to go away" when the mobile device was disconnected, but it would always come back up when the device was reattached.

So for now, until Microsoft applies a solution, we are having our users simply manually launch WMDC prior to (or after) connecting a mobile device. 

(Note: we did attempt to uninstall WMDC on the Windows 10 workstation and then re-install it, but we ran into WMDC install problems trying to negotiate the installed MS Office Outlook (64-bit). Other forums suggested WMDC install process needs to find Office 32-bit instead. This effort against MS Office install and WMDC install is proving to be problematic, and not worth the effort at this time. Opting on the manual launch of WMDC is working for now).

Hi Gerry, your description of the issue is spot on with ours.  Installing WMDC and having it detect the devices was not the problem, but rather, the problem we are encountering is upon cradle disconnect events the WMDC services (RapiMgr and WcesComm) abruptly crash.  The services will ultimately restart about ~1 minute later due to the fail safe built into Windows Services, but this restart only occurs after crash #1 and crash #2, as after that, the services do not automatically restart (but to your point, if the user manually opens up WMDC, they are manually restarting the services).

I am curious, have you found a solution to this issue yet, or are you still stuck with forcing users to manually launch WMDC each time they need to sync?  I have an open ticket with Microsoft on this issue at the moment, however, thus far the only suggestions I have been given are to use the Sync Center, which is not a solution to our problem as our PC application (which facilitates the transfer of data from device to PC via RAPI) requires the WMDC services to be running to function properly.