I've got 3xMoonlander2's and 2xNewpacs both mining on a W10 machine. I had them all on the same hub, and called out the Newpac addresses in their .bat files to keep the miners from scanning & finding the moonlanders. Before I did this, cgminer would see the moonlanders and not know what to do with them - throwing up an error.

In the process of moving the moonlanders to a 2nd hub, I think the address of the first hub changed, so now my "--USB 2:4,2:3" is incorrect because the miner doesn't find the newpac at that address. I've tried digging around in device manager to figure out the address again but nothing I've tried works.

I removed the --USB argument from the bat's and have them mining again, with the constant "ML WTF is this" errors scrolling by.
I have them both called out by serial number individually in their respective bat's. That doesn't stop CGminer from scanning and seeing the moonlanders.
It wasn't until I called out the USB ports via the --USB tag that I got it to stop scanning. And it was all working fine until I added the 2nd USB hub.

How can I definitely determine the (new?) address of my newpacs so the cgminer knows where to find them and not bother scanning for other devices?