Windows Embedded Handheld 6.5 with Win10 CU - Rapimgr crashes on disconnect RRS feed

  • Question

  • My company resells and supports multiple devices that run Windows Embedded Handheld 6.5, and all of the customers that have updated to Windows 10 are having problems with the Creator's Update.  This looks like the right place to get the ball rolling. 

    For basic functionality, we already have to apply the following workarounds:

    • On the device, we disable the Advanced USB Networking option (which worked in prior Windows versions)
    • The RapiMgr and WcesComm services are reconfigured so that they run in the same servicehost instance instead of separate ones. I used the following commands to do that.
    • 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
    • The services are also set to use the LocalSystem account instead of LocalService because of other security errors that had come up.

    Our own application uses the RAPI to move files around, install software, and detect the presence of mobile devices.  However, I've determined that even with only microsoft components, connecting and disconnecting the mobile devices to the PC via USB results in the service crashing.  This is completely reproducible. 
    Error message below.

    Faulting application name: svchost.exe_RapiMgr, version: 10.0.15063.0, time stamp: 0x02799ef5
    Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xa329d3a8
    Exception code: 0xc0000008
    Fault offset: 0x00000000000a917a
    Faulting process id: 0x31c4
    Faulting application start time: 0x01d3233fc5b7116b
    Faulting application path: c:\windows\system32\svchost.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: 26735f97-2730-4ce8-9836-b7be8c8ad65f
    Faulting package full name:
    Faulting package-relative application ID:

    • Edited by Daniel Elm Friday, September 8, 2017 4:06 PM Corrected the product name
    Friday, September 1, 2017 8:21 PM

All replies

  • Hi Daniel,

    There are multiple paths for you.

    1. Report the error using the Windows Feedback App in Windows 10 so that logs can be collected 

    2. As you are a reseller, please reach out to the OEM as they can leverage their partner status with Microsoft to open an incident for review. Should the device require an OS update, you would have to work with the OEM to get a new image. If your company is a Microsoft Partner directly, then you could use that option as well but if the issue is at the device, the OM may need to be involved as previously stated.

    3. Navigate through and start an incident (This may have a cost associated)

    NOTE: There is no such product as WinCE 6.5.  You are likely asking about Windows Mobile 6.5 for Handheld devices and that is actually a derivative of Windows CE 5.  You can look up the lifecycle of Windows Embedded OS Products at



    Saturday, September 2, 2017 5:40 PM
  • Thanks IoTGirl.  I've corrected the model (which is really frustrating, because it's marketed in multiple ways from Microsoft and the various OEMs that have it preloaded).  It's definitely the version that's supported until 2020.

    I'll look into suggestion #1, and I've been pushing the OEMs on #2, but their support organizations are pretty fractured as this product line is an afterthought.
    I'm also working on #3, but I'm probably going to need to get the same OEMs involved.

    Friday, September 8, 2017 4:10 PM
  • Hi Daniel,

    Just to confirm, if you locate the originating exe, right click -> Properties -> Compatibility mode Windows Vista it still has the issue?  Unfortunately RAPI is far older than W10 and as it runs through service host permissions may be difficult to pass on.

    The OEMs are definitely the best option for routing the issue.



    Friday, September 8, 2017 5:04 PM
  • I've tried installing it both ways, with and without compatibility mode in place.  This change, and the configurations I've already done have been accepted as solutions for most people because they're only handling 1 mobile device, and when the disconnect crash silently occurs, they have no idea anything's wrong because the service silently restarts after 1 minute.

    In my case, my peers and my customers need to provision batches of mobile barcode readers, connecting them one after another to transmit data.  For security reasons, wireless is not an option.  Filling up their eventlogs with crashes does not make administrators happy either.

    I totally appreciate that RAPI is practically an antique, it's part of the featureset for that OS, which is supposed to be supported to 2020.  Yes, it's in extended support, but I'd hope that flat out reproducible crashes of the service, which is Microsoft from end to end (Inbox drivers, services, client and host Operating Systems) would fall under that umbrella. 

    Tuesday, September 12, 2017 12:26 AM
  • Hi Daniel,

    The other answer might be to run a VM with an older version of the OS that does support RAPI in the mean time.  For a fix, a request needs to get to the Sustained Engineering Team from one of the three routes I provide above.  Preferably from the OEM in case a change to the device is requited for the fix.



    Wednesday, September 13, 2017 3:58 PM