Skip to main content
Ronald59
Ronald59
Participating Frequently
April 7, 2015
Answered

distiller stopped working

  • April 7, 2015
  • 11 replies
  • 36753 views

uptaded (through CC) to Acrobat DC. Now  I keep getting a messing arbitrarily popping up "Distiller has stopped working..."

I've tried uninstalling and reinstalling.

This topic has been closed for replies.
Correct answer AshuMittal9644438

Hi Ronald59‌, all,

The Distiller crash issue has been fixed in the DC update that was released on 14th July (Release Notes). Please update to latest patch by going to Help > Check for Updates.


Thanks,

-ashu

11 replies

richardp81686504
richardp81686504
Participant
July 14, 2016

I'm seeing the same issue on 6 computers after removing Adobe Acrobat X Standard and installing Adobe Acrobat DC Standard.  Have two tickets open with customer service.  No solution since 7/11/2016.

S
Sammi_M
Participant
February 15, 2017

I've been experiencing this same issue for the past two months. I finally came up with the solution.This is what worked for me:

  1. Open Distiller. As soon as Distiller opens, it begins to scan fonts in alphabetical order.
  2. When Distiller crashes, note the font that was last scanned.
  3. Go to your Windows > Fonts folder and delete the font that follows the previously scanned font.

Hope this helps you.

R
richs56494968
Participant
March 17, 2017

Hard to believe this is still an issue. I deleted a few fonts but finally got it. Distiller works again. Thanks Adobe for the fix--NOT!

Thank you all for finding the solution!!!

jens_ra
jens_ra
Participant
September 29, 2015

Hello all,

similar problem here, Distiller DC keeps crashing on Mac OS 10.10.x during startup (splash screen shows up, PostScript is being started -> crash). Following error message:

Creative Cloud and Acrobat say I'd be running the latest version.

Any news on the topic?

AshuMittal9644438
Adobe Employee
AshuMittal9644438Correct answer
Adobe Employee
July 20, 2015

Hi Ronald59‌, all,

The Distiller crash issue has been fixed in the DC update that was released on 14th July (Release Notes). Please update to latest patch by going to Help > Check for Updates.


Thanks,

-ashu

Ani_walltopia
Ani_walltopia
Participant
August 4, 2015

Unfortunatelly, after latest update from the CC App yesterday, I still get the error message at random times, no matter whether DC's working or not. Here's a few printscreens. Any suggestions?

AbhigyanModi
AbhigyanModi
Participating Frequently
August 4, 2015

You don't have the latest update. As Ashu suggested above, open Acrobat, help->check for updates.

D
djwernars
Participant
July 2, 2015

I have had this issue resolved by Adobe Technical Support:

My Issues

1.Distiller would crash when it stopped on Lucida Console Font. Since this is a Windows system font, you cannot delete it.

2. Every time I attempted to print to PDF, it would hang and I would get " Not Responding"

Solution as per Adobe Technical Engineer

1. Go to Fonts Folder in Windows Control Panel.

2. Change your view to Details

3. Click on the Designer/Foundry heading

4. Select all of the fonts where the Designer/Foundry is blank and save to a folder on your desktop

5. Now go to C:\Windows\Fonts and delete all the fonts that have a blank Designer/Foundry

6. Run Distiller

Now to test which fonts cause distiller to crash, add the fonts back one by one and run distiller after each one.

Since I removed 710 fonts, I do not know which font has caused this yet and told them that I would test this over a period of time.

I am guessing that that it is probably one of the free fonts and not Lucida Console.

Marta B.
Marta B.
Participant
June 29, 2015

I had the same problem after the last update to Acrobat DC. I agree that some fonts cause the problem. Look at the Distiller window in the moment of hang up - there is a list of scanned fonts below in alphabetical order. The next font after the last one listed cause the problem. Uninstall it. After that my Distiller works correctly. In my case it was only one font - marmelatta, demo version.

DezmoMedia
DezmoMedia
Participant
June 17, 2015

