You clicked install twenty minutes ago. The progress bar hasn’t moved. You can’t quit the app, you can’t shut down your Mac, and you’re starting to wonder if you just broke something. You didn’t — this happens to a lot of Mac users, and it’s almost never as serious as it feels in the moment.
An app installation stuck Mac when macOS can’t complete a background process — usually because of a security check, low storage, a dropped connection, or a frozen system service. In most cases you can force quit the installer, verify storage and network, then retry. If macOS blocks the app entirely with a “damaged” warning, that’s a Gatekeeper issue, not a broken file.
What “Install in Progress” Really Means on Mac
“Install in Progress” isn’t a specific app. It’s a generic system message macOS shows whenever it’s writing files, checking signatures, or finishing setup for a piece of software — whether that’s a Mac App Store update, a .pkg installer, or a macOS system update itself.
Under the hood, several things happen during any install: the file gets copied into place, macOS verifies its code signature through Gatekeeper, and (for App Store apps) the system checks in with Apple’s servers to confirm licensing. Any one of those steps can hang if something upstream — your network, your disk, or a background process — isn’t cooperating.
That’s also why interrupting an install mid-process is risky. If your Mac warns you that shutting down “may damage your computer,” it means it. The safer move is almost always to force quit the specific process, not to power off the machine.
Is App Installation Stuck Mac, or Just Slow?
Before troubleshooting, rule out the obvious: it might just be slow. A large app — think Photoshop, Xcode, or a big game — genuinely can take ten or fifteen minutes on an older Mac, especially one with a slower CPU or a nearly full drive.
A few signs it’s genuinely stuck rather than just working:
- The progress bar hasn’t moved at all in more than 10–15 minutes
- Activity Monitor shows the installer process using close to 0% CPU
- You’ve tried to shut down and gotten the “software is being installed” warning, and it’s been showing for well over an hour
- The percentage is frozen at an oddly specific number, like 6% or 42%, and hasn’t changed after a full restart attempt
If you’re seeing any of those, move on to the fixes below in order — they’re arranged from safest and quickest to more involved.
Fix 1 — Force Quit the Stuck Installation
This is the first thing to try, and it resolves the majority of stuck installs.
- Open Activity Monitor (Spotlight: Command + Space, then type “Activity Monitor”).
- In the search field, type the name of the app or “install” to find the relevant process — this is often named
installd,Installer, or the app’s own name. - Select the process and click the X button in the toolbar, then choose Force Quit.
- Give it a minute — force-quitting doesn’t always clear the “Install in Progress” dialog instantly.
If Activity Monitor itself is unresponsive, open Terminal (Applications > Utilities > Terminal) and run:
sudo pkill -9 installdThis is more forceful and works when the GUI is frozen too. It’s safe on a genuinely stuck installer — it just won’t do anything harmful if the install was actually fine, though you may need to retry the install afterward.
Quick takeaway: Force quitting an installer that’s actually stuck won’t damage your Mac. It’s designed to be interrupted safely at this level; the warning about damage refers to yanking power mid-write, not to quitting the process.
Fix 2 — Restart Your Mac the Right Way
If force quitting doesn’t clear things up, restart. Go to the Apple menu > Restart. If the menu itself won’t respond because of the stuck install, hold the power button until the Mac shuts down, wait about 10 seconds, then power it back on.
This clears out any hung background processes tied to the installer and gives the App Store or installer a clean slate to retry. It’s a blunt fix, but it’s genuinely effective — most “install in progress” freezes trace back to a background service that just needs to be reset, not a deeper fault.
Fix 3 — Check and Free Up Storage Space
Installers need working room beyond the final app size — often double the app’s size temporarily, since macOS downloads the package, then unpacks and writes it. If your drive is nearly full, the install can silently stall rather than failing outright with an error.
To check: Apple menu > System Settings > General > Storage. If you’re under about 15–20 GB free, that’s tight enough to cause problems for larger installs.
Fastest ways to free up space:
- Empty the Trash (right-click Trash > Empty Trash)
- Delete old installer .dmg or .pkg files sitting in Downloads
- Use the built-in Storage recommendations to offload unused files
- Check System Settings > General > Storage > Applications to spot large apps you don’t use
Fix 4 — Check Your Internet Connection and DNS
App Store downloads and many .pkg installers phone home during setup, even after the file itself has downloaded — to verify licensing or check for a newer build. A flaky connection can leave the process technically “running” while it waits on a request that will never come back.
Try a different network if you can, or restart your router. If your connection seems fine but the store still won’t respond, clear your DNS cache in Terminal:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderEnter your admin password when prompted. Then retry the install.
Fix 5 — Sign Out and Back Into the Mac App Store
This fixes a specific, common failure mode: the download request gets stuck in a loop where the App Store shows activity but nothing is actually transferring.
- Open the App Store.
- Click your name/account in the sidebar, or go to Store > Sign Out in the menu bar.
- Restart your Mac.
- Sign back in and retry the download.
If that doesn’t clear it, quitting the underlying App Store processes directly in Terminal can help:
sudo pkill storedownloadd storeaccountd mds_stores appstored appstoreagentFix 6 — Boot Into Safe Mode
Safe Mode loads only the essential system extensions and clears certain system caches automatically, which can dislodge whatever’s blocking a stuck installer without you needing to diagnose the exact cause.
On Apple silicon Macs: shut down completely, then press and hold the power button until “Loading startup options” appears, choose your startup disk, hold Shift, and click Continue in Safe Mode.
On Intel Macs: restart while holding Shift until the Apple logo appears.
Try the install again once you’re in Safe Mode, or simply restart normally afterward — sometimes the act of booting into Safe Mode and back is enough to reset whatever was hung.
Fix 7 — “App Is Damaged and Can’t Be Opened”: The Gatekeeper Problem
If the install itself finishes but you get a message saying the app “is damaged and can’t be opened, you should move it to the Trash” — that’s a different issue entirely, and it’s one most stuck-install guides skip even though it’s one of the most common real-world causes of an install that never fully completes.
Despite the alarming wording, this almost never means the file is actually corrupted. It means Gatekeeper — macOS’s built-in check for code signing and notarization — couldn’t verify the app, usually because:
- The app was downloaded from outside the App Store and isn’t notarized by Apple
- The download was interrupted, so the file’s signature doesn’t match what macOS expects
- You’re on a newer macOS version, like Sequoia or the newer Tahoe release, with stricter enforcement than the app was originally built against
First, try the supported path: right-click the app in Finder and choose Open, then confirm in the dialog. If there’s an Open Anyway option under System Settings > Privacy & Security, use that — it whitelists just that one app without touching your Mac’s overall security posture.
Fix 8 — Clear the Quarantine Flag With Terminal
If “Open Anyway” isn’t available, macOS has likely tagged the file with a quarantine attribute — a flag it applies to anything downloaded from the internet. You can remove it directly, which is safe as long as you trust the source of the app:
xattr -dr com.apple.quarantine /Applications/AppName.appReplace “AppName” with the actual app name. The -r flag applies this recursively across every file inside the app bundle, which matters — clearing it on just the top-level file often isn’t enough.
One caution worth taking seriously: only run this on software you downloaded yourself from a source you trust, like the developer’s official site or GitHub. This command is not a general-purpose fix for random files — it’s specifically for apps you already vouch for that Gatekeeper is being overly strict with. Never disable Gatekeeper system-wide (via sudo spctl --master-disable) as a routine fix; that removes protection for every app on your Mac, not just the one giving you trouble.
Fix 9 — Run Disk Utility First Aid
If installs are failing inconsistently across multiple different apps, the underlying disk could have a problem, not any individual installer.
- Open Disk Utility (Applications > Utilities).
- Select your startup disk, usually Macintosh HD.
- Click First Aid, then Run.
- Let it complete — this can take several minutes — and address any errors it reports.
If First Aid keeps reporting the same unresolved errors on repeat runs, that’s worth taking to Apple Support or a certified technician before it affects more than just app installs.
Fix 10 — Reinstall macOS (Last Resort)
If nothing above works and installs consistently hang across different apps and sources, a clean macOS reinstall resolves most deep system-level corruption. Reinstalling through Recovery Mode (hold the power button at startup, then choose Reinstall macOS) does not erase your files by default — it reinstalls the operating system over your existing data. Still, back up first via Time Machine before doing this; it’s the kind of step you want a safety net for regardless.
This should genuinely be your last option after Fixes 1 through 9, not a first response to one stuck install.
App Store Downloads vs. .pkg/.dmg Installers: Why They Get Stuck Differently
Not every stuck install has the same cause, and knowing which type you’re dealing with narrows down the fix fast.
| Mac App Store apps | .pkg / .dmg installers | |
|---|---|---|
| Common stuck cause | Account/licensing check loop, App Store cache | Corrupted or incomplete download, Gatekeeper signature check |
| Typical symptom | Progress bar frozen at a low percentage, “Waiting” status | Installer freezes partway through, or app opens to a “damaged” warning |
| Best first fix | Sign out/in of App Store (Fix 5) | Force quit the installer (Fix 1), then check Gatekeeper (Fix 7–8) |
| Where files download to | Handled internally by the App Store app | Usually sits in ~/Downloads until you drag it to Applications |
How to Prevent Stuck Installs Going Forward
A few habits meaningfully cut down how often this happens:
- Keep at least 20 GB of free storage as a working buffer, not just enough to fit the app itself
- Download installers only from the developer’s official site or the Mac App Store — third-party download aggregators sometimes repackage or corrupt installers
- Let macOS’s built-in Archive Utility handle unzipping .zip installers rather than a third-party unzip tool
- Keep macOS reasonably up to date, since major releases like Sequoia and Tahoe have changed Gatekeeper and permissions behavior in ways that can affect older installers
- If an install repeatedly hangs, check Console (Applications > Utilities > Console) and search for the app’s name around the time it froze — it often shows a specific error you can search for directly, rather than guessing
None of this needs to be complicated. Most stuck installs come down to one of a small handful of causes, and working through the fixes above in order will resolve the vast majority of them without ever needing a full reinstall.
NEED MORE ANSWERS? OUR FULL GUIDE HUB FOR MORE FREE SOFTWARE GUIDES.
FAQ Section
Q1: Why is my Mac app stuck on installing?
Most often it’s a hung background process, low storage space, or a network hiccup during a licensing check. Less commonly, it’s a Gatekeeper signature verification that’s blocking the app entirely rather than a literal freeze.
Q2: Is it safe to force quit a stuck Mac installation?
Yes, generally. Force quitting the installer process (not pulling the power) is the standard first step and won’t damage your Mac. What you should avoid is powering off abruptly while a progress bar is actively moving.
Q3: How long should a Mac app take to install?
Most apps finish in under a few minutes. Large software like Photoshop or Xcode can take 10–20 minutes on slower Macs. If there’s been zero progress for over 15 minutes, treat it as stuck.
Q4: Can I shut down my Mac during “Install in Progress”?
You shouldn’t force it. If macOS shows a warning that shutting down may damage your computer, force quit the installer process first, then shut down normally once it’s cleared.
Q5: Why does my Mac say an app is damaged and can’t be opened?
This is almost always Gatekeeper flagging an app that isn’t notarized, was downloaded incompletely, or wasn’t signed the way your macOS version expects — not an actually broken file. Try Open Anyway in Privacy & Security settings first.
Q6: How do I clear a stuck Mac App Store download?
Cancel the download, sign out of the App Store, restart your Mac, sign back in, and retry. If it’s still stuck, quit the App Store background processes through Terminal.
Q7: What does “Install in Progress” mean on Mac?
It’s a generic macOS system message shown whenever software is being written to disk and verified — it isn’t tied to one specific app and can appear for App Store downloads, .pkg installers, or macOS updates.
Q8: Does reinstalling macOS delete my files? No, a standard reinstall through Recovery Mode installs the OS over your existing data and keeps your files. It’s still smart to back up with Time Machine first as a precaution.
