none
Unable to install Windows Mobile Device Center on Windows 10 v 1709

    Question

  • I have just made a fresh (clean) install of Windows 10 x64 version 1709 and it is a total disaster. It is impossible to even install WMDC. Installer displays some useless message and that is all.

    Is there anybody who was able to at least install WMDC on Windows 10 1709?

    Andrew

    SOLUTION (ALL REQUIRED STEPS)

    My original question was about installing WMDC. Alexander has given a perfect solution. Unfortunately there are a few more steps required to make it working. This thread is long and has a few references to other threads. Below I will write a summary. Let's assume you want to make a clean (fresh) install of Windows 10 1709. Personally I have tested these steps on Home and Professional x64 Polish version. Some texts are translated from Polish - it is possible that the same text in English Windows version has a little different spelling.

    Install Windows 10 1709 and drivers required for your computer, connect to the internet and install updates.

    Install .NET 3.5. Select Programs and Features in Control Panel and then Turn Windows features on or off https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10

    Find orca.msi file on your old computer. It was installed as part of Windows SDK. If you don't have any read this: https://msdn.microsoft.com/en-us/library/aa370557(VS.85).aspx

    Tip from Rune:

    Download ISO file from here https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk and open it (Windows 10 can open ISO files, alternatively use 7-zip). Extract these files:

    Orca-x86_en-us.msi

    838060235bcd28bf40ef7532c50ee032.cab
    a35cd6c9233b6ba3da66eecaa9190436.cab
    fe38b2fd0d440e3c6740b626f51a22fc.cab

    Install orca.

    Download Windows Mobile Device Center from here https://support.microsoft.com/en-us/help/931937/description-of-windows-mobile-device-center. I'm using 64 bit version: drvupdate-adm64.exe

    Use 7zip to extract drvupdate-amd64.msi from drvupdate-adm64.exe. Read and work carefully. Do not confuse exe with msi.

    Open drvupdate-amd64.msi in orca and remove CustomAction MsiProcessDrivers.

    Save modified file and close ORCA.

    Install modified drvupdate-amd64.msi. The process should create c:\windows\windowsmobile\drivers with 4 folders inside.

    Start the original drvupdate-amd64.exe and WAIT. There is no window or any other visible activity - installer works in the background. You can observe the process in Task Manager or Sysinternals Process Explorer. Wait until:

    • CPU utilization is close to 0%
    • there is no drvupdate-amd64.exe process
    • there is only one msiexec.exe

    Now c:\windows\windowsmobile should contain the complete installation.

    Open PowerShell or command prompt as Administrator and run these two commands:

    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 your computer. Remember to be patient. Once I restarted my computer to early and the installation of drvupdate-amd64.exe was interrupted.

    Open Services (right click on Start, and then click on Computer Management => Services & Applications => Services) and find "Windows Mobile-2003-based device connectivity" (WcesComm) and "Windows Mobile-based device connectivity" (RapiMgr). You should see that both are working. For both of them right click, select Properties and on Recovery tab in "Subsequent failures" select the "Restart Service". Default option is to restart service after 1 minute. I have changed it to 0. These modifications are required because both services are stopped when you disconnect your device.

    Run Windows Mobile Device Center program from Start menu.

    Connect your device to USB port. Expected behavior: in the bottom right screen corner you should see that your device is being configured, a few seconds later device is ready, a few seconds later you should see in WMDC that device is connected.

    If you have any third party security software with firewall (I have ESET Internet Security) it is possible that your device will not connect to Windows Mobile Device Center.

    In default configuration firewall blocks communication for WcesComm service running in svchost.exe. It was enough to enable for Svchost/WcesComm:

    outgoing UDP, remote address 169.254.2.1, remote port 5679

    incoming TCP, remote address 169.254.2.1, local port 990

    To be sure that it will always work I have enabled communication for TCP and UDP in both directions for all port numbers and remote address 169.254.0.0/16 (maybe in your firewall you will need something like this 169.254.0.0/255.255.0.0 or 169.254.0.0 - 169.254.255.255)

    Searching for IP 169.254.2.1 I have found this old post (https://social.msdn.microsoft.com/Forums/en-US/b53de52c-a8ee-47f5-9eea-e1c37d02ced5/tcpip-transport-via-activesync?forum=netfxcompact):

    When you cradle your device, you should find a new IP address on the Desktop computer connected to the device, which you can obtain through the command "ipconfig":

    Ethernet adapter Local Area Connection 9:

            Connection-specific DNS Suffix  . :
            IP Address. . . . . . . . . . . . : 169.254.2.2
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            IP Address. . . . . . . . . . . . : fe80::8200:60ff:fe0f:e800%13
            Default Gateway . . . . . . . . . :

    The device actually will obtain an IP address as well, which is usually 169.254.2.1.

    Special thanks to Alexander for his invaluable tips. All this would be impossible without his help.

    Andrew





    • Edited by AnWu Tuesday, November 14, 2017 10:47 PM
    Sunday, October 22, 2017 6:07 PM

Answers

  • Hi.

    I had the same problem and was able to install. To be sure that it works, could you please repeat what I did? I made following (on Windows 1709 x64 in Hyper-V):

    1. Extract drvupdate-adm64.exe with 7zip. There is two files inside: driver-setup.exe and drvupdate-amd64.msi 
    2. Using Microsoft ORCA, open drvupdate-amd64.msi and remove CustomAction MsiProcessDrivers: just delete the row.
    3. Save this file, close ORCA and then install it. The process should create c:\windows\windowsmobile\drivers with 4 folders inside.
    4. Start the original drvupdate-amd64.exe and WAIT. It will take 2-3 minutes (at least, so long took it on Hyper-v) until it finished. Sometime you will not see any activities, but it works in background. Watch with Task Manager, until drvupdate-amd64.exe finished and the only one msiexec.exe is there.... Now c:\windows\windowsmobile should contains the complete installation 

    I was able than in Hyper-V VM to install the Device Emulator, Windows CE 5.2 Emulator Image and connect over DMA (Enh. Session should be off!)

    Please, let me know, if it works. 

    Best regards, Alexander 


    • Edited by Alexander Demidovich Tuesday, October 31, 2017 6:08 PM
    • Proposed as answer by SLNG IT Thursday, November 2, 2017 8:22 PM
    • Marked as answer by AnWu Friday, November 3, 2017 1:21 PM
    Tuesday, October 31, 2017 1:05 PM

All replies


  • Hi AnWu,

    thanks for posting here.

    For your case about Windows using, please go to Microsoft Community for suitable help.

    Your understanding and cooperation will be grateful.


    Best Regards,

    Yohann Lu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, October 25, 2017 7:06 AM
    Moderator
  • Hi Yohann

    Thank you for your suggestion. In my humble opinion there is no better forum than Smart Device Development => Windows Mobile Development for this type of question. How can we develop software for industrial devices with Windows CE/Mobile if we cannot install WMDC. It is enough that we have to use VS 2008. We don't want to and we cannot use Windows Vista for development because at the same time we have to use VS 2017. I hope there are some internal communication channels and you can forward this problem to proper people.

    And by the way I have tried to post to suggested Windows forum. Here is the result:

    {"ErrorMessage":null,"IsError":false,"Result":{"message":"Message must be 6 to 60000 characters long."},"Success":false,"CorrelationVector":null,"DependencyCorrelationVector":null}

    Nice JSON object. Perfect for people who are not developers. Of course my message have more than 6 and less than 60000 characters.

    Cheers,

    Andrew

    Wednesday, October 25, 2017 12:47 PM
  • Did you download the right version for your OS?

    https://support.microsoft.com/en-us/help/931937/description-of-windows-mobile-device-center

    Can you show what "System Information" shows on your PC for "OS Name" and "Version"?

    I just did a clean install of:

    OS Name Microsoft Windows 10 Pro
    Version 10.0.16299 Build 16299

    And downloaded the 64 bit version from the page linked above (drvupdate-amd64.exe). Installing that results in:

    WMDC Installer Error Dialog

    So, I contacted my support personnel (yeah, right!), extracted the exe using 7-zip and ran the installer msi with option /lv install.log:

    msiexec /lv install.log /i drvupdate-amd64.msi

    From the log we can see the following:

    MSI (s) (34:A8) [13:59:14:627]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI18B2.tmp, Entrypoint: ProcessDriverPackagesCustomAction MsiProcessDrivers returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)

    Browsing to C:\Windows\Installer (copy and paste that path into a file explorer window, you won't see that folder if you have "Hide protected operating system files (Recommended)" checked in your file explorer's view settings) shows that the file MSIxxx.tmp (whatever the temp name is on your system) does exist in that folder.

    So, let's rename this file to a DLL and use the dependency walker to see the dependencies. That takes a while to load, but then shows a bunch of errors because of "API-MS-WIN-CORE-XXXXX.DLL"s that are missing.

    A quick search on Google confirmed my suspicion that it would be a missing VC-Redist...

    So, let's install all VC-Redist packages for all older versions of VC

    Well... I've got VS 2015 installed on my PC (and VS 2008 as well) so no point in installing redist packages for VS2015, but none of the older redist packages help either, ugh...

    Ok, let's open this damn msi in Orca (it's in your VS installation, read this blog post).

    Orca shows the DLL it's trying to process is DIFxApp.dll

    A bit of Google search got me this little gem...

    So, anyway to get DifX installed on Windows 10?

    Well, I found a possible solution here:

    1. Download the WDK7.1 here.
    2. Mount the ISO (I use VirtualCloneDrive), install the WDK.
    3. Extract the drvupdate-amd64.exe using 7-zip
    4. Open the msi in Orca
    5. Click "Binary" on the left side
    6. Right click DIFxApp.dll and select "Drop Row" from the context menu
    7. Right click DIFxAppA.dll and select "Drop Row" from the context menu
    8. Right click in empty area on the right side and select "Add Row"
    9. Navigate to the location of the DIFxApp drivers in the DDK (in my case D:\WinDDK\7600.16385.1\redist\DIFx\DIFxApp\WixLib\amd64)
    10. Add both the DIFxApp.dll and DIFxAppA.dll files, making sure the row name is the same as the DLL file name
    11. Save the MSI file
    12. Install

    Unfortunately, still no go...

    So, next try...

    Unpack the msi with 7-zip. This gives us a bunch of dlls, inf files, etc. Looking at the MSI in more detail with Orca shows us that it will install all RNDIS DLLs into \Windows\System32\Drivers\RNDIS, so let's do it all manually:

    1. Create an RNDIS folder in \Windows\System32\Drivers
    2. Copy all RNDIS_*.DLL files into the \Windows\System32\Drivers\RNDIS folder
    3. Copy the RNDIS_*.inf and cat files into the \Windows\System32\Drivers\RNDIS folder
    4. Create a Serial folder in \Windows\System32\Drivers
    5. Copy all RNDIS_*.DLL files into the \Windows\System32\Drivers\RNDIS folder

    etc. etc. It may be possible to do this all manually and get it to run fine on Windows 10, but I'm running out of will to fix this. Someone else, please take over... ugh!

    Please report back here if someone finds a working solution for this!


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, October 26, 2017 1:35 AM
    Moderator
  • As a final attempt I tried to make a WIX installer out of the MSI. That almost works, apart from an ICE27 error I don't know how to fix...

    Using Dark.exe from the Wix Toolset, and fixing several small items, this is the final Wix XML (can't post it all here because the xml is too large).

    Unfortunately, building this results in the following error:

    WMDC.wxs(866,0): error LGHT0204: ICE27: 'RemoveExistingProducts' Action in InstallExecuteSequence table in wrong place. Current: Selection, Correct: Execution

    It seems to be caused by this part of the XML:

            <InstallExecuteSequence>
                <Custom Action="CheckIfWpdPresent" After="LaunchConditions">NOT (REMOVE="ALL")</Custom>
                <Custom Action="AbortIfWpdNotPresent" After="CheckIfWpdPresent">NOT (Installed OR (REMOVE="ALL") OR (WpdPresent="1"))</Custom>
                <Custom Action="UpgradeError" After="FindRelatedProducts">NEWPRODUCTFOUND</Custom>
                <Custom Action="MsiProcessDrivers" After="DuplicateFiles" />
                <Custom Action="MsiCleanupOnSuccess" After="InstallFinalize" />
                <RemoveExistingProducts After="MigrateFeatureStates" />
            </InstallExecuteSequence>

    I'm hoping there is somebody on this forum with a good understanding of WIX/MSI that can help fix this issue. Maybe then we will be able to create a Windows 10 WMDC installer that actually works.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, October 26, 2017 3:27 AM
    Moderator
  • Ok, changing

    <RemoveExistingProducts After="MigrateFeatureStates" />

    to

    <RemoveExistingProducts After="InstallFinalize" />

    fixes the build, but unfortunately I get the exact same error in the installer build by Wix.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6


    Thursday, October 26, 2017 3:41 AM
    Moderator
  • Ok, so... reading this and this.

    From those discussions I hope Microsoft is going to follow their own recommendations and will provide the WMDC drivers via Windows Update (or using Device Configuration or SetupAPI).

    Microsoft; is there any plan to support WMDC on Windows 10 through Windows Update?

    The other option is for someone to re-write the installer to use the Device Configuration framework or the SetupAPI...


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, October 26, 2017 4:34 AM
    Moderator
  • Hi Michel

    I have made similar tests: extracting driver installer, logging, checking dependencies - to no avail.

    Similar thread has been started here:

    https://social.technet.microsoft.com/Forums/windows/en-US/557e9694-0e45-409e-9bb9-8a7139eb2088/windows-mobile-device-center-wont-install-on-windows-10-fall-creators-update

    but currently there is no solution.

    Andrew

    Thursday, October 26, 2017 5:52 PM
  • Hi Folks,

    Would this thread help?  https://social.msdn.microsoft.com/Forums/en-US/bbf0f1db-3e8c-42df-b47b-e0fb855d74fc/windows-mobile-device-center-wont-open-nor-reinstall?forum=windowsmobiledev  The original thread is a little dated but the latest poster seems to have had some success but I am not sure if it is the same issue as you are discussing.

    Sincerely,

    IoTGirl

    Friday, October 27, 2017 4:32 AM
    Moderator
  • Nope, that deals with issues AFTER installing WMDC. On the latest Windows 10 build, WMDC can't be installed anymore AT ALL.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Friday, October 27, 2017 4:51 AM
    Moderator
  • I have opened a support case today for this. Hopefully this opens additional channels to get a solution...
    Monday, October 30, 2017 6:59 PM
  • Thanks Uwe!

    Please, if you can, report back here if you hear back from MS support.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Monday, October 30, 2017 8:46 PM
    Moderator
  • Hi.

    I had the same problem and was able to install. To be sure that it works, could you please repeat what I did? I made following (on Windows 1709 x64 in Hyper-V):

    1. Extract drvupdate-adm64.exe with 7zip. There is two files inside: driver-setup.exe and drvupdate-amd64.msi 
    2. Using Microsoft ORCA, open drvupdate-amd64.msi and remove CustomAction MsiProcessDrivers: just delete the row.
    3. Save this file, close ORCA and then install it. The process should create c:\windows\windowsmobile\drivers with 4 folders inside.
    4. Start the original drvupdate-amd64.exe and WAIT. It will take 2-3 minutes (at least, so long took it on Hyper-v) until it finished. Sometime you will not see any activities, but it works in background. Watch with Task Manager, until drvupdate-amd64.exe finished and the only one msiexec.exe is there.... Now c:\windows\windowsmobile should contains the complete installation 

    I was able than in Hyper-V VM to install the Device Emulator, Windows CE 5.2 Emulator Image and connect over DMA (Enh. Session should be off!)

    Please, let me know, if it works. 

    Best regards, Alexander 


    • Edited by Alexander Demidovich Tuesday, October 31, 2017 6:08 PM
    • Proposed as answer by SLNG IT Thursday, November 2, 2017 8:22 PM
    • Marked as answer by AnWu Friday, November 3, 2017 1:21 PM
    Tuesday, October 31, 2017 1:05 PM
  • Hi Alexander,

    thank you very much for your idea. I can confirm that after following your procedure all services on my physical machine where installed and were able to start.

    I'm not at the office today so I cannot check the device connectivity but I will do that first thing in the morning. I get back to you with the results.

    BTW, MS Support's first response was "Product is not supported on Windows 10 so we cannot put time into finding a solution". But they want to discuss workarounds. We'll see. 

    Best regards

    Uwe

    Tuesday, October 31, 2017 3:19 PM
  • Hi Uwe,

    I have installed the physical 1709 and connected per USB one MC9190, which I have here. It works! So, next 6 month until 1803 are safe now :)

    The issue is actually not with WMDC itself, but with AcLayers.dll - the SHIMS library. The background: Windows Installer MSIEXEC.EXE, which is in standard Windows delivery, is "shimmed" with VistaRTMVersionLie. There is something wrong with the implementation of this shim in 1709 AcLayers.dll in NS_VistaRTMVersionLie::APIHook_GetVersionExA - the stack overflow is happend in this function. I'm pretty sure, MS could easily solve it (I think, it is actually a bug)

    Best regards, Alexander 

    Tuesday, October 31, 2017 3:47 PM
  • Well, for me this screen shows for about 30 seconds, then disappears and nothing happens. I tried uninstalling everything, reinstalling as per instructions by Alexander, but no joy..

    

    Note that the installation is indeed successful in the two-step approach. The \Windows\WindowsMobile folder contains the full installation now, but I just don't get WMDC to start on my machine...


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6


    Tuesday, October 31, 2017 7:06 PM
    Moderator
  • Hi Michel,

    please, check if the both services (wcescomm and rapimgr) have SvcHostSplitDisable (more here)

    Best regards, Alexander 

    Tuesday, October 31, 2017 8:20 PM
  • That didn't do it either. What did it for me was setting both the WcesComm and RapiMgr services (that's what they are called on my machine) to:

    Then at least WMDC starts up, but I still can't get any device to connect. The devices are set to use USB Serial and I see the device under Mobile devices in the device manager:


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Tuesday, October 31, 2017 11:22 PM
    Moderator
  • Does Sync Center work?  I don't have a device to try at the moment but I was able to find it on my Windows 10 PC

    http://windows10helper.com/windows-mobile-device-center-for-windows-10.html

    Wednesday, November 1, 2017 2:02 AM
    Moderator
  • Nope, no joy...

    Sync Setup says "There are no new sync partnerships that can be set up on this computer.", even though the device is connected under Device Manager->Mobile devices->Microsoft USB Sync.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Wednesday, November 1, 2017 2:59 AM
    Moderator
  • If this is indeed the new WMDC it may be in support so you might get more traction reporting that error rather than against installation of WMDC.
    Wednesday, November 1, 2017 5:28 AM
    Moderator
  • Hi Alexander,

    it's working, tested with an Omnii XT15. Copying files, deploying software and the debugger of VS2008 all well:-)

    I forwarded your analysis to MS and they will check into it (assuming that WMDC is not outside of the support boundaries).

    I'll get results in a few days and will post them here.

    Thanks again for your help!

    Best regards

    Uwe

    Wednesday, November 1, 2017 10:45 AM
  • Hi to All,

    the official verdict is here:-(.

    WMDC is out of support and we are on our own.

    Thanks to Alexander it seems we are fine until 1803. Hopefully they have fixed the Bug in aclayer.dll by then.

    Michael, what is your status?

    Best regards

    Uwe

    Wednesday, November 1, 2017 7:25 PM
  • I'm still no go here...

    WMDC starts up fine now, but I just can't get it to connect to the device. The device shows up correctly as Microsoft USB Sync device under Mobile devices in the Device Manager, but WMDC does not connect.

    WcesComm and RapiMgr services are started, they both have SvcHostSplitDisable set to dword:1, they both are logged on with the "Local System account" and "Allow service to interact with desktop" checkboxes set.

    WMDC connection settings are set to:

    Control Panel -> Sync Center -> Sync Setup keeps reporting "There are no new sync partnerships that can be set up on this computer".

    So yeah, no go and nothing left to try I think. This is a fresh Windows 10 x64 build 1709 installation (not upgraded but a real fresh clean install).


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Wednesday, November 1, 2017 10:51 PM
    Moderator
  • Hi Michael,

    please try to switch the "Allow Connections to one of the following" to "DMA".

    In my experience the Bluetooth setting doesn't work. 

    Another thing: I have set the registry keys recommended by Alexander and now the services run with their default user "Local Service"

    Best regards

    Uwe

    Thursday, November 2, 2017 5:25 AM
  • No change. I don't think setting DMA has any effect on being able to connect a REAL device (I think DMA connections are only used for CE emulators running on the same PC as WMDC).

    So, unfortunately the end-result is that it is still not working for me.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, November 2, 2017 9:51 PM
    Moderator
  • Hi Alexander, Uwe, Michel

    First I would like to confirm that I was able to install WMDC - thank you very much Alexander. Then I have applied a "registry hack" to WcesComm and RapiMgr services - thanks again Alexander. Now I can start WMDC. Unfortunately my device doesn't connect, so I'm in exactly the same situation as Michel. I have changed both services to "Local System account" and "Allow service to interact with desktop" - no luck either.

    Uwe, I don't have DMA setting in "Allow Connections to one of the following" combobox. Only Bluetooth and Infrared. But I think it doesn't matter because I want to use USB (Allow USB connections - checked).

    I have a fresh Win 10 x64 Pro 1709 on real hardware (not virtual machine). What is the difference between our machines and software? I have Windows with Polish language and locale. In Poland we have comma as decimal separator. I think it is not important but who knows?

    My steps so far:

    1. Install Windows with all drivers (video, audio, etc.)
    2. Install all available updates (Windows Update)
    3. Enable Hyper-V, configure virtual switch (it is laptop with only one WiFi card, no ethernet)
    4. Enable .NET 3.5
    5. Install some other software like Firefox, 7zip, Adobe Reader, Sysinternals, and many more tools
    6. Install VS 2008
    7. Install WMDC
    8. Install more tools like Windows Mobile 6 SDK, Motorola EMDK, ...

    To test WMDC installation I have restored my system from backup (steps 1-5, without VS 2008). Then I have installed WMDC. Is it possible that there is something in VS 2008 what is required to connect device to WMDC?

    Andrew.


    • Edited by AnWu Thursday, November 2, 2017 10:03 PM
    Thursday, November 2, 2017 10:01 PM
  • I have a fresh install on Windows 10 x64 Pro 1709 (US English), VS2008 + WEC7, VS2015 + WEC2013, WMDC installed.

    No go, so we can eliminate the Polish language being a problem for sure...

    Uwe, Alex; what version of VS + WEC do you have installed?


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Thursday, November 2, 2017 10:34 PM
    Moderator
  • Hi Alexander! I also can confirm that your Solution is perfectly valid!

    Thank you so much!!

    Friday, November 3, 2017 12:23 PM
  • Hi Michael and Andrew,

    I honestly do not know what the "Allow Connections to one of the following" does. In my experience switching its values allowed me to connect again, that's all.

    I have VS2008, VS2010, VS2015 and VS2017 installed. German WIndows. no CE7, no CE2013.

    It was an update from 1703.

    Hope that helps.

    Best regards

    Uwe

    Friday, November 3, 2017 12:56 PM
  • Hi Andrew,

    DMA Option will appear, if the device emulator has been installed (the one is included in VS2008). You can recognize it, if the folder c:\program files (x86)\Microsoft device Emulator\1.0 is there. The amd64 System will have the additional folder in c:\program files. There should be SERDMAAsPlugin.dll 

    I had the clean installation of 1709 with all updates and without VS2008. The WMDC option , mentioned by Uwe, had only two parameters: Bluetooth and Infrared. Now, after installing of VS2008 with SP1 and them EMDK and some WM Powertoys, there are 3 parameters - Bluetooth, Infrared and DMA.  MC9190 still connects without any problem.

    After modifying the registry for both services and reboot, please make sure, they are both owned by the same process (Task Manager, the "Services" tab). I didn't change them to Local System account - both are running under Local Service.

    This is how it looks on my PC:

     Can you probably update c:\windows\inf\setupapi.dev.log somewhere? 

    Regards, Alexander 

    Friday, November 3, 2017 4:54 PM
  • Hi Michel

    Finally I was able to connect my device. Try the following:

    Install Windows 1709 (fresh copy).

    Connect to the internet and install updates.

    Install .NET 3.5 (select Programs and Functions in Control Panel and then Add/Remove Windows Features - this is my own translation from Polish, so maybe English names are a little bit different).

    Install WMDC as described by Alexander (first install "hacked" MSI, then EXE - remember to wait, installer works in the background).

    Add two registry entries as described by Alexander in separate thread. For your reference I repeat it here: Open PowerShell as Administrator and run these two commands:

    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 your computer.

    Run Windows Mobile Device Center program from Start menu.

    Connect your device to USB port. Expected behaviour: in the bottom right screen corner you should see that your device is being configured, a few seconds later new message "device is ready", a few seconds later you should see in WMDC that device is connected.

    That was my experience. I have repeated these steps two times with the same results. After that I restored my previous fresh Windows 1709 from backup. To remind you it has a lot of tools installed. I have installed WMDC, connected my device and ... nothing. I have uninstalled ESET Internet Security 11 (the newest version) and now I'm able to connect my device again! It looks that WMDC works correctly - thank you Alexander for all suggestions and perfect solutions. Michel - if you have any antivirus or other suspicious program uninstall it and check again. I hope you will find a solution. Let us know which program is guilty.

    UPDATE: the real problem was firewall in ESET Internet Security. In default configuration it blocks communication for WcesComm service running in svchost. I'm not sure if these parameters are good for everybody, but for me it was enough to enable for Svchost/WcesComm:

    outgoing UDP, remote address 169.254.2.1, remote port 5679

    incoming TCP, remote address 169.254.2.1, local port 990

    Searching for IP 169.254.2.1 I have found this old post (https://social.msdn.microsoft.com/Forums/en-US/b53de52c-a8ee-47f5-9eea-e1c37d02ced5/tcpip-transport-via-activesync?forum=netfxcompact):

    When you cradle your device, you should find a new IP address on the Desktop computer connected to the device, which you can obtain through the command "ipconfig":

    Ethernet adapter Local Area Connection 9:

            Connection-specific DNS Suffix  . :
            IP Address. . . . . . . . . . . . : 169.254.2.2
            Subnet Mask . . . . . . . . . . . : 255.255.255.0
            IP Address. . . . . . . . . . . . : fe80::8200:60ff:fe0f:e800%13
            Default Gateway . . . . . . . . . :

    The device actually will obtain an IP address as well, which is usually 169.254.2.1. So now, when you want to connect to the Desktop's HttpListener, you would make a HttpWebRequest with the url being http://169.254.2.2:12345 assuming your HttpListener listens on port 12345.

    Note: Remember to make an exception for the port in firewall settings, if you are using Windows XP.

    Cheers,

    Anthony Wong [MSFT]

    Andrew






    • Edited by AnWu Saturday, November 4, 2017 1:34 AM
    Saturday, November 4, 2017 12:00 AM
  • Hi Andrew,

    good to know it works. You should probably update your initial post, that the firewall/antivirus is also for the issues responsible. There is the note, that it doesn't work for you :)

    Alexander 

    Tuesday, November 7, 2017 8:35 AM
  • Alexander, I was waiting for some good news from Michel. I have updated my original post. Now it contains a complete step by step instruction. I would like to thank you very much for your help. If you ever come to Warsaw I will buy you a beer (or a few)

    Andrew

    Tuesday, November 7, 2017 1:08 PM
  • Thanks for this. It is crazy that Microsoft continues to break this in new ways with each release. Have you found a fix for copying .lnk (shortcut) files over to the device? Current working around it using cecopy. 

    Thanks again,

    Shawn

    Thursday, November 9, 2017 9:56 PM
  • Your suggestion worked fine with: Win10 Enterprise 1709 build 16299.19 with ESET Endpoint AV.

    Orca did I found here - and install just what you need, like this:

    https://developer.microsoft.com/nb-no/windows/downloads/windows-10-sdk

    Download the iso and extract it with 7-zip following files in a folder:

    Orca-x86_en-us.msi
    838060235bcd28bf40ef7532c50ee032.cab
    a35cd6c9233b6ba3da66eecaa9190436.cab
    fe38b2fd0d440e3c6740b626f51a22fc.cab

    Install then ORCA using the msi  - and use: find - orca to run the msi editor on "drvupdate-amd64.msi"

    Enjoy!

    Rune :-)


    Tuesday, November 14, 2017 6:01 PM
  • This didn't work.  The one cab file wasn't recognized.


    Tom O'Connor

    Thursday, November 23, 2017 12:02 AM
  • https://support.waspbarcode.com/kb/articles/windows-10-fall-creators-update-v1709-windows-mobile-device-center-fails-to-install-or-uninsta

    Best wishes,

    Damir

    Tuesday, November 28, 2017 2:32 PM
  • This condition of Windows 10 1709 appears to be corrected (at least in so far as it acts like 1703) as of the November cumulative update (https://support.microsoft.com/en-us/help/4051963).

    The condition that first appeared in 1703 where the 2 windows mobile services were not loading in the same service host (and thus could not communicate with one another) will still exist but that can be resolved with the SvcHostSplitDisable related tweaks that you already know about.


    May we all make money in the sequel.

    Thursday, December 28, 2017 9:56 PM
  • thanks Alexander and Andrew, worked for me.

    regards Hermann

    Wednesday, January 3, 2018 12:02 AM
  • The need for running the modified .msi has been resolved by a Windows Update.  I'm not sure which update has this fixed in it first, but I have confirmed that KB4054517 no longer requires the use of the modified .msi.

    To get WMDC working properly (as of 22 Jan 2018, on a Win10 1709 PC), follow these steps:

    1) Ensure the latest Windows Updates are applied (or at least KB4054517 is installed).

    2) Enable the .net 3.5 feature.  (hit "Start" and type "Turn Windows Features on or off", and check the .NET Framework 3.5 box and hit OK).  Alternatively, you could wait for the WMDC installer to prompt to install .net, but I have found this method to be more reliable.  Often times the other way to install .net 3.5 will fail the first time.

    3) Install WMDC using the regular .exe (found here: https://support.microsoft.com/en-us/help/931937/description-of-windows-mobile-device-center)

    4) Set these two registry keys:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RapiMgr]
        “SvcHostSplitDisable”=dword:1
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WcesComm]
        “SvcHostSplitDisable”=dword:1

    5) To fix issues with WMDC closing after disconnecting a devcie, follow the steps here: https://answers.microsoft.com/en-us/mobiledevices/forum/wp6n-sync/windows-mobile-device-center-fails-to-launch/191e6a44-df8b-4ef3-a772-91d04c299435?auth=1

    6) Reboot (to get the two registry keys above to take effect).

    In most cases at this point, the Windows Mobile device will still not connect.  If this happens, uninstall WMDC (Start-Settings->Apps, uninstall both "Windows Mobile Device Center" and "Windows Mobile Device Center Driver Update"), and then re-install WMDC using the same .exe.  After this second install, WMDC should be working.

    • Edited by Zeb JS Tuesday, January 23, 2018 12:15 AM
    • Proposed as answer by Farlop Friday, February 2, 2018 7:33 AM
    Monday, January 22, 2018 11:01 PM
  • thanks for the update Zeb!
    Wednesday, January 24, 2018 5:23 PM
    Moderator
  • Hi Zeb,

    thanks for Info. Seems, MS has decided to fix the SHIMS libraries. I'm pretty sure, because they have received a LOT of dumps  :)

    Alex

    Thursday, February 1, 2018 6:37 PM
  • Thank You Zeb JS - our Motorola / Zebra MC9200 is working again ;)

    There is one strange behaviour on different machines - if we cold boot the device Windows will end in an BSOD.

    I managed to find a few workarounds as described here -> h**ps://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/rndis-usb-driver-causing-bsod-on-windows-10-fall/b8420302-978c-4d7d-b5f6-2158174bf993?auth=1&rtAction=1518687999909

    Regards

    Martin



    • Edited by Martin Biro IV Thursday, February 15, 2018 11:15 AM Edit: Will also crash with by disabling the xHCI Interface
    Thursday, February 15, 2018 10:54 AM
  • Hi,

     I have just made a fresh (clean) install of Windows 10 x64 version 1709 Enterprise . It is impossible to even install WMDC. Installer displays message that "DLL required for this install to complete could not be run. Contact your support personnel or package vendor" .but  I have just made a fresh (clean) install of Windows 10 x64 version 1709 Pro  and WMDC Install very good and run.WHY?

    Is there anybody who was able to at least install WMDC on Windows 10 1709 Enterprise?

    please help me

    Javad 

    Saturday, February 24, 2018 6:44 PM
  • It's best to search this forum before you post.

    This thread has all the info you need.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6


    Saturday, February 24, 2018 8:32 PM
    Moderator
  • Thank you Alexander. This worked for me.
    Monday, March 5, 2018 4:15 PM
  • windows mobile device center Not Working on my lenovo laptop windows 10 pro 64 bit. I have 3 desktop computers with windows 10 pro and it work fine on them. can it be a bad setting? the WMDC starts with the green rectangle but then it just disappears it doesn't seem to attempt a link. This is my field computer, it does me absolutely no use if I can't hook it up to the data collector. the field device is window CE 6.5 pro.

    thanks

    Friday, March 9, 2018 1:40 AM
  • Alexander, thank you very much for this solution to this problem that drove me crazy

    Dominique

    Friday, March 9, 2018 9:32 AM
  • Hi Alexander,

    many thanks, It's works!

    Alessandro

    Thursday, March 29, 2018 7:16 PM
  • Hello,

    After all steps I got a problem when WMDC says that device is connected (connected only in settings but in main window not connected), but in Device manager I see only Microsoft USB Sync. Apps which I used to configure devices doesn`t see it.

    I use Datalogic Configuration Utility with Datalogic Falcon X3+

    Any ideas?

    Best Regards 

    Kamil


    • Edited by Kamil D Tuesday, April 3, 2018 12:15 PM
    Tuesday, April 3, 2018 11:07 AM
  • Hi Kamil,

    What advice does Datalogic provide?  WMDC is really only a transport layer so you will likely need to work with Datalogic for the specifics of their connection.

    Sincerely,

    IoTGirl

    Tuesday, April 3, 2018 3:14 PM
    Moderator