It is worth asking if you are using the supplied, cable, but it is unlikely this is the cause of the problem. Trying different ports may change results in the case of signal quality.

Sometimes a different port can help or hurt.

If the issue is signal quality, then sometimes a HUB in-between can help or hurt.

Most charger cables would be able to detect device mode, but would fail during sustained data transfer.

The micro-B cable provided with the dev kit is very good quality.

For various reasons this might fail even if the hardware is good.

A running Jetson has a default sample of both a network interface and mass storage (read only).Similar if mass storage is not automatically allowed. For example, there may be settings to say to not use network adapters as a network device until ok’d. Security and other local settings can get in the way of using a device mode USB port.Windows does not know how to work with this custom device (recovery mode). Being able to see recovery mode is a good test of hardware function. This should never fail, otherwise it implies hardware error. By default a Jetson shows up as a custom device when in recovery mode.OTC accepts either, which is why the detect pin is needed. What shows up is completely custom to any computer which implements a B type connector.For the micro-B, device mode is triggered by the correct micro-B cable ID detect being seen by the Jetson.The port will only show up if it is in device mode.Before asking more, some USB info might be useful:

Windows 10 serial terminal