Inspiring

Answered

Error 83 § 4, font dictionary. no solutions

Forum|Forum|8 years ago
September 22, 2017
5 replies
10620 views

Since either the last windows or after effects update (I did them in quick succession) after effects repeatedly crashes in progress or on start, prompting (before crashing) "After Effects warning: The font dictionary can't be read [...] (83 § 4)".

Premiere does not crash, but warns about a set of invalid fonts.

No other application mentions or has any problems with those fonts.

I used all of those fonts for YEARS without problems. If I deactivate the affected ones, everything works fine, but this is just not an option.

I cleared all the AdobeFnt.lst files. This works only temporary. I reinstalled After Effects and the Monotype Fontexplorer Pro. I reinstalled the fonts. The error returns.

AE completely crashes, even takes windows with it at times.

After clearing the AdobeFnt.Lst files and emptying the font cache, it works for a time (even with the mentioned fonts activated), then it complains and crashes again.

AE Version is 14.2.1.34

Windows Version is Win 10 Pro (all updates installed)

It's a i7-6800k Intel PC with 48 GB Ram and a GTX 970. All drivers are up to date.

Any ideas?

This topic has been closed for replies.

Correct answer mapleandjamprod

Looks like they are now in C:\Users\**YOUR NAME**\AppData\Local\Temp\Adobe\Premiere Pro\12.0\Typesupport

You now have to go to that Adobe file and click in each of the folders

Ocelot66

New Participant

Worked for me, after combing through font files on my C: , using downloaded font management utilities for 5 hours, found this thread, tried it. It was the adobe font datbases.

Action taken: Deleting

AdobeFnt_CMaps.lst
AdobeFnt_OSFonts.lst

From C:\Users\**YOUR NAME**\AppData\Local\Temp\Adobe\After Effects\17.7\Typesupport

And then Starting AE solved it instantly, I can open my short film project now.

CorySouthpaw

Participating Frequently

Thank you @Ocelot66! I'm obviously running an older version of AE and was trying to continue working on a project but kept getting Font dictionary error 83 :: 4. Very frustrating! Doing a restart did not work, and the locations that Adobe listed did not exist. But your solution worked! I deleted the same 2 files you mentioned and upon opening the same project the errors were gone. No restart required... Much appreciated!

M

mapleandjamprodCorrect answer

New Participant

Looks like they are now in C:\Users\**YOUR NAME**\AppData\Local\Temp\Adobe\Premiere Pro\12.0\Typesupport

You now have to go to that Adobe file and click in each of the folders

The Viking DP

Participating Frequently

This fixed it.

W

weidAuthor

Inspiring

The issue seems to have been solved with one of the latest updates. Thanks for that!

marcusr10618703

New Participant

Hi,

I received, “The font dictionary can’t be read” error in after effects – 83: :4 – for the last 2 weeks

I am at the end of my wits about this error. I have tried everything, even restoring my system from a month back using windows restore procedure. Of course that did not work. I even removed all of my fonts that didn’t come with Windows.

I am asking for help because I have a project in 2 weeks. I have Adobe CS 5.5 suite. I was so desperate that I uninstalled the full suite and reinstalled it.

I follow the instructions from "The font dictionary can't be read" error in After Effects

To the fullest and I have not had any luck. I don’t know what to do and I’m so frustrated that there’s no tech support (Phone calls) on adobe for the suite that I paid big $$$ for.

If anyone can help me. I would even pay you. I have searched high and low. Youtube and beyond. I’m almost at the point of reinstalling Windows 10 to make it happen.

I get the same Error. The splash screen doesn’t get passed the “initializing mediacore” prompt.

Help, help, help!

nasg85

New Participant

@

marcusr10618703

Delete the all .Ist files in your users folder:

C:\Users\**yourname***\AppData\Local\Adobe\TypeSupport

Deleting them in the program files folders does fAll.

I've had the same problem after a windows update on cs6.

Also, google "take ownership menu hacks". Its a right click menu .reg file. It adds the option to "take ownership" of any system files that might block you from deleting. Handy in general when troubleshooting stuff like this...

Hope this helps