socratis wrote:You were told more than once where to look for. More than once. Windows, not VirtualBox. You seem to be stuck with the idea that somehow it's a VirtualBox problem. I will repeat it once more; it's not a VirtualBox problem, treat it as such.
The easiest thing you could try? Select the connection and press F2. Rename the connection. Done. And honestly, is this something besides a cosmetic error?
I have the same problem. The issue is that on Windows if software does not follow MS specs may corrupt things in Windows. So, your arguments are just plain unproven.
Rather than talking people down as stupid, you should really try working with people to find the cause, be it in VirtualBox or in Windows or somewhere between.
My problem also showed after upgrading Windows 10, but i am not sure if they were present even before.
Now, after deleting the adapter in the device manager there seems to be something left behind.
Installing VirtualBox afterwards shows "Cannot rename this connection. A connection with the name you specified already exists. Specify a different name." error. Even if it fails, it shows that (non-working) adapter in the Host Network Manager, which is weird, as it failed and should have not created an entry.
Please note, VirtualBox seem to have bad error checking here, i noticed that trying to create a host-only adapter may just hang, or it may return "An adapter with this name already exists" after minutes. In case of errors it seems to leave partially created adapters around.
But the tip with the registry is good, i will check this.
(i noticed this is a rather old post, but seem to be good information for me anyway - and seems to be relevant for VirtualBox 6.0 too).