For what it's worth, I spent the last two hours uninstalling fonts, only to find the issue was some old web design software (WYSIWYG 8.0) that was listed in Distiller as a Watched folder. Once I uninstalled this software, the problem went away. I also cleared out my font cache, which for my Windows 7 Professional, is in C:/Windows/System32/FNTCACHE.DAT. If you delete this file and reboot, it clears out your font cache. I did this before uninstalling WYSIWYG 8.0, so it may be unrelated to this problem. At any rate, the Distiller error has gone away. 

Juan C Walls
Juan C Walls
Participating Frequently
May 28, 2015

Same issue here every single day since I applied the update from previous Acrobat (maybe XI?) to Acrobat DC.

Probably also because of the problem with fonts. I have tons of fonts and no time to check them one by one.

It crashes randomly shortly after start-up. Apparently it has nothing to do with what I am doing at that moment.

Sachin Soni
Adobe Employee
Sachin Soni
Adobe Employee
April 29, 2015

Hi,

First of all, extremely sorry for the inconvenience caused :-(

We are able to reproduce the issue in-house. The problem happens when Distiller tries to load a font that has some delimiter (like '(', ')', '{', '}') in the font name. While we are working on a fix for the same, meanwhile, as a workaround, fonts with such delimiters can be removed from the locations where Distiller looks for Fonts. Following are such locations:

C:\Windows\Fonts

C:\Program Files(x86)\Adobe\Acrobat DC\Resources\Font\

C:\Program Files(x86)\Common Files\Microsoft Shared\EQUATION\

C:\Program Files(x86)\Common Files\Adobe\Fonts

Thanks & Regards

Sachin Soni

    T
    Thrill Media
    Inspiring
    April 29, 2015

    Thanks for the update. I did remove Blox and haven't had the issue since. Don't think I have EVER used that font.

    judyr23717440
    judyr23717440
    Participant
    April 28, 2015

    I too have the same problem. I can't be wasting time going through every font on my system to see which one(s) distiller all of a sudden doesn't like.

    D
    dkirkhus
    Participating Frequently
    April 14, 2015

    OK, after temporarily disabling the HD that contains my client projects (and all of their respective fonts) I was able to open Distiller without it crashing. I then changed font settings in Distiller so that it only looks in the default Windows and Adobe paths.

    All seems to be functioning properly, now. I managed to print to Adobe PDF with no issues.

    Thanks, adrianad16709978.

    K
    kateyb98376864
    Participating Frequently
    April 14, 2015

    I think I may have fixed my problem...  I am no longer seeing the Distiller stopped working pop up and I am now able to print to PDF

    Win 7 Ultimate 64 bit

    My Fonts and program are all installed on the same drive  thus preventing me from gaining access to Distiller to change the settings. Windows would not let me make any changes to the Default Font folder.

    This is what I did...

    Not knowing which font(s) where causing the problem, I moved all but protected fonts (automatically labelled) from the Window's Font folder and placed them in a temporary folder.

    I restarted Distiller DC and great news...the program did not crash and I was able to change the settings to temporarily not include the Windows Fonts .No more pop ups and I can now print to PDF!

    What I am going to do..

    Through the process of elimination, I will gradually restore the fonts I removed from from the Window's folder to find the culprits(s)

    Once I am satisfied that the problem Font(s) are found and no longer  included in the Window's Font folder, I will change the settings in Distiller back (permanently) to include the Window's Font folder.

    In closing, and because so many others are having the same issues, I really do think it would be prudent for Adobe to make the necessary adjustments to their program(s) to prevent this kind of issue.

    Thanks

    Kathy

    V
    Adobe Employee
    Vishal@PDF
    Adobe Employee
    April 22, 2015

    Hi Kathy,

    This issue is already reported to Acrobat Engineering and they are investigating it. So far they have found that some fonts (copyright by sRB-Powers) like "sarusFlowerDing(sRB).TTF" / com_srb_.TTF / similar are causing the crash. Can you please check if you are also having any such font installed in your system which you have moved now to temp folder?

    Thanks,

    Vishal

      Show more replies
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices