Skip to main content
Participating Frequently
May 13, 2025
Answered

Distiller error after

  • May 13, 2025
  • 14 replies
  • 15395 views

I have several users getting an access denied Distiller error after updating Acrobat DC to version 25.001.20458.

 

The error pops up randomly even when Acrobat is not in use. I have tried removing DC, running the cleanup tool and reinstalling DC. I also apllied the latest optional update 25.001.20474.

I have cleared all temp folders and granted users full control over all Adobe folders, c:\windows \temp and c:\temp.

 

I also tried turning UAC from off to on but the error still comes up intermittently. Has anyone else has this issue?

 

 

 

 

 

 

Correct answer S_S

Hello everyone,

 

We are live with a new update (25.1.20xx), which has a fix for the issue.

 

Please update the app and let us know if the issue is fixed for you.

More info here: https://adobe.ly/3V38zfs

 

Let us know how it goes.


Regards,
Souvik.

14 replies

Participating Frequently
May 21, 2025

I have a handful of users getting this error randomly appearing as well.

Meenakshi Negi
Community Manager
Community Manager
May 21, 2025

Hi defaultjrhx2dc50p54,

 

Thank you for reaching out, and sorry about the trouble.

 

We will check with the support team about the latest information on this and update you. 

We appreciate your patience.

 

Thanks,

Meenakshi

 

Participant
May 21, 2025

Also have a number of users reporting this

Participant
May 19, 2025

We are also having this issue. Have you figured out a solution?

Participating Frequently
May 19, 2025

I tried a few things from all the posts I could find on the error. My machine never had the error. I noticed in the %Temp% folder, my Acrobat Distiller folder was named "Acrobat Distiller DC". On the 2 problem machines, the folder either didn't exist or was named something different. We use the same Adobe Acrobat Pro version at the office, so our setups should be identical, I would think. I uninstalled Adobe, deleted the contents of the %temp% folder. Then created a folder and named it "Acrobat Distiller DC" and reinstalled Adobe. So far, the users haven't had the issue reappear.

MW_MWAuthor
Participating Frequently
May 19, 2025

I have more than a dozen users and it seems new reports are coming in daily so manually going through all those steps for every person with the error would be quite time consuming.

Participating Frequently
May 15, 2025

@MW_MW Did you happen to find a fix? This error has started popping up for some of my users now as well. 

MW_MWAuthor
Participating Frequently
May 15, 2025

I have not. I have a case open with Adobe. However, all they did was grant full control to the c:\windows\temp folder for all users. I told them I had done that on a differnt computer with the issue and it did not resolve the problem. I have updated the ticket and I am not getting any response. The problem is growing in my environment. I am getting reports of it daily now. 

Participant
June 3, 2025

Have you found a fix for this yet? We are seeing this in our environment now.

creative explorer
Community Expert
Community Expert
May 13, 2025

@MW_MW I don't have that issue, but, a workaround you could explore involves manually specifying a different temporary folder location within Acrobat's preferences. To do this, open Acrobat, go to Edit > Preferences, then select "Convert to PDF." Under "Adobe PDF Settings," click "Edit." In the "General" tab, examine the "Temporary files directory." Try changing this to a specific folder on the user's local drive where they have full read/write permissions, perhaps even creating a new folder specifically for this purpose (e.g., C:\AdobeTemp). While this might not address the underlying cause of why Acrobat is losing track of the default temporary folder, it could potentially provide a more stable location and prevent the "Access Denied" error from popping up intermittently. Once you change the 'Preferences' always make sure to restart the app for good measure. 

Or if you can, or could roll back to the previous version that had no issue if the above doesn't work. 

m
Participant
May 29, 2025

Did this work ?

 

MW_MWAuthor
Participating Frequently
May 30, 2025

No, it did not.