nickbeth
commented
2 weeks ago I'm unsure why this would happen, but it's likely the permission level of the app affects the processes it spawns, hence the usbipd commands that are run under the hood. I'm honestly unsure how to fix this, maybe usbipd allows to specify the user group that is mounted with?
While the commandline windows usbipd attaches a serial device (correctly) with permissions for group 20 (dialout), using the gui it gets attached with group 18 (not found).
As there seems to be logic on the windows side involved - where does the group id get defined?