Bug #4169: Windows upgrade failure - CHIRP

Actions

Copy link

Bug #4169

closed

Windows upgrade failure

Added by Dennis Fox over 7 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

10/29/2016

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

(All models)

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Bad news...

After windows 10 upgraded to ver 1607 (anniversary edition) build number 14393.351 yesterday, Chirp has stopped functioning. It worked fine up to the build just before that (200 something).

Double Click on the Icon or the exe file and the blue rotating circle appears for about 15 seconds and then NOTHING. Same if you single click and select execute. I have tried Vista, Win 8, even XP compatibility mode... no help there either. Just the blue circle then nothing.

Tried uninstalling, reinstalling, etc. No help. (By the way the Icon now has the Administrator shield on it and always runs as admin privileged. Can not get that to go away even with a new install. That must be stuck in the registry, so maybe a registry edit might help, but I am not that sophisticated.

By the way, I had the usb cable working perfectly, etc. NO problem there...

Hope it is just me and my HP 2GB AMD64 PC, but I doubt it. (I can run the linux live ubuntu off the usb thumb drive, but when if I upgrade chirp, it does not run any more.
Sad!
Dennis Fox

Actions

Copy link

Updated by Jim Unroe over 7 years ago

Status changed from New to Feedback

Windows 10 has become famous for corrupting the chirp.config file. Once it becomes corrupted, CHIRP won't launch.

What you have to do is delete or rename the chirp.config file and the next time you launch CHIRP, it will create a new one.

But before you delete it, please upload the corrupt chirp.config file to this issue. It might be possible for a CHIrP developer to study the file and figure a way to have CHIRP repair it, or at least detect it and possibly replace it.

The chirp.config file is stored in the same folder as the debug.log file so follow the instruction on the "How To Report Issues":http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues page which explains how to find the debug.log file.

Jim

Actions

Copy link

Updated by Dennis Fox over 7 years ago

Hello Jim:

Well, you are correct, and deleting the chirp.config did the trick.

I would attach the file, but had already modified it prior to your response. I can tell you what was in it tho...

one line of spaces with a capitol "L" at the end, followed by three lines of spaces. Nothing else. I chirp were to test for a config starting with spaces, that should allow it to detect the windows caused error. Then delete and re-start...

Dennis

Actions

Copy link