Bug #10596
closedcould not open port 'COM9': PermissionError(13, 'Access is denied.', None, 5)
0%
Description
CN worked fine a couple of days ago. Opened it today and was told there was a newer version. Upgraded and attempted to program a radio and received an error that it cannot open the com port. The error persists on any com port and with any radio. Uninstalling and reinstalling CN didn't help, nor did rebooting the computer.
Updated by Doug Rehman over 1 year ago
Note: This was with both Prolific and FTDI chipset cables.
Updated by Jim Unroe over 1 year ago
Are you sure the correct port is COM9? Have you tried using the "Help me..." selection to have CHIRP-next guide you through the selection of the correct COM port?
Jim KC9HI
Updated by Doug Rehman over 1 year ago
Yes, I use Device Manager to confirm the correct com port when I plug in a cable.
Updated by Doug Rehman over 1 year ago
The FTDI was com9, the Prolific was com4. (I didn't capture that on the log as it gives the identical error, just with "4" instead of "9".)
Updated by Doug Rehman over 1 year ago
I believe I have fixed the issue by:
1) Uninstall Chirp Next
2) Delete CN installer and redownload
3) Use Regedit to find and delete every instance of "Chirp"
4) Reinstall Chirp Next
Apparently there was either some corruption in the previous install file download or something corrupted during the install.
Updated by Dan Smith over 1 year ago
- Status changed from New to Not a bug
There is no chance that a corrupted chirp install could result in the operating system returning a specific error message like that. What is possible is that something stuck running in the background was still holding onto the serial port (which Windows reflects as Access Denied for historical reasons). Reinstalling and such probably released that and that's why it works now. A reboot would probably have had the same effect. Either way, now resolved.
Updated by Doug Rehman over 1 year ago
From OP: "nor did rebooting the computer". The problem persisted AFTER the reboot—this was NOT an issue with something running in the background holding onto the com port. The only way to fix it was a complete removal of CN, including purging the Registry.