Fix Acrobat Reader DC Opening as Acrobat Pro DC on a Terminal Server
Question details
Determine why Acrobat Reader DC appears or launches as Acrobat Pro DC on a terminal server and restore PDF access for users.

- Product
- Adobe Acrobat Reader DC
- Device & OS
- not provided
- Scenario
- Users open PDFs through a shared terminal-server installation of Acrobat Reader DC.
- Observed behavior
- Reader appears to have changed to Acrobat Pro DC, and users without Adobe IDs may be unable to open PDFs.
Ask a server administrator to check the installed Acrobat product, version, and deployment package. Note whether the behavior affects every user or only specific user sessions.
Check Acrobat's 64-bit migration and shared deployment settings
Use this approach to identify whether the product appearance is related to Reader migration, licensing, or the shared installation.
A change in the displayed product does not by itself establish what caused the issue. Check both the installed package and the affected user's licensing or sign-in state.
Open Adobe's guide at https://helpx.adobe.com/acrobat/kb/about-acrobat-reader-dc-migration-to-64-bit.html and compare its 64-bit migration details with the installed version.
In the server's installed-apps list and the Acrobat Help > About screen, check the product name and version. On Windows, an administrator can open the installed-programs list by running appwiz.cpl.
Review the enterprise deployment package and shared-environment settings used for the server. In an affected user session, open Acrobat and check whether a Pro account, license, or trial is active.
If the wrong package or conflicting Pro components are present, have the administrator remove or redeploy them as appropriate using Adobe's enterprise guidance. Install the Reader package intended for the shared environment, then apply available updates through the approved deployment process.
Sign in to a fresh terminal-server session as an affected user and open a PDF from the shared location. Confirm which application launches and whether an Adobe sign-in prompt blocks access.

Use WPS Office to Open PDFs While You Troubleshoot Acrobat
WPS Office provides a PDF reader that users can try for opening documents while an administrator investigates the Adobe deployment. It does not repair Acrobat's installation or licensing.
- 1. Install WPS Office: Download WPS Office and ask the administrator to install it in accordance with the terminal server's deployment policies.
- 2. Open the PDF: Launch WPS Office, select Open, and browse to the PDF you want to read.
- 3. Check access in a user session: Open the same PDF from an affected user's session and confirm that WPS displays it successfully.

Frequently Asked Questions
Does the 64-bit Reader migration automatically mean Acrobat Pro was installed?
Not necessarily. Check the installed-apps list, Help > About, and the user's license or sign-in state, then compare the version with Adobe's 64-bit migration guidance.
Why are users being asked for an Adobe ID?
The prompt may relate to the deployed product or its licensing and sign-in settings. Check the enterprise package and the affected user's Acrobat session before changing the installation.
Should I uninstall every Acrobat component from the server?
No. First identify the installed products and deployment settings. An administrator should remove conflicting or incorrect components only as appropriate for the organization's Adobe deployment.
What should I send Adobe if the problem persists?
Contact Adobe enterprise support with the installed product and version, deployment details, affected-user symptoms, and relevant installation and licensing logs.




