Interestingly, InDesign running with the new DLL doesn't have the option "Show 'Start' Workspacen When No Documents Are Open" anymore - it's completely gone, so this might indeed indicate problems with the "Start" Workspace. Support has replaced this DLL file with a recent version, because the crash report signaled problems with this DLL. Sounds risky to me, but this was the first thing adjusted by the support via remote control.
It seems as if Adobe needs full access to its Program, Program (x86) and ProgramData folders for "EVERYONE". I've installed Adobe CC with a real Administrator account (not the pseudo-admin account Win10 creates at first start) and been using it with non-admin accounts with no further security permission changes. I was not aware of this as a potential problem because I'm running a standard Win10 with unaltered standard permission settings. Wrong permission settings for Adobe folders
InDesign finally could be recovered for a problematic Windows user account with which InDesign was always crashing on start-up, and it turned out that the problem was related to two things.ġ. I had a one hour chat with Adobe's support this morning. Just getting back to this thread with good news: Let us know which of these steps fix the issue for you. Then Delete the fonts from C:\Windows\Fonts.Copy-Paste all the fonts on new new folder on Desktop.Please try validating system fonts ( ) and remove the corrupt fonts and then try to launch InDesign.If that does' help either, we need to check for corrupt fonts. If it successfully opens in Safe Mode, go to Preferences, and disable the preference "Show Home screen when no documents are open"Ĥ. For Windows Machine, check for E vent Viewer logs. Go to Windows Start menu > Open Event Viewer > Windows Logs > Application > Look for recent error related to InDesign.įew users have confirm that the issue has resolved by disabling home screen from InDesign Preferences.ģ.This will help us find the logs at our end.) Crash Report: (Please submit crash report with same email address with which you are logged in on this community.I would request if you can share a few more details like: And when you visit a Web page that uses them, it is nice to see the page as it is meant to, even if you can't read it, instead of a bunch of garbage characters.Sorry to hear about this issue. These don't take up much space at all, and won't slow anything down. I believe this will take the appropriate fonts with it. You can also edit this list and remove them.
So just keep that application running in the background instead of quitting and launching all the time.Īs for foreign language fonts, if you go to System Preferences, Language & Text, Languages you can see a list of which languages your Mac supports. If an application takes a long time to launch, there are other reasons too. But that isn't something you'd want to worry about too much. Sometimes applications create a font menu on startup - a graphic list of all fonts to make it easy to select a font. Better font handling in OS X and faster processors are a thing of the past. In general, the slowness caused by having lots of fonts is a thing of the past. If you get rid of one, then that application may not work right anymore. Some of these may not even appear in Font Book as they are core fonts, so not "manageable." They have to be there.īut in addition, you need to watch out for fonts that are installed by applications. These are used by all sorts of applications. In addition, don't get rid of AppleGothic, Menlo, Helvetica, AquaKana, Times, Times New Roman, Comic Sans, Georgia, Trebuchet MS, Arial, Arial Black and Verdana. Font Book is smart enough to not let you remove critical fonts: Keyboard, LastResort, Monaco, Geneva and LucidaGrande.