Windows Mobile Device Center Compatibility with Windows 10

Here is what I found out -- HP Support Center told me that Microsoft is not providing a patch for Windows Mobile Device Center (WMDC) at this present time there is no known workaround for connecting to the new Windows 10 operating system. iPAQ software will be unable to sync with WIndows 8, 8.1 or 10.   HP continues to state that other customers have been asking of late, and a request was sent to HP IT for updates but due to age of the iPAQ handheld line a resolution might not be forthcoming.

HOWEVER, I have been on the phone for two weeks with the Answer Desk and Tier II Microsoft Support and explained t the Tier II the issue lies with THEM and Microsoft NEEDS to create the patch since many of us use these devices, the function beautifully and somehow so FIX IT!  The Tier II person was supposed to e-mail me something so I could copy and paste HP's answer but I am still waiting for the e-mail.  Some excuse about Microsoft's e-mail servers being busy and they allegedly sent it 4 or 5 times.  Microsoft is forwarding this issue to their Tier III people so that a patch or update or fix can be created and pushed through via the updates that Microsoft sends us.  They told me it may take another 3 to 4 weeks.    So folks, chat with Answer Desk, have them escalate to Tier III.   Remember the squeaky wheel gets the oil!!!!

Same problem here. I've tried everything including a brand new Windows 10 installation followed immediately by installation of WMDC to rule out any potential conflicts with existing software.

Hopefully an update will be available soon although I wouldn't hold my breath!

I read your post before I updated to Windows 10 today. I have thousands of WM 6.5 devices that connect to my customers' PCs. 

The flagged answer is not helpful to me or people that use Windows Mobile Device Center. 

A procedural work around to launch Windows Mobile Device Center manually will establish the connection. 

Workaround steps:

1. Place device into cradle.
2. Launch Windows Mobile Device Center (WMDC)
3. Create a partnership. (optional)
4. When the PDA is removed from the cradle WMDC is automatically closed.
5. When the PDA is returned to the cradle manually launch WMDC.
6. Click 'OK' to the message "There is no email to preform the requested action...."
7. Access the internet on device.

Microsoft, please auto launch WMDC when the device is placed into the cradle on Windows 10 and create an option to never show the message "There is no email to preform the requested action...." message again.

Hopes this helps. 

***EDIT Since Windows 10 1703 and 1709 there are more steps, you need to change services to local.

UPDATE: Some good suggestions which seem to work are now at this web page.

https://social.technet.microsoft.com/Forums/office/en-US/9cab3e8e-6cc4-48e4-8ed9-d595bc83f04b/windows-mobile-device-centre

PREVIOUS: I am 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://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/how-to-instal-net-framework-35-on-windows-10/450b3ba6-4d19-45ae-840e-78519f36d7a4

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.

https://stackoverflow.com/questions/43394045/windows-mobile-device-center-stops-working-after-windows-10-1703-upgrade

ALSO put WMDC in Vista compatibility mode. Lastly reboot your PC before you want your device to sync.  

I have talked our company out of using ActiveSync our software can also update using WiFi and Ethernet. We are developing our software for Android. Our next deployment will be Android.

Tried your workaround and was able to get Mobile Device Center to connect again once I removed the device from the cradle. Unfortunately still getting the same error of "... encountered a problem on the desktop".

I chatted with Answer Desk and told them of the known issue and asked to escalate to Tier III. Manager got back to me and closed my case because the issue was being discussed in another thread.

Getting frustrated!