Adobe Keeps Crashing | Fixes That Stick

An Adobe app that quits mid-task can wreck a file and your mood. Most crash loops come from a short list: a messy update state, damaged preferences, a GPU clash, a stale plug-in, or a cache that’s gone bad. You don’t need to guess. You can narrow it down with a few controlled tests.

The steps below work for Windows and macOS. Start with the fast checks, then move to deeper repairs. Stop the moment the crashing ends.

What Counts As A Crash And What To Note First

“Crash” can mean a hard close, a freeze that forces Quit, or a pop-up that says the app had to close. The fix is easier when you spot a pattern. Take one minute to capture three details, then start changing things.

• Write the app and version — Note the exact app name and version from the Creative Cloud desktop app or the app’s About screen.
• Note the trigger moment — Launching, opening a file, exporting, switching workspaces, or using a specific tool.
• Save the error clue — Copy any code or message, or snap a screenshot of the crash dialog.

Crashes on launch often point to preferences, fonts, or permissions. Crashes during export often point to GPU settings, cache files, or an effect that isn’t playing nice.

Fast Fixes That Stop Most Adobe Crashes In Minutes

Start here. These are quick, low-risk moves that clear a lot of common crash causes.

• Restart the computer — A reboot clears stuck background tasks and locked cache files.
• Update the Adobe app — In Creative Cloud desktop, install the latest patch for the crashing app.
• Update Creative Cloud desktop — Install updates for the desktop app too, then reopen it.
• Try a clean launch — Close other heavy apps, unplug extra displays if you can, then launch again.

If the crash is gone, you’re done. If it still happens, go step by step from here.

Reset Preferences And Caches When Adobe Keeps Crashing

Preferences store workspaces, recent files, performance choices, and more. When a preference file gets damaged, the app may crash at launch or right after you click a tool. Resetting preferences is often the quickest “deep” fix.

Reset preferences without losing everything

• Use the reset prompt — Many Adobe apps can reset preferences during launch with a keyboard shortcut, then confirm the prompt.
• Rename the settings folder — If you don’t see a prompt, close the app and rename its settings folder so it rebuilds on next start.
• Bring settings back slowly — Re-apply only what you need, then test. Don’t import old workspaces right away.

Clear caches that can crash exports and previews

Cache folders speed previews and thumbnails. They can also turn into a crash trigger when a cache file is locked, bloated, or out of sync after an update.

• Purge the app cache — Clear Media Cache or similar cache tools inside the app’s preferences where available.
• Clear temp files — On Windows, delete what you can from %temp%. On macOS, restart to flush temp items.
• Check disk space — Keep free space on the drive used for scratch and caches, or exports may fail.

GPU And Driver Checks For Sudden Closes

Most Adobe apps lean on the GPU for drawing and playback. When the GPU driver is old, corrupted, or mismatched with a new app build, you can see crashes tied to zooming, scrubbing, switching panels, or exporting.

Run a fast GPU isolation test

• Turn off GPU acceleration — Disable hardware acceleration or GPU rendering, relaunch, then retry the exact action that crashes.
• Switch to software for one job — Export once with a software renderer option if your app offers it.
• Lower the load — Drop playback resolution, pause background renders, and close GPU-heavy apps while you test.

If stability returns with GPU off, focus on driver health and GPU settings next.

Update GPU drivers with fewer surprises

• Install the vendor driver — Use NVIDIA, AMD, or Intel drivers rather than an older default driver.
• Pick a clean install — Choose a clean install option if the installer offers it, then reboot.
• Re-enable GPU and retest — Turn GPU acceleration back on and run the same task again.

On laptops with two graphics chips, set the Adobe app to use the high-performance GPU in system graphics settings. GPU switching can cause mid-task exits.

Plug-ins, Fonts, And Files That Trigger Repeat Crashes

If the app crashes only with certain projects, or right after you add an effect, the trigger may live in a plug-in, a font, or the file itself. This section helps you isolate the culprit without wrecking your setup.

Isolate third-party plug-ins and extensions

• Start with plug-ins removed — Move third-party plug-ins out of the plug-ins folder, then launch and test.
• Update each plug-in — Install the newest build that matches your Adobe app version.
• Restore one at a time — Add a single plug-in back, test, then repeat until you spot the trigger.

Handle fonts that crash design apps

Corrupt fonts can crash at launch or when text tools load. This shows up after font installs or after syncing fonts from multiple sources.

• Disable recent fonts — Turn off fonts added right before the crashing started, then relaunch.
• Rebuild the font cache — Clear the OS font cache using safe system steps, then restart.
• Keep a lean font set — Store rarely used fonts outside the active system fonts list.

Test whether the file is the trigger

• Open a blank project — If a fresh file works, the crash may be tied to a project file or an asset.
• Import into a new file — Create a new project and import assets rather than opening the crashing file directly.
• Save locally with a short path — Copy the project to a local SSD and use a simple name to reduce path issues.

Sync folders and network drives can add file locks and partial writes. For testing, work local, then copy the finished folder back when the app is closed.

Repair Installs And System Settings When The Crash Won’t Quit

If you’ve done the steps above and the crash pattern doesn’t change, repair the install state. This is where you fix damaged program files, blocked folders, and background services that keep the app unstable.

Reinstall cleanly from Creative Cloud

• Uninstall and reinstall the app — Remove the app in Creative Cloud desktop, reboot, then install it again.
• Remove leftovers — Delete remaining app folders after uninstall if they remain, then reinstall once more.
• Reset Creative Cloud cache — Quit Creative Cloud desktop, clear its cache folders, then reopen it.

Check permissions and security blocks

Security tools can block an app from writing to its cache or licensing folders. That can cause silent exits on launch or crashes when saving.

• Allow-list the app — Add the Adobe app and Creative Cloud desktop to allow-lists in antivirus or endpoint tools.
• Verify write access — Confirm your user can write to Documents, AppData (Windows), Library (macOS), and the cache location used by the app.
• Test controlled folder access — If Windows Controlled Folder Access is on, test it off briefly to see if crashes stop.

Use this decision table to pick the next move

Symptom	Best First Fix	Time
Crashes on launch	Reset preferences and fonts	10–20 min
Crashes on export	Disable GPU and clear caches	15–30 min
Crashes with one project	Import into a new project	10–40 min
Random exits mid-work	Driver update and reinstall	30–60 min

If none of these steps change the crash pattern, grab the crash report logs and send them through Adobe’s help center so they can match the error signature to a known bug.

Keep Crashes From Coming Back After You Fix Them

Once things are stable, a few habits keep it that way. These keep your setup clean and reduce the chance of the same crash loop returning after the next patch.

• Patch at a quiet time — Update when you can open a test project and run a short export afterward.
• Match plug-ins to app versions — Update plug-ins right after app updates, then test one project.
• Install fewer fonts — Add fonts only when you need them, then archive the rest.
• Work from a local SSD — Edit locally, then copy to cloud storage after you close the app.
• Use autosave and versions — Turn on autosave, keep incremental saves, and export backups before big edits.

When adobe keeps crashing, treat it like a small science project. Save work often during these tests. Change one thing, retest, then move on. Once you find the trigger, the fix tends to hold.

If you’re stuck in a loop where adobe keeps crashing on launch even after a reinstall, try a fresh user account test again. If it works there, the issue sits in your user profile and you can migrate settings in small pieces.