Other PDF Issues

Fix Acrobat Outlook PDF Portfolio Plugin Failing on RDS

Rana GarciaRana Garcia Nov 5, 2026 868 views

Question details

The Acrobat Outlook plugin creates blank PDF portfolios for subsequent users on a Windows Server 2019 RDS environment after the first user session.

How to Fix Acrobat Outlook PDF Portfolio Plugin Failing for Multiple RDS Users
Product
Adobe Acrobat Plugin for Microsoft Outlook
Device & OS
Windows Server 2019
Scenario
Multiple users attempt to use the Acrobat plugin within Outlook to create PDF portfolios simultaneously in a Remote Desktop Services (RDS) environment.
Observed behavior
The first user successfully creates a PDF portfolio, but all subsequent users receive blank PDF portfolios due to shared background processes locking up.
Before you start

Ensure you have administrator privileges on the Windows Server to manage shared components, apply system patches, and modify Remote Desktop Services temporary folder settings.

Solution 1Recommended

Resolve Shared Process Locking

Identify and terminate shared background processes that become locked by the first Outlook session, preventing other RDS users from generating PDFs.

In a multi-user Remote Desktop Services environment, specific executable files like HTML2PDFWrapFor64Bit.exe or AcroTray.exe can become locked by the first user who triggers the Acrobat plugin. When this happens, subsequent users encounter blank outputs because the shared component is unavailable.

1
Open Task Manager on the Server

Right-click the server taskbar and select 'Task Manager', then navigate to the 'Details' tab to view all running processes across all user sessions.

2
Locate Locked Acrobat Processes

Scroll through the list to find processes named HTML2PDFWrapFor64Bit.exe, AcroTray.exe, or Acrobat.exe that are currently active under the first user's session ID.

3
Terminate and Test

Right-click the locked process and select 'End task'. Ask a secondary user to attempt creating a PDF portfolio in Outlook to confirm if the plugin now functions correctly.

Resolve Shared Process Locking
Process Isolation: If terminating the process works temporarily, you may need to configure the server or contact Adobe Enterprise Support to enforce process isolation for the HTML2PDFWrap component.
Free Microsoft Office alternative

Try WPS Office for Seamless Document Management

If Microsoft Office and Adobe Acrobat plugins continue to cause process lockups in multi-user environments, consider switching to WPS Office. It provides a lightweight, highly stable environment with built-in PDF tools that eliminate the need for heavy third-party plugins.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer tailored for Windows.
  2. 2. Install on Your Server or PC: Run the setup file and follow the standard installation prompts to deploy the software.
  3. 3. Access Built-in PDF Tools: Open WPS Office and select the 'PDF' tab from the main workspace to instantly create, edit, or merge PDFs natively.
Highly compatible with Microsoft Office formats (Word, Excel, PowerPoint)Built-in PDF toolkit to read, edit, and manage PDFs without external pluginsLightweight architecture ideal for Remote Desktop Services (RDS) and multi-user serversFamiliar user interface for quick adoption and seamless migration
microsoft office alternative - wps office

Frequently Asked Questions

Why are my Outlook emails converting to blank PDFs in Adobe Acrobat?

This usually happens when a required shared component, such as HTML2PDFWrapFor64Bit.exe, is locked by another user or session. It can also occur due to insufficient read/write permissions in the Windows temporary folders.

Does this Acrobat plugin issue also affect Windows 11 and Microsoft 365?

Yes. Users have reported similar issues where emails erratically convert to blank portfolios on Windows 11 running Microsoft 365, indicating broader plugin compatibility issues beyond just Windows Server 2019 RDS environments.

How do I fix Acrobat process isolation issues on a multi-user server?

You can mitigate process isolation issues by configuring Group Policy to enforce per-session temporary folders and ensuring you are running the latest enterprise patches. If the component remains locked, you may need to reach out to Adobe Enterprise Support for an application-level fix.