Fix Adobe Acrobat File Association Missing in Windows Server RDSH
Question details
Users in a Windows Server 2016 Remote Desktop Services environment are unable to set Adobe Acrobat 2017 as the default PDF handler because it is missing from the RDSH file association list.
- Product
- Adobe Acrobat
- Device & OS
- Windows Server 2016
- Scenario
- Configuring default PDF applications in a Remote Desktop Services (RDS) session host deployment.
- Observed behavior
- Adobe Acrobat 2017 does not appear in the available applications list for PDF associations, preventing administrators and users from assigning it as the default PDF handler, even though Adobe Reader appears normally.
Ensure you have administrator access to the Windows Server 2016 RDSH environment and verify the exact installation method and version of Adobe Acrobat currently deployed.
Repair Acrobat and Re-register the Application
Repairing the Acrobat installation within the RDS environment often restores missing registry keys required for file associations.
In RDSH environments, applications must be installed specifically for Remote Desktop sessions. If Acrobat was installed incorrectly, its file association ProgIDs might not register properly for all users.
Open the Command Prompt as an administrator and type 'change user /install' to put the server into Remote Desktop installation mode.
Go to Control Panel > Programs > Programs and Features. Locate Adobe Acrobat 2017, right-click, and select 'Change', then choose 'Repair' and complete the on-screen wizard.
Once the repair is complete, return to the Command Prompt and type 'change user /execute' to switch the server back to application execution mode.
Configure File Associations via Group Policy (GPO)
Force the PDF file association at the domain or organizational unit level using a custom XML configuration file.
Try a Lightweight PDF and Office Suite for RDSH
If deploying and managing heavy PDF software like Adobe Acrobat in Windows Server RDS environments proves difficult and causes association errors, WPS Office offers a streamlined alternative. It features a built-in, robust PDF editor alongside full Word, Excel, and PowerPoint alternatives, optimized for multi-user and remote desktop environments.
- 1. Download WPS Office: Visit the official WPS Office website and download the enterprise or standard installer suitable for Windows environments.
- 2. Deploy in RDS Install Mode: Switch your Windows Server to install mode by running 'change user /install' in Command Prompt, then run the WPS Office installer.
- 3. Set as Default PDF Handler: Open Windows Default Apps settings and select WPS PDF as the default application for all .pdf files.
Frequently Asked Questions
Why does Adobe Reader show up in the RDSH list but Acrobat does not?
Adobe Reader is often installed with global defaults that universally register its file associations out of the box. Conversely, Acrobat requires specific Remote Desktop deployment steps, such as using the Adobe Customization Wizard, to register properly for all session users in an RDS environment.
How do I find the correct ProgID for Adobe Acrobat 2017?
You can find the ProgID by opening the Registry Editor (regedit) and navigating to HKEY_CLASSES_ROOT\.pdf. Look at the default string value for this key, which usually points to the installed ProgID, such as Acrobat.Document.2017.
Do I need to uninstall Adobe Reader to fix Acrobat file associations?
Not necessarily. You can run both in an RDS environment, but you must strictly manage file associations using a Group Policy XML file to ensure Windows Server correctly routes PDF file requests to Acrobat instead of defaulting to Reader.
