h1. Running CHIRP Under Windows

{{>toc}}

Running Chirp under Windows is pretty straight-forward, but it has some traps to offer. You can run into a few situations in which a little doing is needed before Chirp starts correctly.


h2. Corrupt Chirp configuration file

If Chirp just does nothing when you try to start it, then its configuration file might have been damaged: Windows 10 has a bad habit of corrupting it.
Solution: Delete the chirp.config file. The next time CHIRP is loaded, a new chirp.config file will be created. The chirp.config file is kept in the same folder as the debug.log file (it might be in C:\Users\<user>\AppData\Roaming\CHIRP\chirp.config).


h2. Non-standard character in program path

CHIRP won't load when the Windows user account has a special character (accented characters, umlauts, characters which aren't in the latin alphabet) in it.
Solution: Put Chirp somewhere into a path which doesn't contain special characters.


h2. You get an "Error opening file for writing: c:\program files (x86)\chirp\_ctypes.pyd"

Solution: Run Chirp with Administrator privileges.