Android 'App Not Installed' Error – Fix in 2 Minutes

You go to install an app – maybe an update, maybe something from the Play Store – and Android just says "App not installed." No reason, no error code. Just a brick wall. I've seen this hundreds of times in my help desk. The fix is almost always the same, and it takes about two minutes.

The real fix: Clear the Package Installer cache

Android's package installer is the system app that handles all app installations. When its cache gets corrupted – which happens after a failed install, a storage glitch, or just time – it stops working. Here's how to fix it step by step.

1. Open Settings on your phone. Swipe down from the top and tap the gear icon, or find the Settings app in your app drawer.
2. Go to Apps (or Apps & notifications on some phones).
3. Tap See all apps to show every app on the device – not just the ones you installed.
4. Tap the three-dot menu (upper right corner) and select Show system apps. This is the step people miss. Without it, you won't see the package installer.
5. Scroll down until you find Package Installer (it might also be called Package Installer Helper on some Samsung phones). Tap it.
6. Tap Storage (or Storage & cache).
7. Tap Clear cache. Do not tap Clear storage – that resets everything and can cause side effects. Just clear the cache.
8. Go back to the main Settings screen, then force stop the Package Installer app. You'll find the Force stop button on the same app info page, just above the Storage section.
9. Try installing the app again. Go back to the Play Store or your downloaded APK file and install normally.

After you clear that cache, you should see the installation proceed past the point where it used to fail. I've fixed this on Pixel 7s, Galaxy S23s, and Motorola G-series phones. It works.

Why clearing the cache works

The package installer cache holds temporary data from previous installations – things like file signatures, permissions from old installs, and metadata. When that cache gets corrupted, the installer sees conflicting info and gives up. Clearing the cache forces Android to rebuild that data fresh from the app file you're trying to install. No more conflict, no more error.

Think of it like a scratch pad. If the scratch pad has old, smudged notes from a week ago, the installer gets confused. You're just handing it a clean page.

Less common variations of this issue

Sometimes clearing the cache alone doesn't cut it. Here are a few other things I've seen cause the same error, and what to do about them.

Storage almost full

If your phone has less than 500 MB of free space, Android can refuse to install apps even if the app file is small. The installer needs room to unpack and verify the app. Check your storage in Settings > Storage. If it's under 1 GB, clear out old photos, uninstall unused apps, or move files to a cloud service. Then try again.

Corrupted APK file

If you're sideloading an app from a website (not the Play Store), the download might have been interrupted or corrupted. Delete the APK file, re-download it from the original source, and try installing again. I always recommend checking the file size against what the site says it should be – a mismatch means a bad download.

Play Store cache is also worth clearing

For apps from the Play Store, a corrupted Play Store cache can sometimes trigger the same error. Go to Settings > Apps > Show system apps > Google Play Store > Storage > Clear cache. Don't clear data unless you're desperate – it logs you out. After that, restart the Play Store and try installing.

App not compatible with your Android version

Rare but real. If the app requires Android 12 or later and you're on Android 10, the installer will quietly fail. Check the app's requirements on the Play Store page or the developer's website. The error message won't tell you this, but it's a hard stop for the installer.

Security software blocking the install

Some third-party antivirus apps or device administrators can block installation of apps they don't recognize. Temporarily disable any security app you have, try the install, and re-enable it after. I've seen this most often with McAfee and Norton on Samsung phones.

How to prevent this from happening again

You can't stop the package installer cache from ever getting corrupted – that's just how software works. But you can reduce how often it happens.

• Keep 1-2 GB of free storage on your phone at all times. Low storage is the number one trigger for install failures.
• Clear the Play Store cache once a month, whether you're having problems or not. It takes 10 seconds and prevents a lot of weirdness.
• Never force-close the Package Installer during an installation. Let it finish, even if it takes a while. Interrupting it corrupts the cache almost every time.
• Download APKs only from trusted sources. APKMirror and the developer's own site are safe. Random file-sharing sites are not.

That's it. Clear that cache, and you're back in business. If for some reason the error still happens after all this, you might be looking at a hardware issue – a dying storage chip – but that's extremely rare. For the other 99% of cases, this fix works.