You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible to have multiple network adapters with identical names. This is frequently observed when upgrading VirtualBox, which can leave behind bad virtual network adapters that can never be removed without taking extreme measures with the registry, or reinstalling Windows from scratch. This appears to also be possible with, in at least one case, USB network adapters, which can leave behind multiple orphaned adapters with the same names.
In this case, a user reports the presence of 16 identically named network adapters. Neither the "pro" nor "non-pro" Network Meters can handle this case properly. NetMonitor fails because stats from the invalid adapters overwrite valid one, and Rainmeter itself fails because it cannot retrieve stats by name because it finds the wrong adapter (presumably the first in the list). Rainmeter's Interface=Best option is the only thing that works correctly.
Enhance NetMonitor to attempt to exclude invalid adapters without excluding ones that are simply down or disconnected. Also, correct a bug in the non-Pro Network gadgets that do not properly report "session" stats when no network adapters are configured.
The text was updated successfully, but these errors were encountered:
It is possible to have multiple network adapters with identical names. This is frequently observed when upgrading VirtualBox, which can leave behind bad virtual network adapters that can never be removed without taking extreme measures with the registry, or reinstalling Windows from scratch. This appears to also be possible with, in at least one case, USB network adapters, which can leave behind multiple orphaned adapters with the same names.
In this case, a user reports the presence of 16 identically named network adapters. Neither the "pro" nor "non-pro" Network Meters can handle this case properly. NetMonitor fails because stats from the invalid adapters overwrite valid one, and Rainmeter itself fails because it cannot retrieve stats by name because it finds the wrong adapter (presumably the first in the list). Rainmeter's
Interface=Best
option is the only thing that works correctly.Enhance NetMonitor to attempt to exclude invalid adapters without excluding ones that are simply down or disconnected. Also, correct a bug in the non-Pro Network gadgets that do not properly report "session" stats when no network adapters are configured.
The text was updated successfully, but these errors were encountered: