Usually you have a vendor and a device id to identify the connected device on the bus
You’re right though, that in every different port it will get its own memory allocated an so on (at least I also believe that), but that’s no reason to not identify the already known device
there are a couple IDs in the device manager, if you look closely you will see where it changes, and then search the registry for that string and you will find how crazy Windows can be with USB hardware. Actually stripping out those ID’s is a huge pain. I only know because of having to make legacy hardware work for work
it was worse with USB1 and old drivers wouldn’t unload so then when you unplugged them and plugged them back in, sometimes they wouldn’t work unless you rebooted. Windows is stupid
Usually you have a vendor and a device id to identify the connected device on the bus
You’re right though, that in every different port it will get its own memory allocated an so on (at least I also believe that), but that’s no reason to not identify the already known device
there are a couple IDs in the device manager, if you look closely you will see where it changes, and then search the registry for that string and you will find how crazy Windows can be with USB hardware. Actually stripping out those ID’s is a huge pain. I only know because of having to make legacy hardware work for work
it was worse with USB1 and old drivers wouldn’t unload so then when you unplugged them and plugged them back in, sometimes they wouldn’t work unless you rebooted. Windows is stupid
Just check it with lsusb on Linux and you’ll see the device and vendor id stays the same, independent of the port - else no udev rules would work
Don’t know though what ever the fuck windows is doing…