"Save as Adobe PDF" from MS Office/365 apps fails occasionally
Windows 11 Enterprise Build 22621.1848
Microsoft® PowerPoint® for Microsoft 365 MSO (Version 2304 Build 16.0.16327.20324) 64-bit
Adoba Acrobat Pro Version 2023.003.20215 64-bit
Trying to create a PDF file from MS Office document (usually Powerpoint, but also in Word, Excel) using "Save as Adobe PDF", I often get a dialog titled "Adobe PDFMaker" with the message "Adobe PDFMaker needs to save the file before continuing. Do you want PDFMaker to save the file and continue?"
If the file is indeed not saved, then clicking "Yes" saves the file and proceeds to select the PDF file name and location.
However, this often happens even if I did save the file right before going to "Save as Adobe PDF", and in these cases, clicking "Yes" just closes the dialog without generating a PDF. When that happens, it persists no matter how many times I save the document.
For a long time, the only resort I had was to close the file and re-open it, and then a PDF can be generated with no message. It's an annoying workaround.
I recently found both a way to reproduce this problem, and some nicer workarounds.
If I change the file properties from within the PowerPoint (File->Info->Properties, change anything in the dialog) then any subsequent attempt to generate a PDF will result in this behavior. It may not be the only reason, but it repeatedly creates the problem, and I often set the document properties right before creating a PDF.
As for workarounds: I found that there are several ways to generate a PDF from Office:
- Using "Save as Adobe PDF" as I usually do (which generates a PDF with the PDF Producer property to "Adobe PDF Library 23.3.247") - is prone to the issue described.
- Using "Print" and choosing to "Adobe PDF" (which sets the PDF Producer property to "Acrobat Distiller") does not have this issue, but unlike PDFMaker, it does not preseeve the file properties from PowerPoint.
- Using "Save a copy" and choosing "PDF" from the file type drop-down creates a PDF using PowerPoint's internal generator (PDF Producer set to "Microsor® PowerPoint® for Mircosoft 365") without the issue above. It preserves the file properties (and even lets me edit them in the File Save dialog). Oddly, after using this method, the problem disappears and I can use "Save as Adobe PDF" again. I am going to switch to this method, although it is somewhat less natural.
I don't know if there are any benefits for using the Adobe PDFMaker method over the Microsoft "Save As" method, but the former is the more accessible method, so likely the default for most people, and this issue may be a hassle for others too. So please either fix it or remove it...

