However, if you change that device to use the WinUSB driver instead, then reboot, it can be opened by that chrome app, and by other apps that use the chrome USB API. This can be seen with the 'USB Device Info' chrome app:

On Windows Vista 32 home basic, the chrome USB API will not open a usb connection to a Garmin 60CSx which is using the latest grmnusb driver (v2.3.1). The zadig / WinUSB workaround is less than ideal for this app, due to the user interaction required we'd like to find a solution or workaround that will just work out of the box. Here's the text of a help ticket I opened with Garmin I am wondering if anyone here might have ideas for a workaround / can verify that you see the same behavior? (I'll post any updates from them here for now, they just say that they cannot guarantee what the engineering department will do, if anything)