Missing font dialogue crashes InDesign CC when opening documents

[DKingDesigner]

Subject says it all. InDesign crashes almost every time I open a document. When I reopen, it recovers all the open files (plus the one I opened), so I'm able to work, but I'm beginning to dread needing to open something. I started keeping track and noticed the trend. If the file has missing fonts, the Missing Font dialogue starts to come up, but doesn't populate. Then the report crash screen comes up and InDesign closes. Files that aren't missing fonts open without a hitch. I use NexusFont to manage most of my fonts and sync some through TypeKit. I just noticed that my Creative Cloud Manager is not staying logged in (I log in and a minute later, it logs me out), so maybe TypeKit is the problem? This is a recent problem. InDesign does crash a lot for me, but only recently (maybe just a few days) has it been crashing every time I open a document. It's beginning to get really frustrating. Anyone have any ideas how I can troubleshoot this?

I'm on Windows 10 with plenty of memory and drive space (along with a designated scratch disk). According to the Creative Cloud Manager, I'm up to date on InDesign CC.

[winterm]

Not at all solid solution, but may serve as some kind of workaround, or at least for testing purposes. Simple javascript to open indd document without bothering user about missing fonts, links, whatever...

var file = File.openDialog("Open InDesign document", "Documents:*.indd");
app.scriptPreferences.userInteractionLevel = UserInteractionLevels.NEVER_INTERACT;
var myDoc = app.open(file);
app.scriptPreferences.userInteractionLevel = UserInteractionLevels.INTERACT_WITH_ALL;

[DKingDesigner]

Thanks. It definitely works to skip the dialogue, and the file I tested it on opened without crashing ID. Now I need to figure out why the Missing Font dialogue causes a crash. I appreciate the work around.

[winterm · Accepted solution]

If I were in your shoes I would probably start looking in two directions, order may vary:

1. Application itself. Trashing prefs, clearing ID cache files, finally - reinstalling the app.

2. Fonts. Stop Nexus manager, Typekit (maybe even disconnect from the net for the moment), create brand new doc for testing, Document fonts folder next to it, and test it with tried-and-true locally installed fonts.

That said, narrow your search, and let's see. It's all just a shots in the dark now...

[DKingDesigner]

Resetting the preferences seems to have fixed it. I should have done that first, but I hate having to redo all my preferences.

[winterm]

So do I

I found a rule: if you take a bit of spare time to carefully customize your fresh preferences, then do a good backup of InDesign Defaults file, then even write a simple vbs script to quickly restore it from backup in case of corruption (as I did years ago), corruption stops and your precious script just sits unused

Anyway, glad you sorted it out.