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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-10-05T15:03:54+00:00

    Thanks soooo much for this fix!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-12-29T08:24:22+00:00

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-10-09T16:02:13+00:00

    I found this thread today after having the same problem with a HP IPAQ and a trying to connect it to a new laptop with the Windows 10 Creators Edition installed.

    It is now working thanks to all who contributed. I thought I would document my steps so it could be helpful for someone in the future:

    1. Downloaded the 6.1 WMDC from the link provided
    2. Uninstalled the existing versions - restarted
    3. Installed from the file downloaded.
    4. Did the fix with the Services applet in GBZ_RS answer, but found similar problems to others about it not being fixed after a restart
    5. Did the registry fixes with a command line prompt with admin privilages

    REG ADD HKLM\SYSTEM\CurrentControlSet\Services\RapiMgr /v SvcHostSplitDisable /t REG_DWORD /d 1 /f

    REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WcesComm /v SvcHostSplitDisable /t REG_DWORD /d 1 /f

    1. Restarted but found "Windows Mobile-2003-based device connectivity service" in Services would not start as there was a conflict
    2. So I also changed the "Windows Mobile-based device connectivity" in Services to also use a Local System Account (I also selected "Allow service to interact with desktop" for both as well - although this may not be needed)

    It now connects and even after a restart. So thanks again to all who contributed.

    PS I did also change the "Windows Mobile-2003-based device connectivity service" to start "Automatically" rather than use the "Automatically (Delayed Start)" option, but I suspect that wasn't required.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2017-09-26T17:18:57+00:00

    Same thing here.  stopped working after latest update

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments