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-09-18T12:48:25+00:00
1) Windows 10 v1703 (the creators update)

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

from x0x0x0x0x0 replied on April 20, 2017

Thank you!

and for PC with USB 3.0

this description was helpful!

Depending on your computer hardware, we have had some success making sure the mobile devices

are connected to USB 2.0 ports rather than 3.0, using an external USB hub as a go-between

https://support.waspbarcode.com/kb/articles/windows-mobile-device-center-and-windows-10

2) Windows 8, 10 with USB 3.0

using an external USB 2.0 hub
1. and 2) - this fixed my issue
(Windows 10 v1703 and Dell Latitude E6540 with USB 3.0)
Was this answer helpful?

0 comments No comments
Anonymous

2017-08-17T20:19:09+00:00

Was working no longer seems to be working. i wrote detailed instructions and was able to repeat multiple times on multiple systems now i can not.
Was this answer helpful?

0 comments No comments
Anonymous

2017-08-15T08:19:09+00:00

Dears,

Any updates for the above?

regards,

Alaa
Was this answer helpful?

0 comments No comments
Anonymous

2017-08-03T11:46:38+00:00

Hi Again,

I've tried your advise, still facing same issue. does anyone can check for this and give me a solution?

thanks in advance

Alaa
Was this answer helpful?

0 comments No comments