Did you go to the help page, download the script and run it as the instructions direct?
Yes. I've also manually nuked the InDesign Defaults and all the InDesign Recovery files. And, just for laughs, I tried an older version of dvaui.dll. I haven't done the tedious task of removing fonts and replacing them in small batches, but I'll try that tomorrow. This sucks.
You can try a reinstall, in case the .dll is actually damaged, but if that doesn't help, you probably need to call tech support (who probably can't help you, but it will get the problem in the pipeline).
I did the reinstall. First I deleted Batang, then uninstalled CC. Reinstalled CC, updated it, ran the Help Script on CC64 and CC32. Still crashes on quit. It's not a tech support issue. I'm going to take a stab at the fonts, then if it's still crashing on quit go back to CS6. Thanks for listening, BTW.
Anytime you get a repeatable crash scenario that can't be fixed by doing the ordinary steps (including trashing the prefs, if you haven't tried that -- see Replace Your Preferences) it should be reported because it means there's a programming problem of some sort. Windows is not, unfortunately, helpful with crash reports that would ease diagnosis. Your report would hopefully help other users in the future. If you don't want to call, please at least fill out the bug report form if more font troubleshooting, etc doesn't get you running: Adobe - Feature Request/Bug Report Form
Peter, I have trashed the prefs and recovery data more than once (#2 above). I've done it using CTRL-ALT-SHIFT-boot as well as manually as descibed in the link you reference.
I will report my issues to Adobe. I misunderstood your "tech support" reference in #3 above. I thought you were referring to the IT department where I work (City of Portland, Oregon).
Our IT dept. does a great job supporting over 6,000 employees, but their help on specific software bugs is limited. I don't want them to wipe my drive!
I would really like to know if other Windows 7/InDesign CC users are having problems, or if it's going just great for them.
Do you have any insight into general consensus?
I really appreciate your advice.
As far as I know the cleaner tool does work. It should remove any traces of the apps so you can reinstall fresh.
As far as how others are faring, it's a bit early to know. I think we may have seen one other report of crash on exit on Windows 7, but I also think a prefs change fixed it (I haven't done a search to confirm). There ARE plenty of reports of trouble that seem to be font related, and it might not hurt to temporarily move all the non-required fonts out of your Fonts folder temporarily and see if it stops crashing. Trying a new user would be a good diaganostic test, as well.
And I hear you about wiping the drive. Why is it that always seems to be IT's first reaction?
I'm embarrassed to report this, but I caused the problems I've been having myself.
In all the installs, reinstalls, fixes and scripts I've tried as I've upgraded to InD CC, there are 2 tweaks from previous versions that I felt I couldn't live without:
- Running InD with the empty text file "DisableAsyncExports.txt" at the root of the program to disable background printing and PDFing; and
- Equalizer.js by Marc Autret in the startup scripts folder.
I finally removed Equalizer and it seems to have resolved the crash on quit issue.
Thanks again to Peter Spier for support. Definitely a 4 star MVP.
Don't see where I actually provided much help here. I will say that removing any third party items is always one of the first trouble-shooting steps to try.
And I'm pretty sure Marc would like to hear from you about this...
I'll be sure to let him know. and moral support and actually having discourse with a human on the forums was very helpful.