Skip to main content
Participant
July 24, 2025
Question

Print producion tools function not working in latest Windows 11 update

  • July 24, 2025
  • 1 reply
  • 469 views

Hello, 
I am writing to report a problem I recently encountered with Acrobat on Windows 11.
Since the latest Windows 11 updates, Print production tools has not been working.
I think I have found the source of the problem; at least I have solved it for myself, so while waiting for a potential patch, this may help others.
For me, it was related to access rights to the Config.Msi folder, which contains the RBF files used by Acrobat. Windows was preventing access to this folder. I simply restored administrator rights to this folder and now it works again.
I think the Windows update is trying to better protect users, but it conflicts with Acrobat when you try to switch to Print Production Tools mode.
Is this a problem that will be patched?
Thanks

1 reply

Meenakshi_Negi
Legend
July 24, 2025

Hi Roman2725717259m8,

 

Thank you for reaching out and sharing the information.

We have not heard about this issue from other users yet. Please share more information on what happens when you try to use the print production tool. Did you receive an error message, or did it just not open the options? What version of the application is currently being used? We will check if we can replicate this behavior.

 

Thank you for sharing the steps that helped you restore the function. They might help others who have experienced the same behavior. 

 

Thanks,

Meenakshi

 

 

 

Participant
July 24, 2025

When I tried to access the tool, the left panel opened but remained gray.

I don't remember the error message, but I could choose “Cancel,” “Repair,” or “Don't show again.”
After trying to repair it, I got this message:
“Unable to set security for file D:\Config.Msi\6b3bd3.rbf. Error: 5
Make sure you have sufficient privileges to modify permissions on this file.”

My version is the latest update from Creative Cloud: 25.1

I am available if you need any further information. Perhaps this problem is not widespread but only related to my configuration... but just in case, I thought it might help some people 🙂