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

Anonymous
2017-04-13T09:17:58+00:00

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.***

Windows for home | Other | Devices and drivers

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
2017-04-14T06:25:22+00:00

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.

Was this answer helpful?

400+ people found this answer helpful.
0 comments

51 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-04-19T07:34:25+00:00

    and if a device project not loaded to visual studio 2008, go to Control panel -> Uninstall or change program, right click Power Toys for .NET Compact Framework 3.5and choose repair, this will be fix the problem!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-04-14T22:37:49+00:00

    Maybe you have to restart before it starts to work, I now noticed that the service is back to using the "Local Service" account, however everything still works fine. I did reboot the system at least once before connecting my Pocket PC, so that could possibly be it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-14T15:52:40+00:00

    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.

    The same issue for me, going into the services applet and changing it over to local system account log on mode got it to work again.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2017-04-14T13:03:23+00:00

    Tried to set the Log On account for both Windows Mobile services, it allowed WMDC to open but not connect.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments