Skip to main content
Participant
August 4, 2026
Answered

Component Files opened from a Portfolio show as blank when opened. Closing and reopening the same file shows the document properly.

  • August 4, 2026
  • 20 replies
  • 422 views

Some users in our enterprise are experiencing an issue when working with PDF Portfolios. When attempting to open a component file (PDF) from the portfolio, the new tab with the file is blank. Closing the tab and reopening the same file will correctly show the file on the second attempt.

 

This behavior is occurring on version 2026.001.21771 of Continuous Release. This is affecting only a handful of users. We have attempted some of the usual Preferences tricks like disabling Enhanced Security and Protected mode, but they don’t seem to do anything.

    Correct answer bastionh84226254

    This fixed it for me.

    Adjust Tab Settings: Go to Preferences > General and deselect Open documents as new tabs in the same window if component files show up blank.

    Problem is, you have to open the file (component file) in the portfolio you want to edit/sign, make the edit, then minimize the component file and go back to the portfolio fie (you’ll see the edit you made), and Save the portfolio file. If try to hit Save the edited component file, Acrobat throws a critical error.

    Hope this helps.

    20 replies

    Participating Frequently
    August 20, 2026

    I have the same problem with all pdf portfolios. Changing the tab setting to Open Documents as new tabs in the same window resolves the problem (thank you to the user who posted this temporary fix!). I open files within portfolios daily so I look forward to a fix so the General tab setting can be returned to opening new tabs in same window.

    1.    MacBook Tahoe 26.5.2
    2.    Acrobat Last numbered update was 26.001.21662 on 6/13/26. Updates on 6/30, 7/23, 8/3, 8/12 do not display a version number. However, About Acrobat shows 2026.001.21789.
    3.    This happens with all pdf portfolios and started earlier this month. Not sure if after 8/3 or 8/12 updates.

    Thank you to everyone posting this problem and the Adobe staff working on it.
     

    Community Manager
    August 20, 2026

    Hi ​@Nor_1234,

    thanks for flagging this and for sharing all those details, it really helped us look into it. I completely understand how frustrating this must be, and I appreciate your patience. We've identified the issue and are actively working on a fix as a priority. As soon as we have an update we can share publicly, we'll post it right here to keep you posted.

    Thank you for bearing with us.

    ^AV

    bastionh84226254Correct answer
    Participant
    August 18, 2026

    This fixed it for me.

    Adjust Tab Settings: Go to Preferences > General and deselect Open documents as new tabs in the same window if component files show up blank.

    Problem is, you have to open the file (component file) in the portfolio you want to edit/sign, make the edit, then minimize the component file and go back to the portfolio fie (you’ll see the edit you made), and Save the portfolio file. If try to hit Save the edited component file, Acrobat throws a critical error.

    Hope this helps.

    Community Manager
    August 19, 2026

    @bastionh84226254 - thanks for sharing the workaround here. 

    Participant
    August 19, 2026

    Hope it helps someone while Adobe investigates and can truly fix the issue. Like my last paragraph says, you have to jump through hoops to save the edits when you should be able to open the component file, edit, and save within the portfolio file without having to adjust default preferences or do some funky save routine.

    Participating Frequently
    August 6, 2026

    We are facing the same issue. not able to open the component files within the portfolio.  

    Community Manager
    August 6, 2026

    Hi ​@Imaginative_Flamingoc8d9,

    Sorry for the trouble here. Thanks for flagging that you're seeing this too.

    What you're describing, component files not opening properly within a Portfolio, points to something in how Acrobat loads component files inside a Portfolio on this build. We're flagging this internally for investigation, and to help us reproduce it exactly, it would help to have a few details from you:

    • The OS and version on the affected machines

    • Whether the affected users differ in any hardware from those who aren't seeing it, for example GPU model or display setup

    • Whether the Portfolio file sits on a local drive or a network drive

    • Whether it happens with every Portfolio or only certain ones

    • A short screen recording showing the behavior when you open a component file

    • Acrobat diagnostic logs from one of the affected machines, which you can pull by following the steps here: https://adobe.ly/4xgFOgq

    It would also help to know your exact Acrobat version, and whether this started after a recent update or was happening on an earlier build too.

    Looking forward to those details, and we'll take it from there.
     

    Thanks,
    ^AV

    Participating Frequently
    August 6, 2026

    Windows 11 pro- OS build- 26200.8973, version 25H2, Precision tower 3430

    different hardware for different users.

    portfolio files are on network drive as well as local drive

    every portfolio

    adobe version: 2026.001-21771 (updated today on my computer)

     

    Community Manager
    August 5, 2026

    Hi ​@Omar23724908sa0e


    Sorry for the troubled experience. 

    Thank you for the detailed write-up and for documenting the version, affected users, and workarounds already attempted. That level of detail is exactly what helps us investigate effectively.

    The behavior you are describing, where a component file opens blank on the first attempt but renders correctly on the second, suggests a rendering or initialization issue specific to how Acrobat loads component files within a Portfolio on this build. Since Enhanced Security and Protected Mode have already been ruled out, this points to something lower level in the rendering stack for this version.

    We are flagging this internally for investigation. To help us reproduce the senario exactly our engineering team would require the following details:

    • Operating system and version on the affected machines
    • Whether the affected users have any specific hardware differences from users who are not experiencing this, for example GPU model or display configuration
    • Whether the Portfolio file is stored on a local drive or a network drive
    • Whether this occurs with all Portfolio files or specific ones
    • A short screen recording showing the blank tab behavior and the successful second attempt
    • Acrobat diagnostic logs from one of the affected machines, which you can collect by following the steps at: https://helpx.adobe.com/acrobat/kb/acrobat-diagnostics.html 

    Please also confirm whether this started after updating to 26.001.21771 specifically or was present on an earlier build as well.

    Will be waiting for the requested details. 

    ~Tariq 

     
     

    Participant
    August 5, 2026

    Responses to the details request in order:

    • OS and version on affected machines is Windows 11 23H2
    • No major hardware differences between users, one has a Dell Precision 3260, another has a Dell Precision 3280, neither had a dedicated GPU, both using intel grpahics
    • Issue occurs with portfolio files on both local drives and network shares
    • Not all portfolio files or even component files are affected by this issue, hard to determine what exactly causes the rendering issue, but it seems to happen with PDFs that have images or graphics rather than simple text
    • I was unable to replicate the behavior with non-confidential documents/files, so I can’t upload a screen recording at this time, I will see if the affected users can find a way to replicate the issue with non-confidential info so we can record and upload it safely 
    • Acrobat log dump attached

    This issue reportedly started for these users in the last couple days, which lines up with the 26.001.21771 release.  

    Community Manager
    August 5, 2026

    Hi ​@Omar23724908sa0e,

    Thank you for turning this around so quickly and so thoroughly. Having the OS, the hardware details, the local-versus-network confirmation, the pattern around graphics-heavy PDFs, and the diagnostic logs all in one place gives us a solid package to work from.

    We've received your answers and the attached logs. The detail that it tends to affect PDFs with images or graphics rather than plain-text component files, along with the timing lining up with the recent update, is useful context to have on record. We'll follow up here as we have more to share.
     

    Thanks,
    ^AV