Context Navigation

Changes between Version 2 and Version 3 of Ticket #15060, comment 31

v2	v3
7	7	~~Leaving this open because I think !VirtualBox shouldn't be trawling around inside the completely undocumented {{{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces}}} to discover available network interfaces (and getting the wrong data when duplicate interfaces with the same description are present)~~.
8	8
9		!VirtualBox uses INetCfg <https://learn.microsoft.com/en-us/previous-versions/windows/hardware/network/ff547694(v=vs.85)> to enumerate network interfaces which, I guess, is trawling through {{{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces}}}. In doing so, ¬VirtualBox needs account for fact that the interface description is //not// unique across the interfaces returned by INetCfg.
	9	!VirtualBox uses INetCfg <https://learn.microsoft.com/en-us/previous-versions/windows/hardware/network/ff547694(v=vs.85)> to enumerate network interfaces which, I guess, is trawling through {{{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces}}}. In doing so, !VirtualBox needs account for fact that the interface description is //not// unique across the interfaces returned by INetCfg.
10	10
11	11	And a hearty curse at Windows for keeping the crucial registry key that would have let me solve this problem years ago locked away in a way that prevents administrators from even reading it. God, I wish I could bill Microsoft for the many hours of my life that they have wasted.