@Sawyer-McBride is a scholar of high order. So elementary I never even considered it. With an alternate cable, the device manager successfully reported the mini dock as a serial COM port of which I can connect with my terminal client. Will test on my other computers and report back.

@Sawyer-McBride is a scholar of high order. So elementary I never even considered it. With an alternate cable, the device manager successfully reported the mini dock as a serial COM port of which I can connect with my terminal client. Will test on my other computers and report back.

@Boken-Lin I did that on all of the systems, three of them. Two windows 10 and one windows 8.1 workstation.

@Boken-Lin Yes, previously it was operational. It was operational since I received the device last and first used it Tuesday. Upon connecting to three Windows 8.1 systems and installing the cp210x driver I was able to connect using the wired USB-to-Serial interface using SecureCRT and the device manager reported the COM port.

Conceding that the firmware has no relation to this issue, what else would cause the USB-to-Serial interface to cease operation?

More specifically:

I connected for the first time to the Arduino dock and powered via the micro-usb adapter, first noticing my system didn't recognize it as a host device for the Onion Omega or as an Arduino.

Then I reconnected the mini dock, thinking it was just the Arduino dock thing but also the mini dock ceased recognizing the host device. Then I updated the firmware and performed a factory reset but to no avail on restoring a serial connection.

I've upgraded the firmware to the recent release, 0.0.4 (b216,) and my systems no longer recognizes the Onion Omega as a usb-serial device on the mini-dock or arduino dock. I performed a factory reset, firmware version remains the same but still cannot access the Onion Omega via com port. I am able to connect to the console and web interface via the AP mode and in WiFi host mode.

Any help is much obliged