Error 1: Unexpected exit

Adobe Suite crash on launch: fix missing licensing files

Software – Adobe Suite Intermediate 👁 18 views 📅 May 26, 2026

Adobe apps crash at launch when licensing files get corrupted. The fix is deleting the OOBE folder and letting the apps regenerate it.

Quick answer

Delete the OOBE folder from ProgramData (Windows) or Library/Application Support (macOS) and relaunch Adobe Creative Cloud. The apps will regenerate the licensing files on next startup.

Why this happens

This error pops up most often after a Windows or macOS update, or after a failed Adobe Creative Cloud update. Licensing files inside the OOBE folder get corrupted — usually a permission shift or a partial write from a background update. The apps check for these files at launch, find something wrong, and bail out with Error 1. I've seen this on everything from Photoshop 2023 to After Effects 2024. It's not a hardware issue. Don't bother reinstalling the whole suite. You'll waste an hour and still need to delete these files anyway.

Fix steps (Windows)

  1. Close all Adobe apps. Even check the system tray for Creative Cloud and quit it there.
  2. Press Win + R, type %ProgramData%, hit Enter. This opens the hidden ProgramData folder.
  3. Find the Adobe folder, then AdobeGCClient inside it. Right-click the OOBE folder and delete it. Windows might ask for admin permission — click Yes.
  4. Open Task Manager (Ctrl + Shift + Esc), look for any Adobe processes still running (like AdobeIPCBroker or Adobe Desktop Service). End them if you see them.
  5. Restart your machine. Don't skip this — it clears stuck file locks.
  6. Launch Creative Cloud first. Let it fully load. Then open any Adobe app. It'll rebuild the OOBE folder and licensing files.

Fix steps (macOS)

  1. Quit all Adobe apps. Force quit if you have to (Cmd + Option + Esc).
  2. Open Finder, hit Cmd + Shift + G, paste /Library/Application Support/Adobe.
  3. Find the AdobeGCClient folder. Inside it, delete the OOBE folder.
  4. Empty the Trash. Then restart your Mac.
  5. Open Creative Cloud, let it sit for a minute. Then launch your Adobe app.

If that doesn't work

Sometimes the corruption goes deeper. Try these in order:

  • Run the Adobe Creative Cloud Cleaner Tool. Download it from Adobe's site (free). Run it, select your app, and do a clean uninstall. Then reinstall from Creative Cloud. This nukes leftover junk.
  • Check your hosts file. Rare, but some third-party firewall or VPN tools block Adobe's licensing servers. Look in C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (macOS). Remove any lines pointing to licensing.adobe.com or similar.
  • Repair permissions on the OOBE folder. On macOS, run sudo chmod -R 755 /Library/Application Support/Adobe/AdobeGCClient then delete the OOBE folder again. On Windows, right-click the AdobeGCClient folder, Properties, Security tab, Advanced, and make sure SYSTEM and Administrators have Full Control.

Prevention tips

This keeps happening if you let Adobe auto-update in the background while you're working. The update process gets interrupted, and next thing you know, licensing files are toast. I've stopped this from recurring by doing two things:

  • Turn off automatic updates in Creative Cloud preferences. Set them to notify only.
  • Before any Windows or macOS major update, close all Adobe apps completely. Don't just close the window — quit from the system tray or menu bar. Then run the updates.

Also, if you're in a corporate environment with roaming profiles or folder redirection, the OOBE folder sometimes gets written to a network location instead of local disk. That's a whole separate mess — talk to your IT team about excluding Adobe folders from sync. I've seen that cause this exact crash on login.

One last thing: if you're using Adobe apps from a volume license or a school account, the licensing structure is different. Deleting OOBE might not help. Run the Adobe Licensing Toolkit instead. But for normal Creative Cloud subscriptions, deleting OOBE fixes it 9 times out of 10.

Was this solution helpful?