Share via

Windows Mobile Device Center on Windows 10 (1703)

Anonymous
2018-01-29T16:53:28+00:00

As of last week, I have been able to connect to our RF guns using the Windows Mobile Device Center (WMDC).  We are running Telnet CE on the guns and we program them through the WMDC in combination with ActiveSync on the guns. 

After upgrading to Windows 10 (1703), I had a difficult time getting WMDC to connect with the guns.  After much research I was able to come up with the steps below to get it to work on a regular basis:

  1. Uninstall Windows Mobile Device Center in this order:
    1. Windows Mobile Device Center Driver Update
    2. Windows Mobile Device Center
  2. Reinstall the Windows Mobile Device Center
  3. Right click on Start (Windows)
  4. Left click on Computer Management
  5. Expand Services and Applications.
  6. Left click on Services.
  7. Scroll down to and right click Windows Mobile-2003-based device connectivity.
  8. Select Properties.
  9. Select the Log On tab.
  10. Check “Local System account” and check off “Allow service to interact with desktop.”
  11. Click apply
  12. Scroll down to and right click Windows Mobile-based device connectivity.
  13. Select Properties.
  14. Select the Log On tab.
  15. Check “Local System account” and check off “Allow service to interact with desktop.”
  16. Click apply
  17. Close the Computer Management page.

  ***Note*** The settings above may change when you disconnect from a device or reboot your computer.You will have to redo the settings if it does. ***Note***

  1. Open a command prompt as an administrator.
    1. Left click the Start (Windows) button.
    2. Type in cmd
    3. Right click the command prompt application
    4. Select Run as Administrator
  2. Type in (or copy and paste from blow)

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. Exit the command prompt and reboot your computer.
  2. On the handheld, tap on Start > Settings > Connections > USB to PC icon, uncheck the “Enable Advanced Network Functionality” checkbox, tap OK, and then connect the cable.

Now that I have received: 2018-01 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4056891), it has stopped working again.  I ran the same steps that I used to get it with the initial rollout of 1703. Since this worked with the initial 1703 update, I was hopeful that it would fix it.  No luck.  I have multiple locations that we have to be able to program these RF guns. These locations are not anywhere close to each other, I.E. Puerto Rico, Florida, Texas, California to name a few, so it is not like I can just walk to them to fix them.  Ohio to Puerto Rico is quite a walk.

I am remiss to update them to the 1703 version without a fix.  It is bad enough I have 10 RF guns in my office that need reprogrammed but can't be because I cannot connect to them through their dock. If I cannot find a fix soon, production and distribution of product will become a major issue.

Windows for home | Windows 10 | 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

  1. Anonymous
    2018-02-09T12:50:04+00:00

    So, went through official Microsoft channels and this is what I get:

    "I have reviewed the issue details and this WMDC error is known scenario after fall creators update on windows 10. Unfortunately, WMDC is out of support since 2012 and hence Microsoft does not have any avenue to provide support for this product. Here is link to WMDC’s support lifecycle for your reference.

    I would suggest

    • Testing this scenario with Windows 10 compatibility mode
    • Contacting OEM of the mobile devices/guns for additional support. OEMs are aware about this scenario  and usually can suggest alternate approach.

    I understand this is not ideal update from Microsoft. However, since WMDC is out of support for last 5 years, we support engineers do not have any investigating capabilities for it."

    After asking for an alternate program to connect to the RF Guns, I get:

    "Unfortunately, Microsoft does not have any alternate product for syncing mobile devices to desktops. That is why I was suggesting contacting OEM of these mobile devices as they might have their own approach for it."

    So, there we go.  Thanks to Ian for the assistance.  No, it was not Ian that gave me the response.  That was a sincere thanks. 

    I am working with the distributor to figure out what they recommend to use instead of WMDC.  If anyone has a suggestion, please let me know.

    30+ people found this answer helpful.
    0 comments

