Skip to main content
Participant
October 8, 2026
Question

Starting Oct 6, 2026 Acrobat reader version 26.2.21996 is prompting for a login everytime a pdf is opened.

The staff have not experienced this before and it is only 1 person that has notified us about it. Reinstalling the app did not fix the issue. It is very convenient that it started Oct 6th when the debug files started appearing for the entire company as well.

Has anyone had this? is it related to the latest patch?

    5 replies

    Participant
    October 15, 2026

    I have the same problem
    1. Windows 11 Edu 26100.9457
    2. Standard Adobe ID login prompt
    3. Other users does not have the same problem on the laptop. 

    Translate
    Amal Jaiswal
    Community Manager
    Community Manager
    October 15, 2026

    Hi @efficient_solution928f,

    Hope you’re doing well, and thank you for sharing the requested details.

    Could you please confirm whether this issue started recently, or if you’ve been experiencing it for some time?

    In the meantime, please try the troubleshooting steps outlined in this Adobe Help article: Troubleshoot Acrobat sign-in errors. Please go through the suggested steps and check if they help resolve the issue.

    Also, a new version of Adobe Acrobat, 26.002.22031 (Planned Update, October 14, 2026), is now available. Please update Acrobat by going to Help > Check for updates. Once the update is complete, restart your computer and check if the issue persists.

    Let us know how it goes. If the issue continues, please share what happens after trying the above steps, and we’ll be happy to assist further.

    Regards,
    Amal

    Translate
    Participant
    October 12, 2026

    I have just encountered this issue. After auto updating to 26.2.21996, users receive a sign-in prompt when opening Adobe Reader. Closing the sign-in prompt with the X cause Adobe Reader to close, so users are stuck. We do not have Adobe accounts and never have.

    The environment is a remote desktop environment (Azure Virtual Desktop). The session hosts are Windows 11 Enterprise multi-session edition.

    We have temporarily downgraded to the previous version and set the bUpdater preference to 0, which will hopefully disable auto updates until we have a fix.

    What I think may have happened is that the install somehow switched from Reader to the paid version of Acrobat. It then needs the user to sign in to do a license check. This is just a theory though. We are using the x64 version of Reader, which I believe (unlike x86) uses the combined Acrobat installer (i.e. one installer for Reader, Standard and Pro).

    Translate
    Amal Jaiswal
    Community Manager
    Community Manager
    October 13, 2026

    ​Hi @defaultcmt5ixn4xltl 

    Hope you are doing well and thanks for reaching out and sharing the details.

    Would you mind also sharing:

    • What the sign-in prompt looks like and what it asks for, such as an Adobe ID, an organization or single sign-on login (a screenshot without personal information works well).

    • Whether the same user sees the prompt on another computer, and whether another user signing in on the affected computer sees it too.

    • Also a small video recording of the steps you are taking and the issue as it occurs would be very helpful for further investigation.

    Regards

    Amal

    Translate
    Amal Jaiswal
    Community Manager
    Community Manager
    October 8, 2026

    Hi @Melodic_Beeccbf

    I hope you are doing well, and thanks for the clear description. I’m sorry for the trouble, I understand how disruptive a sign-in prompt on every PDF can be for your user, especially alongside the debug files you are seeing across the company.

    Since only one user is affected while others on the same version are not, a few details will help us look into the difference:

    1. The operating system of the affected computer, and how Reader is installed (individually or deployed by your IT team with policies).

    2. What the sign-in prompt looks like and what it asks for, such as an Adobe ID, an organization or single sign-on login (a screenshot without personal information works well).

    3. Whether the same user sees the prompt on another computer, and whether another user signing in on the affected computer sees it too.

    4. The file names and folder location of the debug files, and whether they also appear on the affected computer.

    Once we have these details, we can share the next steps with you.

    Let us know how it goes.

    Regards,
    Amal

    Translate