Other PDF Issues

How to Fix Acrobat 11 Freezing on Windows Server 2016 Remote Desktop

Muhammad TalhaMuhammad Talha Oct 28, 2026 868 views

Question details

The user needs to resolve an issue where the PDF viewer becomes unresponsive and crashes when scrolling through documents over a remote session.

How to Fix Acrobat 11 Freezing on Windows Server 2016 Remote Desktop
Product
Adobe Acrobat 11
Device & OS
Windows Server 2016
Scenario
Scrolling through PDF documents opened from Perfect Practice integration within a Remote Desktop Services session host.
Observed behavior
The application freezes, pages turn white, and crashes occur involving Acrobat.exe, ntdll.dll, and exception code 0xc0000374.
Before you start

Ensure you have administrative privileges on the Windows Server 2016 session host to modify application preferences or install software updates.

Solution 1Recommended

Disable 2D Graphics Acceleration

Disabling hardware-based rendering prevents display conflicts and freezing issues specifically over Remote Desktop protocol.

Remote Desktop environments often struggle with hardware acceleration designed for local GPUs. Turning off 2D graphics acceleration forces the application to use software rendering, which is significantly more stable in virtual and remote sessions.

1
Open Preferences

Launch Acrobat 11. Navigate to the top menu bar, click on 'Edit', and select 'Preferences' from the drop-down menu.

2
Navigate to Page Display

In the left-hand pane of the Preferences window, select 'Page Display' to view the rendering options.

3
Disable Graphics Acceleration

Under the 'Rendering' section, locate and uncheck the box labeled 'Use 2D graphics acceleration'.

4
Apply and Restart

Click 'OK' to save your changes, then completely close and restart the application to apply the new rendering settings.

Disable 2D Graphics Acceleration
Performance Impact: Disabling this setting may slightly alter text smoothing, but it will drastically reduce white-page glitches and heap corruption crashes.
Seamless Remote Desktop PDF Solution

Read and Edit PDFs Smoothly with WPS Office

Bypass legacy software crashes entirely by using WPS PDF. It is highly optimized for modern Windows Server environments, providing smooth scrolling, reliable rendering over Remote Desktop, and robust editing tools without demanding heavy system resources.

  1. 1. Install WPS Office on the Server: Download and install the latest version of WPS Office on your Windows Server 2016 session host.
  2. 2. Set as Default PDF Viewer: Right-click any PDF document, select 'Open with', choose 'WPS Office', and check 'Always use this app to open .pdf files'.
  3. 3. Enjoy Smooth Scrolling: Open your PDFs directly or through your document management system and enjoy fast, crash-free navigation.
Lightweight architecture perfectly suited for Remote Desktop ServicesHigh compatibility with standard PDF documents and legacy formatsNo graphics rendering conflicts or white-page glitchesIncludes a comprehensive suite of viewing, editing, and conversion tools
microsoft office alternative - wps office

Frequently Asked Questions

Why do pages turn white when scrolling a PDF via Remote Desktop?

White pages typically appear due to rendering failures over the RDP protocol. The application attempts to use local hardware acceleration which isn't fully supported across remote sessions. Disabling 'Use 2D graphics acceleration' in the application settings generally resolves this display failure.

What does exception code 0xc0000374 mean in an application crash?

Exception code 0xc0000374 signifies a heap corruption error in Windows. In the context of older software like Acrobat 11, it indicates that the application or a third-party plugin mismanaged system memory, leading the operating system to forcefully terminate the process to prevent instability.

Is Adobe Acrobat 11 officially supported on Windows Server 2016?

No, Acrobat 11 reached its official end of support before Windows Server 2016 was widely adopted. Running obsolete software on newer server infrastructures often leads to unpatched compatibility issues, security vulnerabilities, and unpredictable application freezing.