Fix: Command Line Tools Not Available from Software Update on macOS

Fix: Command Line Tools Not Available from Software Update on macOS

Written by

in

Quick answer: To fix the Can't install the software because it is not currently available from the Software Update server error, sign in to Apple’s More Downloads portal (developer.apple.com/download/all/) with a free Apple Account and install the Command Line Tools .dmg manually. Alternatively, delete a stale /Library/Developer/CommandLineTools directory or trigger an on-demand catalog scan with softwareupdate in Terminal.

Why this happens

When you run xcode-select --install in Terminal—often while setting up Homebrew, MacPorts, Git, or Python build dependencies after a macOS upgrade—macOS opens a GUI prompt that asks Apple’s Software Update catalog for a matching Command Line Tools package. If the lookup fails, macOS stops with:

Can't install the software because it is not currently available from the Software Update server.

This error rarely means Apple took the servers offline, which is why one Mac can install the tools normally while another Mac on the same network fails. Instead, the local Software Update client could not match your exact macOS build to an eligible Command Line Tools entry in its active catalog.

That mismatch happens for four common reasons:

  • An older or discontinued macOS release: Apple periodically removes older Command Line Tools builds from the live Software Update feed while keeping their standalone installers on the developer portal.
  • A newly released or beta macOS build: Right after a major macOS update or on a beta seed, the on-demand Software Update catalog may not yet advertise a Command Line Tools package for your build number.
  • Leftover files from a previous macOS upgrade: Upgrading macOS in place frequently leaves partial receipts or an outdated /Library/Developer/CommandLineTools folder behind, confusing the installer check.
  • Cached or MDM-overridden update catalogs: Corporate MDM profiles or stale local Software Update caches can point your Mac at an internal or outdated catalog that lacks developer packages.

How to fix it

1. Download Command Line Tools manually from Apple Developer (most reliable)

Bypassing Software Update completely is the fastest way around catalog mismatches, especially on older macOS versions, brand-new releases, or beta builds. You do not need a paid Apple Developer Program membership—any free Apple Account works.

  1. Open Apple’s More Downloads page in your browser: https://developer.apple.com/download/all/ (older links such as developer.apple.com/download/more/ redirect here).
  2. Sign in with your Apple Account and complete two-factor authentication if prompted.
  3. In the search field on the left, type Command Line Tools.
  4. Find the Command Line Tools for Xcode version compatible with your macOS release. If you are unsure which macOS version you are running, check Apple menu > About This Mac or run sw_vers in Terminal.
  5. Download the .dmg file, open it, and double-click the .pkg installer inside to complete setup.

Once the installer finishes, verify that xcode-select points to the newly installed tools and that the package receipt is registered:

xcode-select -p
# Expected output: /Library/Developer/CommandLineTools

pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
clang --version

2. Remove a broken Command Line Tools directory and retry

After an in-place macOS upgrade, /Library/Developer/CommandLineTools often contains incomplete binaries from your previous OS version. Clearing that directory forces xcode-select to request a clean installation.

First, check what active developer directory your Mac is currently using:

xcode-select -p

Remove the existing Command Line Tools directory and reset xcode-select:

sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --reset
xcode-select --install

When the installation dialog appears, click Install and let the download finish. Confirm the installation succeeded by running git --version or clang --version.

3. Force an on-demand catalog lookup with softwareupdate

The GUI wrapper launched by xcode-select --install can fail even when the softwareupdate command-line tool can still see the package. You can expose Command Line Tools to softwareupdate directly by creating the temporary placeholder file macOS uses to flag an on-demand developer tools request. (This is the same mechanism automated package managers like Homebrew use on headless Macs.)

  1. Create the temporary sentinel file:
touch /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
  1. List available updates and filter for Command Line Tools:
softwareupdate -l
  1. Look for a Label: line in the output, such as Label: Command Line Tools for Xcode-16.2 (your version number will match your OS). Copy the exact text after Label: and install it:
sudo softwareupdate -i "Command Line Tools for Xcode-16.2" --verbose
  1. Remove the temporary placeholder file so Software Update stops polling for on-demand developer packages on every check:
rm /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress

If softwareupdate -l still returns No new software available, your macOS version genuinely does not have a package in the live Software Update feed—go back to Step 1 and use the manual .dmg installer.

4. Point xcode-select to full Xcode if you already have it installed

If the full Xcode.app bundle is already installed in /Applications, you already have compilers, SDKs, Git, and build utilities on disk. Many command-line tools do not require the standalone /Library/Developer/CommandLineTools package as long as xcode-select points inside Xcode.app.

Switch the active developer directory to Xcode and accept the license:

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -license accept

Verify that command-line utilities resolve cleanly:

xcrun --find clang
xcodebuild -version

Note that a few third-party package managers (including certain Homebrew formulas and MacPorts configurations) specifically look for SDK headers inside /Library/Developer/CommandLineTools/SDKs. If a build script explicitly asks for standalone Command Line Tools despite having full Xcode installed, install the .dmg from Step 1.

5. Check for custom Software Update catalogs on managed Macs

If your Mac is enrolled in corporate MDM (such as Jamf, Kandji, or Mosyle), an administrator profile may redirect softwareupdate to an internal caching or update server that blocks or omits developer packages.

Check whether a custom catalog URL is active:

defaults read /Library/Preferences/com.apple.SoftwareUpdate CatalogURL

If that command prints a custom internal URL instead of does not exist, your Mac is not talking directly to Apple’s default Software Update feed. On an unmanaged Mac where an old override was left behind, you can reset the preferences key; on a company-managed Mac, install the standalone .dmg from Apple’s developer portal in Step 1 instead.

How to prevent it

  • Reinstall Command Line Tools immediately after major macOS upgrades: Every major macOS upgrade invalidates or partially removes /Library/Developer/CommandLineTools. Plan to run xcode-select --install (or install the matching .dmg) before updating Homebrew or MacPorts.
  • Keep a copy of the .dmg for older build machines: If you maintain CI runners or test Macs pinned to an older macOS version, archive the matching Command Line Tools .dmg from developer.apple.com/download/all/ so you are never blocked when Apple prunes its live Software Update catalog.
  • Clean up temporary sentinel files in CI scripts: If your provisioning scripts create /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress, always remove it in a trap or cleanup step so background update checks stay clean.
  • Wait or grab beta tools when testing macOS betas: When running a macOS developer beta, always download the matching beta Command Line Tools directly from the Apple Developer portal rather than relying on xcode-select --install.

FAQ

Do I need a paid Apple Developer account to download Command Line Tools manually?

No. Signing in to developer.apple.com/download/all/ with a standard, free Apple Account gives you access to release builds of Command Line Tools for Xcode, including archived installers for older macOS releases.

Why did xcode-select --install work on one Mac running the same macOS version, but fail on another?

Upgraded Macs often retain broken package receipts, cached Software Update plist state, or a leftover /Library/Developer/CommandLineTools folder from an earlier OS. Deleting /Library/Developer/CommandLineTools or installing the standalone .dmg bypasses that local state difference.

Do I need both Xcode and standalone Command Line Tools installed?

Not always—full Xcode.app bundles its own toolchain at /Applications/Xcode.app/Contents/Developer. However, tools like Homebrew and MacPorts often expect unversioned macOS SDK paths under /Library/Developer/CommandLineTools, so installing both is safe and avoids build-script path issues.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.