Skip to main content
Participating Frequently
Sep 21, 2026 3:09 PM UTC
Question

Preflight reports "document contains an embedded file entry" on every PDF during PDF/A conversion (no visible attachment)

It keeps giving me the error message saying the document contains an embedded file entry. when the document does not contain an embedded file. It's doing this to every document I try to put through Preflight.

 

Preflight pdf/A-2b keeps giving me an error message that the document contains an embedded file entry. In the summary at the bottom it says there is no embedded file. Why is this happening all of a sudden to every document I try to put through preflight?

[Title renamed by Adobe moderator]

    34 replies

    Participating Frequently
    Sep 21, 2026 8:44 PM UTC

    The results panel shows no embedded file. 

    This is what I have Adobe Pro for Pharma / Windows the error appears when I run either one.

     Version: 26.2.21931.0
        Creation Date: 2026/09/15
        Creation Time: 9:09:44 PM
    c:\program files (x86)\adobe\acrobat dc\acrobat\plug_ins\autobookmark\autobookmark.api
        Version: 8.8.5.0
        Creation Date: 2026/07/01
        Creation Time: 9:58:24 AM
    c:\program files (x86)\adobe\acrobat dc\acrobat\plug_ins\csc\toolbox.api
        Version: 6.4.1.0
        Creation Date: 2022/08/31
        Creation Time: 5:11:50 PM
    C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\plug_ins\IA32.api
        Version: 26.2.21931.0
        Creation Date: 2026/09/15
        Creation Time: 9:09:44 PM
    C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\plug_ins\Updater.api
        Version: 26.2.21901.0
        Creation Date: 2026/09/10
        Creation Time: 1:31:08 PM
     

    Translate
    Anand Sri Bhattacharya
    Community Manager
    Community Manager
    Sep 22, 2026 1:43 PM UTC

    ​@Colorful_uniqueness3376 Thanks for the details.

     

    1. Test with the third-party plugins disabled (do this first). You have AutoBookmark (Evermap, autobookmark.api) and a CSC/toolbox.api plugin loaded. Plugins like these can add data/attachments or interact with the file in ways that leave an /EF entry, and it is quick to rule out:
    • Preferences (Ctrl+K) > General > Application Startup > tick "Use only certified plug-ins", then restart Acrobat and re-run the PDF/A Preflight.
    • Or, more thoroughly, rename the plugin folders so they do not load: C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\plug_ins\autobookmark and \csc (rename to autobookmark_off, etc.), then restart and retest.
      If the "embedded file entry" error stops with plugins disabled, one of them is the cause (or is adding the /EF entry when the PDF is produced/processed).

     

    Check the source workflow for an embedded .joboptions. If your PDFs are produced via Distiller or the Adobe PDF printer with "Save Adobe PDF Settings Inside PDF File" enabled, that embeds a hidden .joboptions file, an /EF entry, in every PDF, which never shows as a normal attachment but fails the PDF/A check. Turn it off in Distiller > Settings > Edit Adobe PDF Settings > Advanced, and re-create a test PDF.

     

    • Check your validated pharma Preflight profile. "Adobe Pro for Pharma" deployments usually run a customised/locked PDF/A profile for regulatory submissions. If the profile's "standards compliance for embedded files" options are misconfigured, it can flag every file. Since a validated config is often locked, this is worth checking with your internal Acrobat/validation admin rather than changing it yourself, especially in a GxP environment.
    • Strip it regardless: run a Preflight fixup to remove embedded files/attachments (it removes structural /EF entries even when nothing is visible), then re-run the PDF/A check.
    • If the embedded content is legitimate and required, target PDF/A-2 or PDF/A-3 instead of PDF/A-1, both allow embedded files (PDF/A-3 allows any file type), so the check will pass.
    • Because this is a validated/regulated deployment, disabling plugins, changing Distiller settings, or editing a locked Preflight profile may need to go through your internal Acrobat admin/validation team, and any change should be documented per your change-control. That is also the group that can tell you whether the profile or a plugin is the common factor across every PDF.

     

    Reference help articles: http://helpx.adobe.com/acrobat/desktop/protect-documents/redact-pdfs/redact.html

    https://helpx.adobe.com/acrobat/using/analyzing-documents-preflight-tool-acrobat.html

    https://helpx.adobe.com/acrobat/using/pdf-x-pdf-a-pdf.html

     

    Regards,

    Anand Sri.

    Translate
    Participant
    Oct 27, 2026 1:16 AM UTC

    This is a ridiculous amount of investigating a problem that is clearly within the Acrobat program.  I tested the preflight/pdf/A process with a file that had been pdf/A’d with no problem in February.  The pdf/A created in Feb. had no embedded file error when analyzed, when I ran the Word doc through pdf/A again, I get the error.  Users shouldn’t have to run all these tests for you to figure this out. 

    Translate
    Anand Sri Bhattacharya
    Community Manager
    Community Manager
    Sep 21, 2026 3:27 PM UTC

    Hello @Colorful_uniqueness3376


    I hope you are doing well, and thanks for reaching out. Sorry for the trouble you had.


    Could you please share more details about the issue?

    1. Which platform are you using: A) Windows or B) macOS?

    2. What exact Acrobat version/build is installed? Check from Meu > Help > About Adobe Acrobat.

    3. Is the error appearing when running A) a PDF/A-2b conversion/fixup or B) a PDF/A-2b compliance check/profile in Preflight?


    Please ensure you have the latest version of Acrobat installed on the machine: 26.002.21931, Out of cycle update, Sep 17, 2026. Check for any pending updates by navigating to Menu > Help> Check for Updates. Install the updates, restart the app and the machine, and try again.


    Rerun the built-in PDF/A-2b profile and note its exact name.
    Go to All tools > Use print production > Preflight. In Libraries, select PDF Standards, open Profiles, and run the relevant built-in PDF/A-2b profile. Adobe notes that Preflight errors are generated by the individual checks and property statements contained in the selected profile. Check these articles for more information: https://adobe.ly/3TgUA8n

    https://adobe.ly/4xvdk21


    In the Results panel, expand “document contains an embedded file entry.” If Acrobat lists a problem object, select it and use Show in Snap or double-click it. Adobe documents the Results list as profile-check mismatches, while the Overview is a separate display of document resources and general information; therefore, the two displays are not necessarily reporting the same condition. Reference article: https://adobe.ly/4hgxU0d


    In the Results panel, select Options > Create Report, choose a detailed report, and save it. This records the exact check and any problem object reported by Preflight. Reference article: https://adobe.ly/4dMxrBK


    I hope this helps, and please reach out if you need any help.


    Regards,

    Anand Sri.

    Translate