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-20T23:08:38+00:00

    Source: https://social.technet.microsoft.com/Forums/windows/en-US/9cab3e8e-6cc4-48e4-8ed9-d595bc83f04b/windows-mobile-device-centre?forum=win10itproapps#a044cbb9-77bd-44c3-a150-3d2cb5bd1c92

    "The creators update has a new feature, related to svchost.exe: the services will not share by default the same svchost.exe, even they are assigned to be run within of the same group with -k option. More detailed has been described here.

    Rapimgr and Wcescomm (Windows Mobile-based device connectivity and Windows Mobile-2003-based device connectivity) are such services: they are defined to be started in the same shared svchost.exe (-k WindowsMobile). RapiMgr creates a kernel semaphore AS_ACCEPTANCE_SEMA, because it starts first.  WcesComm tries to do this too, but fails: the semaphore has been already created and should be only opened. This will fail: not enough permissions (remember: two different svchost.exe, different SID, etc). So, wcescomm is just stopped.

    The fix is simply: add SvcHostSplitDisable to the both services RapiMgr and WcesComm:

    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

    Both services should have the same Local Service Account. You have to reboot after this change

    Added: Both services should have on Recovery tab in "Subsequent failures" the "Restart Service" enabled. Seems, RapiMgr crashes sometimes on the device disconnecting. "

    This fixed my issue.

    I'll give this a try. Thank you!

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2017-04-20T22:04:43+00:00

    Of course it would not be very useful if WMDC does not connect/sync, that is not what i consider expected behavior ;-).

    All I know is that in my case, I was able to get WMDC to work fully (so it connects and syncs with my device again) by doing the steps I described.

    x0x0x0x0x0 posted some valuable info that might be useful for you if it still does not work.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-04-20T14:10:32+00:00

    Source: https://social.technet.microsoft.com/Forums/windows/en-US/9cab3e8e-6cc4-48e4-8ed9-d595bc83f04b/windows-mobile-device-centre?forum=win10itproapps#a044cbb9-77bd-44c3-a150-3d2cb5bd1c92

    "The creators update has a new feature, related to svchost.exe: the services will not share by default the same svchost.exe, even they are assigned to be run within of the same group with -k option. More detailed has been described here.

    Rapimgr and Wcescomm (Windows Mobile-based device connectivity and Windows Mobile-2003-based device connectivity) are such services: they are defined to be started in the same shared svchost.exe (-k WindowsMobile). RapiMgr creates a kernel semaphore AS_ACCEPTANCE_SEMA, because it starts first.  WcesComm tries to do this too, but fails: the semaphore has been already created and should be only opened. This will fail: not enough permissions (remember: two different svchost.exe, different SID, etc). So, wcescomm is just stopped.

    The fix is simply: add SvcHostSplitDisable to the both services RapiMgr and WcesComm:

    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

    Both services should have the same Local Service Account. You have to reboot after this change

    Added: Both services should have on Recovery tab in "Subsequent failures" the "Restart Service" enabled. Seems, RapiMgr crashes sometimes on the device disconnecting. "

    This fixed my issue.

    Was this answer helpful?

    60+ people found this answer helpful.
    0 comments
  4. Anonymous
    2017-04-20T14:06:03+00:00

    If works as expected means that WMDC runs now, but does not actually connect to the device, then yes, it works as expected. Windows Mobile Remote Adapter shows up in Device Manager, and WMDC runs now, but it says Not Connected. I have tried this on multiple machines now with this same result.

    Was this answer helpful?

    0 comments