8 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-06T14:43:45+00:00

    Here is the Event Viewer Log of the Error:

    Log Name:      Application

    Source:        Windows Error Reporting

    Date:          2/6/2018 8:37:43 AM

    Event ID:      1001

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      WDEL48DHMF2.nac.ppg.com

    Description:

    Fault bucket 78756901, type 5

    Event Name: CLR20r3

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: wmdc.exe

    P2: 6.1.6965.0

    P3: 465efff8

    P4: Microsoft.WindowsMobile.DeviceManager

    P5: 6.1.0.0

    P6: 465efe7a

    P7: 1b6

    P8: 56

    P9: System.UnauthorizedAccess

    P10:

    Attached files:

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A8F.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8DFB.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E77.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8EC7.tmp.txt

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wmdc.exe_cdb94df9b8366c2384589bd3841dbaf24979c040_00000000_184aa309

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 2f6a9359-1e9d-4050-baf4-34e79af9f010

    Report Status: 268435456

    Hashed bucket: 91e57f4dd8c159dbc325c510421a5059

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Windows Error Reporting" />

    <EventID Qualifiers="0">1001</EventID>

    <Level>4</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-02-06T13:37:43.873848400Z" />

    <EventRecordID>51065</EventRecordID>

    <Channel>Application</Channel>

    <Computer>WDEL48DHMF2.nac.ppg.com</Computer>

    <Security />

    </System>

    <EventData>

    <Data>78756901</Data>

    <Data>5</Data>

    <Data>CLR20r3</Data>

    <Data>Not available</Data>

    <Data>0</Data>

    <Data>wmdc.exe</Data>

    <Data>6.1.6965.0</Data>

    <Data>465efff8</Data>

    <Data>Microsoft.WindowsMobile.DeviceManager</Data>

    <Data>6.1.0.0</Data>

    <Data>465efe7a</Data>

    <Data>1b6</Data>

    <Data>56</Data>

    <Data>System.UnauthorizedAccess</Data>

    <Data>

    </Data>

    <Data>

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A8F.tmp.mdmp

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8DFB.tmp.WERInternalMetadata.xml

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8E77.tmp.csv

    \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8EC7.tmp.txt</Data>

    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_wmdc.exe_cdb94df9b8366c2384589bd3841dbaf24979c040_00000000_184aa309</Data>

    <Data>

    </Data>

    <Data>0</Data>

    <Data>2f6a9359-1e9d-4050-baf4-34e79af9f010</Data>

    <Data>268435456</Data>

    <Data>91e57f4dd8c159dbc325c510421a5059</Data>

    </EventData>

    </Event>

    0 comments
  2. Anonymous
    2018-02-05T18:31:08+00:00

    Ian,

    No, still not resolved.  I tried uninstalling WMDC as you said above.  Did not help.  So, I did a combination of everything I could think of.

    1 - Removed the WMDC update - fail

    2 - Removed WMDC then reinstalled it without the Computer Management (see first post above) and Registration changes (see first post above) - fail

    3 - Removed WMDC, Reinstalled, made Computer management changes - fail

    4 - Removed WMDC, Reinstalled, made registration changes - fail

    5 - Removed WMDC, reinstalled, made registration changes, then did Computer Management changes - fail

    Of course, I reboot between every step just to make sure that it did not cause any errors that way.

    So, back to square 1 again.  I am not sure where this is going wrong.  I guess my inner Geek is not as strong as I had hoped. 

    I am going to go to Corporate and see if they can have them remove the update.  Maybe that will help. 

    If you have any further ideas, please let me know.  This is rather frustrating.  One of our Warehouses is down to 2 spares.  I am down to 2 spares and I have 10 that need reprogramed in my office.  It would probably help if the software we have wasn't designed in 2004.

    0 comments
  3. Anonymous
    2018-01-31T15:20:03+00:00

    Ian,

    Thanks for the reply.  Removing the update is not an option at this point.  It is a company wide update being pushed down by corporate, and being only an IT contractor here, there is not much of a choice.

    Sync Center is not showing it connecting.  When I open up Windows Mobile Device Center (WMDC) it will show connecting for a few seconds, then I get this:

    If I don't have the gun connected, it will open fine.  When I connect the gun, it crashes.  This is happening on multiple computers, so I know it is not the computer having the issue.  The work around I posted before worked with the initial 1703 update, but

    This is starting to happen company wide.  I have halted the upgrade of the remote warehouses computer until I can get this figured out.  I am starting to think that WMDC is no longer compatible. 

    Oh, I don't believe I mentioned that the guns are using Windows Mobile with active sync.

    0 comments
  4. Anonymous
    2018-01-29T21:22:20+00:00

    Hi Scott,

    What can I suggest now is to use the Sync Center and see if it is being detected by your System. Plug-in your device then press Windows key on your keyboard and then type Sync Center. On the left-hand panel, click View sync results to see if the device is being detected.

    If the issue would still persist, then I recommend to remove the update and then prevent it from reinstalling in the future. Follow the instructions on this article on how you can remove and prevent updates.

    Update me if there are improvements.

    0 comments