The python interpreter in the compiled executable ran into an un-handled exception.
I'm constantly working on this project, and the next version will have better logging so that the log file can have some information to work with on these.
If I had to guess, I know there is a bug on second launch of a database that is corrupted. Deleting the settings.json file inside of the zip folder will fix this.
This is cause because the tool saves the last used database and reloads it on next launch.
Also depending on how/where you launch the tool from, it will try to make the log file in the directory you call from, leading to permissions errors.
So for example if you unzipped in C:\Users\username\cpviewinsights\
But you call the exe manually from cmd line in Windows at path C:\
It will try to make the log file in C:\ and this commonly leads to a permission exception.
Other than that I apologize I'm not sure, lookout for next version here probably by next week.
Next version will have better handling for corrupted databases due to improper export from the firewall.