Bug #9883
openChirp does not work after upgrading to Windows 11
0%
Description
Have been using Chirp to successfully program my Radioddity QB25. After upgrading to Windows 11 can no longer get comm port to open to connect and program the radio. Log file attached
Files
| debug.log (30.2 KB) debug.log | |||
| Prolific 3.8.40.0.png (17.8 KB) Prolific 3.8.40.0.png | First PL2303TA incompatible Windows device driver | ||
| Prolific 3.8.39.0.png (16.8 KB) Prolific 3.8.39.0.png | Last PL2303TA comaptible Windows device driver | ||
| 2021-01-28 08_15_58-Update Drivers - Prolific USB-to-Serial Comm Port (COM3).png (16.5 KB) 2021-01-28 08_15_58-Update Drivers - Prolific USB-to-Serial Comm Port (COM3).png | Selecting the v3.2.0.0 Windows device driver |
.png){kind=link}
Updated by Jim Unroe almost 2 years ago
- File Prolific 3.8.40.0.png Prolific 3.8.40.0.png added
- File Prolific 3.8.39.0.png Prolific 3.8.39.0.png added
- File 2021-01-28 08_15_58-Update Drivers - Prolific USB-to-Serial Comm Port (COM3).png 2021-01-28 08_15_58-Update Drivers - Prolific USB-to-Serial Comm Port (COM3).png added
- Status changed from New to Feedback
CHIRP runs fine with Windows 11. What may not be running fine with Windows 11 is your programming cable.
The Prolific PL2303TA USB to Serial Bridge Controller was considered end-of-life (EOL) at the end of 2020 ("see this page":https://www.prolific.com.tw/US/ShowProduct.aspx?p_id=153&pcid=41). As was done with the PL2303HX chip around 10 years ago, the v3.8.40.0 (and later) device driver that Prolific supplies to Microsoft to be installed by Windows when a PL2303TA chip is detected has been designed to not support this EOL chip.
The work around for the PL2303HX chip was to download, install and select a driver version that was available prior to support being dropped for the EOL chip (v3.3.2.105 or before -- v3.2.0.0 recommended). For the PL2303TA chip that means downloading, installing and selecting a Prolific device driver v3.8.39.0 or before.
I just install the Prolific v3.2.0.0 device driver across all of my Windows computers (Windows 7, Windows 10 and Windows 11) since it will work with both my PL2303HX and PL2303TA chip based programming cables.
Another obvious solution is to use a programming cable that has a USB-to-Serial chip from another chip vendor (FTDI, Silicon Labs, WCH, etc).
Jim KC9HI
Updated by Joseph See over 1 year ago
I too am having issues with chirp running within Windows 11.
In Device Manager, my controller is successfully installed, labeling it COM 7. If I try to run chirp straight, or as administrator, it fails and then asks to check the log file. Opening it reveals:
Traceback (most recent call last):
File "chirpw", line 20, in
File "chirp\chirp_common.pyo", line 21 in
File "chirp\memmap.pyo", line 16, in
File "chirp\util.pyo", line 16, in
InportError: No module named six
At my wits end. I've tried uninstalling and reinstalling, even looking for older versions. I'm at a loss and truly hope someone can help. My Windows Version is Windows 11 Home [Version 10.0.22621.819]
Updated by Jim Unroe over 1 year ago
There is a bug in today's CHIRP daily build. It is being addressed and should be fixed tomorrow. In the mean time, download and install "yesterday's (20221119) build":https://trac.chirp.danplanet.com/chirp_daily/daily-20221119/.
Updated by Bernhard Hailer over 1 year ago
Is it good now, can we close the ticket?
Thanks.