Fix Acrobat DC Crash on Windows 11 24H2

The Short Version: What Gets You Back to Work

If you've just updated to Windows 11 24H2 and Acrobat DC now dies on launch with the dreaded "Acrobat Failed to Start" dialog, don't uninstall and reinstall yet. That wastes twenty minutes and usually doesn't fix it. What actually works, for the vast majority of people, is disabling Acrobat's protected mode.

Close Acrobat completely. Check the taskbar and Task Manager (Ctrl+Shift+Esc) — kill any lingering Acrobat.exe processes.
Open the registry editor. Press Win+R, type regedit, hit Enter.

Navigate to:

HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\DC\Privileged

Look for a DWORD value named bProtectedMode. If it's not there, right-click in the right pane, choose New → DWORD (32-bit) Value, and name it bProtectedMode.
Double-click it, set the value to 0, click OK.
Close regedit and launch Acrobat DC. It should start clean.

That's it. No need to touch the installation directory, no need to run as administrator, no need to roll back the Windows update.

Why This Works

What's actually happening here is a sandboxing conflict. Acrobat DC runs its core rendering engine inside a restricted environment — protected mode — that acts like a security sandbox. It prevents a malicious PDF from taking over your system by limiting what the process can access.

Windows 11 24H2 changed how the kernel handles certain memory and process isolation features, specifically around Arbitrary Code Guard and Virtualization-Based Security. Adobe's protected mode wasn't designed for those stricter policies, so it fails to initialize properly. When it fails, Acrobat can't start the main app at all — that's the "Acrobat Failed to Start" error.

Disabling protected mode removes that sandbox layer, so Acrobat doesn't have to negotiate with the new OS security features. The app launches normally. Yes, you lose some security when opening untrusted PDFs, but for a trusted document workflow, it's an acceptable trade-off — at least until Adobe ships a proper patch.

Less Common Variations

Some people hit this error even after disabling protected mode. If that's you, try these in order.

1. Corrupted Preferences

Acrobat stores its preferences in a folder that sometimes gets corrupted during a big OS update. Rename the entire preferences folder so Acrobat rebuilds it from scratch:

Close Acrobat. In File Explorer, go to:
%appdata%\Adobe\Acrobat\DC
Rename the "Security" folder to "Security.old".
Launch Acrobat.

If that doesn't do it, rename the whole DC folder to DC.old. You'll lose your custom settings, but you'll get a working app. You can dig through DC.old later to copy over any saved stamps or custom dictionaries.

2. Conflicts with Third-Party Shell Extensions

I've seen cases where the culprit isn't Acrobat at all — it's a PDF preview handler installed by another app, like Nuance or Foxit. These register themselves as the default handler for PDFs, and after a Windows update, their context menu extensions can crash Acrobat when it tries to initialize them.

Check your default PDF handler: Settings → Apps → Default apps → set the default for .pdf to Acrobat DC. Then reboot. If Acrobat still crashes, temporarily disable any PDF-related shell extensions using ShellExView. Look for entries from Foxit, Nuance, or PDF-XChange.

3. The Visual C++ Redistributable Angle

Windows 11 24H2 ships with a newer version of the Universal C Runtime, but some older Acrobat builds still depend on the 2015–2019 Visual C++ redistributable. If protected mode is off and preferences are fresh, but Acrobat still won't start, reinstall the redistributable:

Download from Microsoft's official site:
vc_redist.x64.exe (the latest one, for both 2015-2022)
Run it, choose Repair, reboot.

Why this matters: the update can leave behind a broken copy of msvcp140.dll that Acrobat needs. Repairing the runtime re-registers those DLLs without affecting anything else.

Prevention: Keep This From Happening Again

The real fix is to stop Acrobat from tripping over the next OS update. Here's what I do:

Keep Acrobat DC updated. Adobe pushes patches for exactly these compatibility issues. Go to Help → Check for Updates, or better, enable automatic updates. The version that fixes 24H2 is the July 2024 release (24.002.20759 or later). If you're on an older build, that's your problem right now.
Don't disable protected mode permanently. Once Adobe ships a proper fix (and they have, in recent updates), re-enable it by setting bProtectedMode back to 1. Living without the sandbox is fine for a week, not for a year.
Check Acrobat's known issues page before installing a Windows feature update. Adobe maintains a release notes page that lists OS compatibility problems. A thirty-second glance could've saved you the whole headache.

One last thing: if you're using an older Acrobat version (2017 or 2020), none of this registry trick works — those use a different key path. You'll need to install Acrobat DC or use the workaround of running the app in Windows 10 compatibility mode, which is a clunkier fix but still functional.

Now go open that PDF. The fix holds until the next Windows update — and when it breaks again, you'll know exactly where to look.