Hi Festum,
It seems that Windows 10 Build 10049 changed the way network components are identified. There no longer is a "ComponentId" value in the registry, instead the corresponding key is "MatchingDeviceId". This leads to NR service not detecting the TAP Adapter even though it is installed. A workaround is to add the "ComponentId" value to the registry.
Code:
ComponentId REG_SZ nrtap
The detailed steps :
Assume NR client has been installed.
1. run regedit, serch "nrtap" in HKEY_LOCAL_MACHINE\SYSTEM\ node
2. stop when found the nrtap driver node , that contains "MatchingDeviceId" key, value is nrtap
3. add a new string key "ComponentId" value is "nrtap"
4. restart nr client service from services.msc
Thanks,
KevinZ - NeoRouter team