There have been reports of issues with Bridged and host-only on Windows 10. I would look for a ticket at bugtracker and provide your information to the DEVs. They would like to see why some have this issue and some do not.
I had the same error just after I install virtualbox. After I rebooted the hostadapter showed up. I think the bigger problem is that VirtualBox does not seem to clean up the registry properly. Unfortunately I am not a windows programmer, so I am not sure how to go about and solve this issue.
I had lots of problems with Virtualbox and the host adapter. After I deinstalled and run ccleaner,resintalled 4 again, deleted it, then reinstalled 5.0, I am still having issues with the hostonly adapter. I went through the registry and found a number of keys that were left behind. Some of them I found searching for Host-Only.
There probably is some indirect key that is being missed on removal, but causes issues with installation. I saw a similar network problem years ago. I asked Microsoft if they knew where all the registry entries were that affected a Nic with a DHCP address. They told me no. That was years ago, and there a much better tools now to figure this stuff out. (I am told) but I cannot help. This problem seems to have gone on for years and a weird entry, hard to find, could explain the issue.