Skip to main content
New Participant
August 13, 2024
Question

Error in Microsoft Office after deployment of newest Adobe Reader update

  • August 13, 2024
  • 5 replies
  • 4849 views

After deploying the newest version of Adobe Reader 2024.002.21005, we get an error message in Microsoft Word, Excel and PowerPoint:
"Custom UI Runtime Error in PDFMaker.OfficeAddin -
The call to GetCustomUI() for RibbonID "Microsoft.Word.Document" failed".
The error messages for Excel and PowerPoint are nearly the same, except for the "Microsoft.*" suffix.

In the COM Add-Ins lists in all of the three Microsoft applications, there is a new entry "PDFMaker.OfficeAddin", which is active.
When deactivated, the error disappears.

Office Version: Microsoft Word for Microsoft 365 MSO (Version 2407 Build 16.0.17830.20166) 64-bit.



This topic has been closed for replies.

5 replies

New Participant
August 26, 2024

I have a user who stated they don't have the Adobe Add-in enabled and still got this pop-up error.

New Participant
August 26, 2024

Same problem here with Adobe Reader 2024.002.21005 after an automatic update last Friday.

Annoying behaviour and obviously failed testing processes.

New Participant
August 26, 2024

Occurs just at the start of Word, Excel, Powerpoint ...

JR Boulay
Community Expert
August 18, 2024

[MOVED TO THE ACROBAT READER DISCUSSIONS]

Acrobate du PDF, InDesigner et Photoshopographe
New Participant
August 16, 2024

I am experiencing the same issue after updating the adobe application and it is greatly affecting work processes. Please advise when this issue will be resolved. 

Adobe Employee
August 13, 2024

Hi,

Thanks for reporting the issue. We are investigating it on priority.

Could you please provide the following information to help debug this further.

1. Are you deploying fresh Acrobat Reader or applying patch on an existing install.

2. You are getting the error on launching the Word application or while performaing some operation.

 

Participating Frequently
August 18, 2024

This is very annoying, and I'm curious what "investigating it on priority" really means.

 

You've published no officical statement, let alone releasing any kind of a patch. I'm guessing "priority" means "whenever we get around to it".

 

Is the "real" solution is to uninstall reader?

New Participant
August 19, 2024

Hi @38059776, for us, deactivating "PDFMaker.OfficeAddin" in the COM Add-Ins lists solved the problem.
But this is more of a workaround, rather than a solution to the underlying problem.