Yes, this is what I ended up doing; iterating over kIOSerialBSDServiceValue objects (which contain the BSD name), climbing up the parents of each one using IORegistryEntryGetParentEntry, until I find an entry with a "sessionID" property that is identical to the one from my original IOUSBDevice object.

This is the method in our codebase where the iterator is created: https://gist.github.com/PhilCS/bec23749b046435894b9e7d49057932a addedIter is eventually passed down to serialDevicesForIOIterator thru our USBDeviceInserted method.

Yes, I tried to use it as a workaround, but it failed and hit a dead-end after just one level down. I don’t fully understand the high-level goal of the code I’m dealing with, I’m just trying to fix some legacy method that unexpectedly started behaving differently in Monterey. I’ve only first started coding on macOS a month ago, so I’m still throwing things at the wall to see what sticks. Here's what I ended up doing, all the code I added is contained between the “Temporary fix” comments: https://gist.github.com/PhilCS/878c446a18b510397444ea770d6d1044

Yes, this is what I ended up doing; iterating over kIOSerialBSDServiceValue objects (which contain the BSD name), climbing up the parents of each one using IORegistryEntryGetParentEntry, until I find an entry with a "sessionID" property that is identical to the one from my original IOUSBDevice object.