Troubleshooting “Relocated Items” Breaking Adobe Folders

When upgrading macOS, Apple’s system migration process often flags modified shared configuration files and moves them into a Desktop shortcut named “Relocated Items”. If macOS moves the /Users/Shared/Adobe directory or system-level Adobe plugins out of their expected file paths, Creative Cloud applications lose access to critical licensing keys, plugin registries, and preset data. This results in startup crashes, missing presets, or license validation loops across Photoshop, Premiere Pro, and After Effects.

Fast-Fix: The 45-Second Solution

If Adobe apps crash or lose presets after a macOS update, check your Desktop for a Relocated Items shortcut. Open it, navigate to Configuration/Users/Shared/, and check if an Adobe folder exists. If present, copy the Adobe folder back to /Users/Shared/. Then, set folder permissions to Read & Write for all users and restart the Creative Cloud desktop app.

Quick Status Snapshot

• Severity Tier: High (Prevents application startup, background licensing, and plugin availability)
• Project Risk: Loss of customized workspaces, missing third-party plugins, project load failures, and persistent Creative Cloud login prompts
• Root Cause: macOS installer isolating modified files from /Users/Shared or /Library/Application Support into a secure archive folder during an OS update
• Rare Cause: System Integrity Protection (SIP) locking recreated /Users/Shared directories under restricted root-only permissions

Low-Friction vs. High-Friction Scenarios

• Low-Friction Scenario: macOS moved only the /Users/Shared/Adobe preferences or preset cache into Relocated Items. Dragging the folder back to /Users/Shared/ and granting correct user permissions fixes the issue immediately without reinstalling software.
• High-Friction Scenario: Migration Assistant moved core system files from /Library/Application Support/Adobe or broken permission inheritance across the entire shared drive. Restoring functionality requires using the Adobe Cleaner Tool, repairing file permissions via Terminal, and performing a clean reinstall of Creative Cloud.

Service-Level Mechanism

During a macOS system update, the installer checks all files on the drive against strict system security rules. Files located in shared paths that do not match macOS layout standards are moved to /Users/Shared/Relocated Items (or linked via a shortcut on your Desktop). Think of macOS as a shop manager reorganizing a workspace overnight; if tools were left on a shared counter instead of designated storage racks, the manager locks them away in a separate holding locker.

When Creative Cloud or host applications (like Premiere Pro or InDesign) start up, background services look for files in designated paths like /Users/Shared/Adobe for node licensing locks and shared preset references. When those paths are empty or missing, the application assumes corrupted settings or missing dependencies and shuts down immediately. If your system update also triggered account migration issues, see Troubleshooting “Migration Assistant” Failures for Adobe Users.

Probability Breakdown

• 60% – Missing /Users/Shared/Adobe Directory: macOS moved shared configuration folders during an OS update.
• 25% – Incorrect File Permissions on Restored Folders: The restored Adobe folder inherited “Read Only” or “System Only” ownership.
• 10% – Relocated System-Level Plugins: Third-party panels or legacy plugins moved out of /Library/Application Support/Adobe/Plug-ins/.
• 5% – macOS Security Blockade: macOS Sequoia blocking background process disk access to the restored folder structure.

Escalation Variables

Certain setup configurations increase the likelihood of Relocated Items breaking Adobe workflows:

• Upgrading across Multiple OS Versions: Jumping directly from older macOS releases to macOS Sequoia triggers aggressive file relocation routines.
• Non-Admin User Accounts: Restoring folders while logged into a standard account prevents setting correct read/write attributes on /Users/Shared/.
• Background Security Software: Security agents blocking Creative Cloud processes from creating replacement directories when /Users/Shared/Adobe disappears. For more on background security blocks, review Why macOS Sequoia Blocks Adobe Background Processes by Default.

The Cost of Delay: Immediate → Next Session

• Immediate: Applications fail to launch, display “Configuration Error 16”, or fail to load essential media encoders.
• Next Session: Creative Cloud continuously generates incomplete config files in temporary locations, triggering login loops and wiping user preferences on every reboot.

