I had reported about this problem at 22 September 2011 ( http://intrepid.danplanet.com/pipermail/chirp_users/2011-September/001406.ht... ) and Dan has opened the issue - http://chirp.danplanet.com/issues/12 . But it has been closed later.
No, you reported debug.log, which is no longer stored in Program Files as of some daily version months ago.
He's asking about chirpw.exe.log, which is something that the Py2Exe environment creates by itself and I have no control over, as far as I know. I don't believe it gets created unless there's an error that needs to be logged there.
If you are using Windows Vista or Windows Seven, you always should run the program as administrator - right click on the Chirp's shortcut and select "Run as administrator". Or you can change the directory permissions on 'C:\Program Files (x86)\CHIRP' or reinstall the program to another (non Program Files) directory.
Ron, if you could try this and then see if a chirpw.exe.log file gets created, that would be helpful. The contents of this log may help me determine what's causing it to be created in the first place.