locked
Support for Resource Hub Proxy (Rhproxy) driver in LTSB branch RRS feed

  • Question

  • Hi,

    We're using Windows 10 enterprise IoT LTSB on an Intel x64 platform. We need Resource Hub Proxy driver to be able to interface with I2C and SPI buses. However, the driver seems to be missing from the LTSB builds.

    Is there a way to install it manually and/or is it planned to be included in the upcoming LTSB builds. 

    If it's specifically excluded from LTSB, is there another way to interface with I2C and SPI devices on the LTSB builds?

    It's not an option for us to use the CB/CBB builds.

    Any tips/guidance are appreciated, thanks in advance.

    -Rohit

    Tuesday, January 9, 2018 10:00 PM

Answers

  • Hello, rohitdubey12

        The Resource Hub Proxy driver service is a kernel mode driver. It exists in windows 10 only(Home,Pro, Education, or Enterprise),but it does not exist before 1709 version. Which version did you use? You can check whether the rhproxy.sys file exists in the %WinDir%\System32\drivers folder. If this file is missing you can try to restore it from your Windows 10 installation media.

    Best Regards,

    Michael


    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.

    • Marked as answer by rohitdubey12 Wednesday, January 10, 2018 2:18 PM
    Wednesday, January 10, 2018 7:23 AM

All replies

  • Hello, rohitdubey12

        The Resource Hub Proxy driver service is a kernel mode driver. It exists in windows 10 only(Home,Pro, Education, or Enterprise),but it does not exist before 1709 version. Which version did you use? You can check whether the rhproxy.sys file exists in the %WinDir%\System32\drivers folder. If this file is missing you can try to restore it from your Windows 10 installation media.

    Best Regards,

    Michael


    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.

    • Marked as answer by rohitdubey12 Wednesday, January 10, 2018 2:18 PM
    Wednesday, January 10, 2018 7:23 AM
  • Thanks for responding Michael.

    We're currently running version 1607 since that's the latest LTSB version available. I assume one of the future versions of LTSB would support RhProxy when the version number exceeds 1709. Do you know what's the next LTSB version and when would it be released?

    I tried installing the driver manually, but it complained about missing signature until I disabled Driver signature enforcement from the Safe Boot menu. 

    Thanks & Regards,

    Rohit

    Wednesday, January 10, 2018 2:22 PM
  • Hello rohitdubey,

       Sorry for that I don't know what's the next LTSB version and when the version with RhProxy service would be released. And more, i have no Windows IoT Core Enterprise LTSB to test installing the driver manually.

       I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay for this complex issue. Appreciate your patience.

    Best Regards

    Michael


    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.

    Thursday, January 11, 2018 3:11 AM
  • Hi Michael,

    Thanks for following up with this. Please keep me updated.

    I've been trying to install the RhProxy driver from a CB version into my LTSB version, but I can't find the associated cat file that is signed using a valid certificate.

    I've been able to generate a cat file using inf2cat tool in the WDK (and adding a "CatalogFile" entry to the inf file)
    I've been able to generate a cat file using inf2cat tool in the WDK (and adding a "CatalogFile" entry to the inf file)
    Friday, January 12, 2018 6:13 PM
  • I just did an investigation a couple weeks ago. The ACPI SSDT tables have to list MSFT8000 and have all the IO declared in it. The following guidelines are what are to be followed to setup the table: https://docs.microsoft.com/en-us/windows/uwp/devices-sensors/enable-usermode-access. Ideally, you want the board manufacturer to add support in the firmware.

    Here is my review of RHPROXY support in industrial PCs:

    http://annabooks.com/Articles/Articles_IoT10Core/Windows-10-IoT-microIO-Requirements-on-IA-Rev1.6.pdf

    RHPROXY has been part of IoT Core support since the beginning. Windows 10 LTSB 14393 1607 doesn't support RHPROXY. The next LTSB (or LTSC release as it has changed) has not been announced. So support for RHPROXY is only available in the latest CB (now SAC) release 1709.


    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Friday, January 12, 2018 9:31 PM
  • Hi Sean,

    Thanks for the response. I wish I had that review document while I was struggling with SPB and Resource Hub!

    Currently, we already have the MSFT8000 device listed in our ACPI table and the whole thing works fine in CB version. I've also been able to load the RhProxy driver from the CB version into the LTSB and have it working with test code.
    I just had to disable driver signature enforcement from the Safe boot menu, because I couldn't find the actual Security Catalog (.cat file) for the driver (The .inf file doesn't have the "CatalogFile" tag).

    Therefore, the only hurdle now is to find a way to get Rhproxy driver installed in current LTSB without having to bypass security. 
    I tried to create my own Security Catalog using the inf2cat tool, but I didn't have a valid certificate to sign it with, which again caused the device manager to block the driver install. Adding my test certificate to the Root CA doesn't seem to work either.
    I'd appreciate any suggestions you have for for this, CB is not an option for us and it sounds like the next LTSB has been slated for 2019 [#1#].

    Thanks & Regards,
    Rohit

    [#1#]:https://www.computerworld.com/article/3195318/microsoft-windows/enterprise-alert-microsoft-slates-next-windows-10-ltsb-release-for-2019.html

    Friday, January 12, 2018 10:11 PM
  • It was a nagging question since the launch of Windows 10. Your question to me directly, another client asking about IoT Core, and someone at Microsoft reaching out to me at the same time was the perfect time to get this covered. 

    When we talked via e-mail, I suggested that you contact Azius as they have the capability to sign driver files. The only issues is it legal to have RHPROXY on LTSB 14393 - This is a question that Microsoft has to answer. They might say it is not supported. I suggest you reach out to a distributor or your Microsoft contact to get this question answered.


    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Saturday, January 13, 2018 12:40 AM
  • Hi Michael,

    I'm just following up on your note about involving someone familiar with this topic to look into this.

    Has there been any updates on this yet?

    I was able to get the driver working on the LTSB version after disabling the driver signature enforcement, so I think all we need is a way to port this driver from from CB to LTSB, with a valid security certificate.

    Thanks & Regards,

    Rohit

    Monday, January 22, 2018 4:13 PM
  • Hi rohitdubey12,

    Please refer to Sean Liming's reply on 1/12/2018.

    Thanks,

    Jie


    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.

    Tuesday, January 23, 2018 1:20 AM