Error 120: Low Disk Space on System Drive (Hidden Temp Files)

Adobe Error 120 occurs when the Creative Cloud installer halts because your primary OS drive lacks sufficient contiguous space to unpack and stage installation files. Even when File Explorer or Finder shows free gigabytes, hidden temporary caches, leftover setup archives, and system paging files temporarily bloat the drive during extraction, exhausting available storage and halting the process.

Fast-Fix: The 45-Second Solution

If your main drive shows free space but the installer fails with Error 120, hidden setup caches are consuming your storage during extraction. Immediately purge %TEMP% on Windows or ~/Library/Caches on macOS, empty the Trash/Recycle Bin, and ensure your system drive has at least 20 GB of unallocated disk space before launching the installer with administrative rights.

Quick Status Snapshot

  • Severity Tier: Moderate
  • Project Risk: Low (Installation and update routines fail; existing local media files remain untouched)
  • Root Cause: Primary OS drive (C:\ or macOS root partition) running out of working headroom during zip extraction and payload staging.
  • Rare Cause: System virtual memory swap files (pagefile.sys or swapfile) expanding mid-installation and choking drive capacity.

Low-Friction vs. High-Friction Scenarios

  • If it happens during file extraction (10–30% progress): Uncompressed installer payloads are expanding inside hidden temporary folders, requiring double their compressed file size in real-time buffer space.
  • If it happens near final installation (80–90% progress): System virtual memory page files or local OS recovery snapshots are competing with the installer for the last remaining blocks of drive space.

Service-Level Mechanism

When installing or updating an app, Creative Cloud uses a two-stage process: it downloads a compressed package archive and unpacks it into the system’s designated temporary staging directory (%TEMP% on Windows or /tmp on macOS) before moving the final compiled files to Program Files or Applications. Error 120 triggers when the file system signals zero write availability on the root partition. Think of an overfilled engine oil sump: if you pour fresh oil in without draining the dirty fluid sitting in the pan, the reservoir overflows instantly and brings the mechanism to a complete stop.

Escalation Variables

  • Installing Large Suite Bundles: Attempting to install multiple heavy applications (like Premiere Pro, After Effects, and Photoshop) simultaneously multiplies temp file staging demands.
  • Fixed Partition Allocations: Small primary system partitions (e.g., a 128 GB C: drive) where secondary storage is on another drive, as Creative Cloud mandates primary drive staging regardless of chosen install paths.
  • Hibernation & Paging Bloat: High physical RAM usage causing the OS to dynamically expand system swap files during background setup tasks.

The Cost of Delay: Immediate → Next Session

Ignoring Error 120 leaves incomplete extraction folders scattered across your system drive. Repeating the install without clearing these partial archives further starves your operating system of scratch space, eventually causing general system sluggishness, application crashes, and secondary installation errors like [INTERNAL LINK: S01C01.07 – Error 107: Resolving ‘Out of Disk Space’ Errors During Extraction].

What To Do Right Now

  1. Cancel the failed installation process.
  2. Open the OS storage manager and purge temporary files.
  3. Empty the system Recycle Bin or macOS Trash.
  4. Reboot the computer to force the OS to release dynamic swap files and temporary file locks.

Hard-Stop Failure Signals

  • Drive Red-Lining: File Explorer or Finder displays the primary OS drive in solid red, with under 2 GB of remaining space.
  • Write Denial Warnings: Operating system alerts warning that system services cannot save configuration state files.

The Professional Recovery Sequence

Method 1: Purge Hidden Windows Temp Folders

  1. Press Win + R to open the Run dialog box.
  2. Type %temp% and press Enter to open the local temporary folder (C:\Users\<User>\AppData\Local\Temp).
  3. Select all files (Ctrl + A) and press Shift + Delete to permanently remove them. Skip any items currently locked by active system processes.
  4. Press Win + R again, type temp, press Enter (C:\Windows\Temp), and delete all contents.
  5. Run Disk Cleanup (cleanmgr.exe), select drive C:, check Temporary Files, Delivery Optimization Files, and Recycle Bin, then click OK.

Method 2: Purge Hidden macOS Caches and Local Snapshots

  1. Open Finder, click Go in the top menu bar, select Go to Folder…, and type:Plaintext ~/Library/Caches
  2. Move large cached setup directories (specifically Adobe installer folders) to the Trash.
  3. If using Time Machine, clear local APFS snapshots by opening Terminal (Cmd + Space > type “Terminal”) and running:Bash sudo tmutil thinLocalSnapshots / 10000000000 4
  4. Empty the Trash completely.

Method 3: Clear Adobe Direct Download Staging Caches

  1. Navigate to the Adobe installation cache path:
    • Windows: C:\ProgramData\Adobe\Installer\ and C:\Users\<User>\AppData\Local\Adobe\OOBE
    • macOS: /Library/Application Support/Adobe/Installer/
  2. Delete leftover .zip, .dmg, or folder archives matching recent setup attempts.
  3. Relaunch the Creative Cloud desktop application.

Method 4: Relocate Default Windows Temp Environment (Optional for Small System Drives)

If your primary drive partition is restricted in size:

  1. Create a folder named TEMP on a larger secondary partition (e.g., D:\TEMP).
  2. Press Win + R, type sysdm.cpl, and go to the Advanced tab.
  3. Click Environment Variables.
  4. Edit both TEMP and TMP user variables to point to D:\TEMP.
  5. Restart your system and run the Adobe installer.

Required Resource Allocation

  • System Drive Overhead: Minimum 20 GB of free, unallocated space on the OS partition regardless of where applications are installed.
  • Privileges: Local Administrator rights to delete protected system temp files and modify environment variables.
  • File System Type: NTFS (Windows) or APFS (macOS) with journaled permissions.

Final Render

Cleaning out hidden system temp caches releases the working space needed to resolve Error 120. Maintaining a consistent buffer of free space on your system drive ensures that Adobe installation routines extract and deploy without hitting disk limits.