Searching on your terms, I found this "solved" topic which seems to be a 2016 Windows (comm device: CH340/FTDI) driver issue. Your issue might be different.
Searching on your terms, I found this "solved" topic which seems to be a 2016 Windows (comm device: CH340/FTDI) driver issue. Your issue might be different.