Acrobat crashes at launch on Windows 11? Check the build

Record what happens during launch

"Acrobat crashes" can describe several different states. Open the desktop app directly from Start and watch what happens. Record the time to the minute, whether a window appears, whether it closes within seconds, whether it stays visible but stops responding, and whether Acrobat.exe or AcroRd32.exe remains in Task Manager.

• It closes before a full window appears. Keep the app build, activation, permissions, plug-ins, runtime, and installation state in scope.
• The window remains but says Not Responding. Use the app not responding guide. A hang is not the same as an immediate process exit.
• It opens until one PDF is selected. Keep that file, its location, and the viewing action in scope.
• Reader opens but Acrobat does not. Record the two products and builds separately.

Write down the Windows edition, version, OS build, system type, recent Adobe or Windows update, and any visible activation or sign-in message. Timing is useful evidence, but it does not prove that the most recent update caused the crash.

Identify the product, track, and build

Adobe maintains separate Acrobat and Acrobat Reader products. It also separates Continuous and Classic tracks. A release note for the Continuous track should not be applied blindly to a managed Classic installation.

If the app stays open long enough, use Help > About Adobe Acrobat or Help > About Adobe Acrobat Reader. Record the full build. On a managed PC, the Apps list, installed-program inventory, software center, or administrator may provide the version and track when the app closes too quickly.

Do not switch tracks, replace a managed package, or use a consumer installer over an organization deployment. Ask the responsible administrator which update channel and installer apply.

Apply the current Adobe update

Adobe's September 7 Continuous release note says build 26.002.21900 fixed bug 4597476, described as Acrobat crashing at launch. Adobe's release index lists 26.002.21901 one day later. Adobe also documents that current product updates are cumulative.

It is reasonable to infer that the later cumulative update includes the earlier launch-crash fix. Adobe does not say that bug 4597476 caused every matching symptom, so the build check is a precise first branch, not a universal diagnosis.

Use Acrobat's official update mechanism when it opens, or Adobe's official installer and enterprise update route for the identified product and track. Save work in other apps, keep the PC on reliable power, and follow organization policy. Restart Windows after the update, then try one direct launch.

If the current build opens, record the before and after versions and stop changing things. If it still closes, preserve that result instead of reinstalling immediately.

Run Adobe's repair once, then restart

On Windows, Adobe documents a repair through Control Panel for damaged installation files. Close Adobe apps. Open Control Panel > Programs > Programs and Features, select the installed Acrobat or Reader product, choose Change, and use the repair option that Adobe provides. On a managed PC, get administrator approval before changing the installation.

Restart Windows when the repair finishes. Launch the app directly once and record whether the window appears, closes, hangs, or remains usable. Do not run repair repeatedly if the result is unchanged.

If an activation message appears, use Adobe's account and activation path. Do not edit license files, certificates, hosts entries, services, or system time to force activation.

Separate launch crashes from one-PDF crashes

If Acrobat opens directly, test one known-good local PDF that contains no sensitive information. Do not begin with the file that first exposed the problem. Record whether the app stays open, closes when any file opens, or fails only with one document.

A crash tied to one PDF does not belong in the same branch as an app that cannot reach its start window. Keep the file's source, size, storage location, security setting, and repeatability in scope. Do not upload a private PDF to a public repair site, disable Protected View, or print to a new file merely to make the symptom disappear.

If browser tabs are also crashing, read the browser tab crash guide and widen the evidence beyond Acrobat.

Use one official reinstall only when needed

If the current supported build still exits after one repair and restart, preserve account and license details, close other Adobe apps, and use Adobe's official uninstall and install path for the correct product and track. Managed deployments belong with the administrator.

Use Adobe's download page. Do not use a mirror, patched executable, old installer archive, registry script, or third-party cleaner. Do not delete unrelated Adobe folders, plug-ins, profiles, fonts, certificates, PDFs, or user data.

Restart and test direct launch once after the reinstall. If it still fails, stop repeating the same change. The unchanged result and exact time are useful for the support handoff.

Preserve crash evidence for support

Adobe documents crash-report and diagnostic collection for Acrobat and Reader. Record the product, track, full build, Windows build, system type, launch method, time, visible state, and the result of the update, repair, restart, and controlled reinstall.

Reliability Monitor and Event Viewer may show the application name, faulting module, exception code, and event time. Adobe's own diagnostic tools can collect process, system, and product logs. Collection is evidence gathering, not a repair.

Logs can contain usernames, file paths, document names, account state, plug-in names, system details, and organization data. Review the files, destination, Adobe privacy terms, and workplace policy before uploading them. Do not post raw logs or private PDFs to a public forum.

Send the compact record to Adobe support or the organization administrator. State what changed and what did not. Avoid guessing at a plug-in, runtime, profile, or Windows component unless the evidence points there.

Where OmniMend fits

On Windows 10 or 11 x64, OmniMend 2.0.9 can organize read-only Windows, process, crash, update, and retest evidence around the Acrobat launch problem. Diagnosis is read-only. A supported repair inside OmniMend requires approval and a result check.

OmniMend does not update or repair Acrobat, reinstall Adobe software, edit the registry, change security controls, fix activation, support Windows Arm, or guarantee that the app will launch. Adobe's update, repair, reinstall, diagnostics, and support paths remain primary.

If you want a separate evidence record on a supported Windows x64 PC, review OmniMend's crash-analysis scope or download OmniMend. Read the privacy information before sharing any report.