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
    2017-06-21T01:27:20+00:00

    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.

    This solution worked for me on my PC which has been running Windows 10 for 2 years and was upgraded to Windows Creator. However, I wanted to move my operating system over to an M.2 SD card, so I used windows Media Creator Tool to make a Windows Creator Installation disk DVD. After a clean install of Windows Creator to the new M.2 disk and applying the fixes described above, I cannot get my PC to connect to my Trimble Ranger. I've also applied these two registry hacks:

    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

    There must be something in the upgraded system that makes this fix work, but not if a freshly installed version of Windows Creator. Still looking for a fix.

    TR

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-06-19T14:27:28+00:00

    None of these are fixing the issue for me. Doing the local account thing in services got mobile device center running but none of the other fixes will get the PC to detect the device. Doing that regedit just makes explorer.exe crash on startup and once I've stopped and started explorer.exe, the Windows CE device still isn't being detected.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-06-16T16:01:23+00:00

    I did have to do the registry fix to get mine to stay fixed.  Be sure to run CMD as administrator and copy and paste the following.

    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

    Restart the system.

    Was this answer helpful?

    0 comments
  4. 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