

This driver is unsigned, so driver signature enforcement (introduced in 1607 build) should be disabled.

( rohitdubey12's posts here ht_tps://_com/Forums/en-US/4a25ff63-b421-4a23-856f-acbfcfd93f83/support-for-resource-hub-proxy-rhproxy-driver-in-ltsb-branch?forum=WindowsIoT )ĭriver (zip with rhproxy.inf and rhproxy.sys) is attached. We are using Win 1607 LTSB, with build does not include Resource Hub proxy driver (rhproxy) driver.īut this driver could be transferred from other builds (we used driver from 1903). There MSFT8000 devices should exist ( ht_tp://annabooks_com/Articles/Articles_IoT10Core/Windows-10-IoT-microIO-Requirements-on-IA-Rev1.6.pdf ). It can be verified by reading ACPI table via RWEverything ( ht_tp://rweverything_com/downloads/RwPortableV1.7.zip ). After OS IMAGE ID switch in bios to Win 10 IOT Core, 5 new devices are listed in Device Manager.
