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

2019-03-10T08:41:39+00:00

I want to make sure that please send the queries as soon as. Possible
Was this answer helpful?

0 comments No comments
Anonymous

2019-03-04T10:28:56+00:00
I don't think you need all that.

Just make sure these services are starting automatically as local service:
- Windows Mobile-2003-based device connectivity
- Windows Mobile-based device connectivity
You may need to review:

https://support.waspbarcode.com/kb/articles/windows-10-creators-update-v1703-and-fall-creators-update-v1709-windows-mobile-device-center-m

This has been working consistently on multiple computers.
Was this answer helpful?

0 comments No comments
Anonymous

2019-03-02T12:18:08+00:00

Here on page 2, this was the solution for me. Doesn't seem to have been quoted since, so I think it's been missed by others.

Note that it is almost certain that you will have to install WMDC (or at least the driver update bit) _twice_.

ie

install .NET 3.5 if not already done

install drvupdate-amd64.exe

install WMDC-fixes-for-Win10.msi

WMDC should now open from control panel, but will likely not connect to the mobile device, and the device will likely not show up in Device Manager.

disconnect the mobile device

uninstall the WMDC Driver Update (it may not be necessary to reinstall WMDC itself)

install drvupdate-amd64.exe again

It doesn't matter even if you install the "fixes" first, WMDC driver update still needs to be installed, uninstalled and reinstalled!
Was this answer helpful?

0 comments No comments