Skip to main content
Participant
Nov 17, 2026 6:49 PM UTC
Question

Reader 26.2.22031.0: Accessibility.api process enumeration saturates UI thread; disabling assistive technology resolves it

Technical bug report — request for Acrobat Reader engineering investigation

Summary
Acrobat Reader was sluggish throughout normal use, not only when opening PDFs. Native stack samples localized sustained main UI thread CPU usage to Accessibility.api performing Windows process enumeration. Disabling assistive technology support removed the observed hot path and reduced CPU work by approximately 96–98%. Please investigate a permanent fix that preserves accessibility support.

Environment
Adobe Acrobat Reader 64-bit, version 26.2.22031.0. Windows 11 Pro (Acrobat system report: OS version 10.0.26300), 20 logical processors, approximately 32 GB RAM. Intel Iris Xe and NVIDIA RTX 3050 Ti Laptop GPU; active display reported on Intel. Incident: 17 November 2026.

Observed behavior
The main window thread consumed 4.796875 CPU seconds in five seconds: approximately 96% of one logical CPU, or 4.8% total CPU capacity on this machine. Most measured thread CPU time was privileged/kernel time. Four of five high-CPU native samples included Accessibility.api calling KERNEL32!CreateToolhelp32Snapshot / Process32NextW and ntdll system calls through Oleacc/UIAutomationCore message processing. Repeated Accessibility.api offsets: +0xf2f9 / +0xf33e, +0x4a582, +0x36c69. Private Adobe symbols were unavailable, so nearest exported symbol names in the raw samples are not exact internal function identifications.

Memory and disk pressure did not explain the captured load. A sampled 1.8 MB PDF was locally available and read fully in approximately 12 ms. Sluggishness occurred across PDF files.

Observed reproduction/comparison (affected session, not a guaranteed clean-system recipe)
1. Enable Preferences > Accessibility > Enable assistive technology support.
2. Display a PDF in the normal document window, with no Preferences or System Information dialog open. Observe sustained main-thread CPU and collect native stack samples.
3. Uncheck Enable assistive technology support and apply.
4. Repeat CPU measurements and stack sampling in the same Reader process.
5. Scroll the existing PDF and open another 17-page PDF.

Expected
Responsive interaction and low idle CPU while accessibility support remains enabled, including when accessibility or UI Automation clients query Reader.

Workaround and validation
Unchecking Preferences > Accessibility > Other Accessibility Options > Enable assistive technology support persisted bEnableAT=0 under HKCU\Software\Adobe\Adobe Acrobat\DC\Access. No restart was needed.
Before: 4.796875 CPU seconds per five seconds.
After: 0.1562, 0.1094, 0.2031 CPU seconds per five seconds (approximately 95.8–97.7% less CPU work).
Five subsequent native samples showed the main thread waiting in NtUserGetMessage without the previous Accessibility.api enumeration chain. Scrolling updated the existing document view. A different 17-page PDF opened successfully; subsequent aggregate Acrobat CPU readings were approximately 0.19–0.23% of total machine capacity. Reader remained responding.
Only the accessibility preference was changed; no plugin binary, driver, or security setting was changed. The workaround can affect screen-reader integration.

Limitations
Native thread contexts and StackWalk64 produced point-in-time samples, not a continuous trace or memory dump. WPR profiling failed with 0xc5585011. Windows UI Automation was used during inspection and may interact with or amplify this path; high CPU was measured before UI inspection. The original triggering client and precise private Adobe source-code defect remain unconfirmed. No long-duration or restart-persistence test was performed.

Request
Please investigate repeated process enumeration in Accessibility.api under UI Automation/MSAA queries, confirm whether a fix exists, and advise how to preserve accessibility support without the sustained UI-thread CPU load. Supporting before/after diagnostic files are available locally but are not attached to this post because browser file-upload authorization was blocked. No PDF documents, screenshots, personal filenames, or personal folder paths are included in this post.