Android 'Package Installer Has Stopped' – Fix It for Good

Android's Package Installer crashes when you try to install or update an app. Here's why it happens and the steps to fix it, from clearing cache to resetting app preferences.

You're mid-way through installing a new app from the Play Store, or maybe you're sideloading an APK from a trusted source. Suddenly, a pop-up appears: “Package Installer has stopped”. The installation dies. Sometimes the whole screen goes gray. If you tap the app icon again, it might work once or twice, then crash again. It's infuriating, especially when you're trying to get something done.

This error usually shows up on Samsung Galaxy phones and other Android devices after a system update, a new version of Google Play Services, or when you've been fiddling with default app settings. It's not a full-blown phone failure—it's just that the system component that handles app installations has tripped over its own cache or gotten tangled with another app's permissions.

Root Cause

Android's Package Installer is the behind-the-scenes tool that actually installs APK files onto your device. When it crashes, it's almost always because its cached data is corrupted or because its permissions have been revoked or misaligned. Think of it like a kitchen blender with a clogged blade—the motor's fine, but it can't process the ingredients until you clean it out.

Common triggers include a recent system update that changed how apps request permissions, or using a third-party “installer” app that overrides the system one. Also, if you've ever used an app like “App Manager” to disable system apps, you might have accidentally disabled the wrong component. But the fix is straightforward and doesn't require a factory reset.

The Fix: Step-by-Step

Try these steps in order. Most people only need step 1. If not, keep going—step 4 is the heavy hammer.

Step 1: Clear Cache and Data for Package Installer

Head to SettingsApps (or Application Manager). Then tap the three-dot menu and choose Show system apps – you need to see hidden ones.

  1. Scroll down and tap Package Installer (sometimes labeled “Package Installer” or “com.google.android.packageinstaller”).
  2. Tap Storage.
  3. Tap Clear Data and then Clear Cache.
  4. Go back and try your app installation again.

This wipes out any corrupted temporary files. It's like restarting that blender—works 80% of the time.

Step 2: Uninstall Updates for Play Store

If the error persists, the problem might be in the Play Store app itself. Go back to SettingsApps, find Google Play Store, tap the three-dot menu, and select Uninstall updates. This reverts the Play Store to its factory version, which often fixes the conflict.

Don't worry—when you open the Play Store again, it'll automatically update itself to the latest version.

Step 3: Check for Disabled or Conflicting Apps

Sometimes the culprit is an app that hijacks the install process. Go to SettingsApps, and look for anything like “Installation Manager” or “Package Manager.” If they're disabled, enable them. Also, if you have any “downloader” apps or APK installers from unknown sources, consider uninstalling them—they're not needed and often cause conflicts.

Step 4: Reset App Preferences

This step resets all default app settings and permission restrictions for every app, but it doesn't delete any personal data. Go to SettingsAppsReset app preferences (you'll find it under the three-dot menu or at the bottom). Confirm the action and then try your install again.

This is the nuclear-but-safe option. It clears any overridden permissions that might be blocking the Package Installer.

Step 5: Clear Play Services Cache

Google Play Services is the backbone that connects apps to Google's servers. If its data is stale, it can mess with installations. Go to SettingsAppsGoogle Play ServicesStorage, then tap Manage StorageClear All Data. Note that this will sign you out of some Google apps temporarily, but it's worth it for a clean slate.

Still Failing? Check These

  • Check your available storage – If you're under 500MB, the Package Installer might fail due to space. Clear some old photos or apps.
  • Disable 'Unknown Sources' temporarily – For sideloaded APKs, toggle Install unknown apps off for the browser you're using, then on again. This resets the permission.
  • Check for a system update – If you're on a dated version of Android (like 10 on a phone that supports 12), an update might fix a known bug. Go to SettingsSystemSoftware update.
  • Boot into Safe Mode – If the error only happens after you install a specific app, safe mode will tell you. Press and hold the power button, then long-press “Power off” to reboot into Safe Mode. If the Package Installer works fine there, a third-party app is the culprit. Uninstall your most recently installed apps.

I've seen this error pop up after a routine Samsung One UI update on a Galaxy S21, and the cache clear alone did the trick. If you've tried every step above and the crash still happens, it might be time to back up your data and do a factory reset–but that's rare. The steps above handle 95% of cases.

Pro tip: If you're sideloading APKs, always use the system's built-in installer rather than third-party apps like APK Installer. The less interference, the better.

You've got this. Most people fix it in under five minutes with step 1. If you hit a snag, drop me a comment below and I'll help you troubleshoot further.

Related Errors in Mobile – Android
App not installed Android 'App Not Installed' Fix: The Real Reasons & Fixes 963 Google Play Store error 963 fix for Android Google Play Services has stopped Fix Android 'Unfortunately, Google Play Services Has Stopped' for Good Android 'Unfortunately, [App] Has Stopped' – Real Fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.