Diagnostic Contrast (Differential Diagnosis)

Distinguish Relocated Items file loss from other common macOS startup errors:

• Relocated Items vs. TCC Database Corruption: Relocated Items causes physically missing directories. If folders are in place but apps crash when accessing files, see Fixing “TCC.db” Permission Corruptions for Adobe Apps.
• Relocated Items vs. Full Disk Access Denied: If Adobe folders exist in /Users/Shared with correct permissions, but Premiere Pro still cannot save project files, see Why “Full Disk Access” is Mandatory for Premiere Pro 2026.
• Checking the Relocated Items Summary: Open the Relocated Items shortcut on your Desktop and open the report named Relocated Items.pdf. Look for lines referencing /Users/Shared/Adobe or /Library/Application Support/Adobe.

What To Do Right Now

1. Open Finder and navigate to /Users/Shared/. Check if an Adobe folder exists.
2. Open the Relocated Items shortcut on your Desktop (or go to /Users/Shared/Relocated Items/).
3. If an Adobe folder is inside Relocated Items/Configuration/Users/Shared/, copy it back into /Users/Shared/.
4. Right-click /Users/Shared/Adobe, click Get Info, unlock the padlock, and set Everyone to Read & Write.

Hard-Stop Failure Signals

Escalate to a full Adobe suite cleanup if you experience these symptoms:

• Error 16 or Error 192: Persistent licensing errors on every app launch despite restoring folders.
• Creative Cloud Desktop Login Loops: The desktop app repeatedly asks for credentials and fails to load installed apps. See Fixing “Keychain Access” Loops for Creative Cloud Login.
• System Folder Lockouts: Finder refuses to modify permissions on /Users/Shared with “Operation Not Permitted” alerts.

The Professional Recovery Sequence

Step 1: Locate and Extract Displaced Adobe Folders

1. Open Finder and double-click the Relocated Items alias on your Desktop.
2. If the alias is missing, navigate directly to /Users/Shared/Relocated Items.
3. Open the Configuration folder, then navigate to Users -> Shared.
4. Locate the displaced Adobe folder and any associated AdobeGCData folders.

Step 2: Restore Files to Native macOS Paths

1. Open a second Finder window and press Cmd + Shift + G.
2. Type /Users/Shared/ and press Enter.
3. Drag the Adobe folder from the Relocated Items directory into /Users/Shared/.
4. If a partial Adobe folder already exists in /Users/Shared/, select Merge or replace it with the restored folder.

Step 3: Repair Directory Permissions via Terminal

1. Open Terminal (Cmd + Space, type Terminal).
2. Run the following command to set folder ownership to your current account:Bash sudo chown -R $(whoami):staff /Users/Shared/Adobe
3. Run this command to grant complete read and write access across the folder:Bash sudo chmod -R 777 /Users/Shared/Adobe
4. Enter your Mac administrator password when prompted.

Step 4: Re-link Plugin and Preset Directories

If custom plugins or scripts were moved from /Library/Application Support/Adobe/, drag them back to /Library/Application Support/Adobe/Plug-Ins/. If you cannot see hidden library folders, follow Fixing “User Library” Visibility for Manual Plugin Installation.

Required Resource Allocation

• Admin Rights: Full administrator privileges on macOS to modify shared directory permissions.
• Storage Overhead: Free disk space on the system drive equal to the size of the relocated folders (typically 2 GB to 10 GB).
• Terminal Access: Standard command-line access to run basic permission repairs.

Combined Symptom Escalators

• Missing Adobe Folders + Persistent Permission Alerts: Indicates both file displacement and system-level security isolation. Full Disk Access must be re-granted after folder restoration.
• Missing Adobe Folders + Dynamic Link Failures: Premiere Pro and After Effects fail to pass comps back and forth because shared bridge files in /Users/Shared/Adobe are incomplete.

Final Render

Restoring displaced folders from Relocated Items and resetting access permissions on /Users/Shared/Adobe reconnects Creative Cloud to its local licensing and preset files, eliminating launch crashes without requiring a full operating system reinstall.