After Windows 10 Creators Update can not connect my Windows CE device via Windows Mobile Device Center

Anonymous

Hello

After I installed Windows 10 Creators Update I can not connect my Windows CE device via Windows Mobile Device Center(WMDC)

When I started Visual Studio 2008 and tried to open my project I am developing for my Windows CE device it first said that "Microsoft.CompactFramework.CSharp.targets"

is missing but after reinstalling the compact framework that was fixed.

But then i noticed that when I try to connect my Windows CE device nothing happens on the pc(WMDC does not start) and the device is not trying make a connection.

I can not start WMDC manualy and an hour before when the creators update was not installed everything was working fine.

Any Ideas how to fix this?

In the Event Viewer is noticed these new errors:

Failed to start the Windows Mobile-2003-based device connectivity service due to CreateSemaphore(0x80070005) failure (see data for failure code).

and

The server {373E19B5-76AA-46D5-93A9-2E39A99B39B2} did not register with DCOM within the required timeout.

I do not know what this means but those appeared after the update so hope they help.

***Post moved by the moderator to the appropriate forum category.***

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.

0 comments

Answer accepted by question author

Anonymous

I still use a Pocket PC 2002 based device and ran into the same problem.

These are the steps I took to get WMDC to work again:

If Windows 10 is showing you the "This app isn't working correctly" notification when you try to start Windows Mobile Device center, first reinstall it as it suggests. I simply removed WMDC first and then used the 6.1 installation available from the Microsoft Download Center:

This should make the message go away, but WMDC still does not launch, either nothing happens or it will be stuck on the splash screen.

Now go to the Services applet, and look for the "Windows Mobile 2003-based device connectivity" service. Double-click it to view it's properties, choose the "Log On" tab and select "Local System account" as the log on mode.

You should now be able to start the service and WMDC will work as expected again.

0 comments

51 additional answers

Anonymous

2017-05-24T15:26:03+00:00

Thank you!!!! Worked perfectly.
Was this answer helpful?

0 comments No comments
Anonymous

2017-05-28T20:00:49+00:00

GBZ-RS, thank you so much for this fix!!! I was about to pull my hair out because I HAVE to use this at work, and the tech support people who supplied the machine with Windows CE had no clue how to fix this. I was able to share the solution with them, so hopefully they can help others.
Was this answer helpful?

0 comments No comments
Anonymous

2017-06-02T14:13:45+00:00

The issue is also not solved after reinstalling WMDC. I get the message. Missing components. Can this be solved? A lot of customers have this issue.
Was this answer helpful?

0 comments No comments
Anonymous

2017-06-16T14:32:53+00:00

I tried the reinstall and the change in the service - and it fixed the issue, until I had to reboot and then it was back to square 1. Repeating the fix sorted it but I really don't want to have to do it every time I start my computer up. Is anyone else having this recur when thewir PC is starting up? Would the registry fix resolve that once and for all?
Was this answer helpful?

0 comments No comments