What the INSTALL_FAILED_UNKNOWN_SOURCES Error Means
The INSTALL_FAILED_UNKNOWN_SOURCES error (sometimes displayed as -26) occurs when attempting to install an APK file if the Android system blocks the process due to missing permission to install apps from "unknown sources"—that is, sources other than the Google Play Store.
A typical scenario: you downloaded an APK file in your browser or file manager, tapped on it, and instead of installing, you see a "App not installed" notification with an error code. The system protects you from potentially malicious software by requiring explicit consent for sideloading.
Causes
- Global permission disabled. In your security settings, the "Unknown sources" option (on Android 7.1 and lower) or "Allow installation of apps from unknown sources" (Android 8.0+) is turned off.
- No permission for the specific source. On Android 8.0 and higher, permission must be granted not globally, but per app (browser, file manager) from which the installation is initiated.
- Installation via an unsupported context. The system does not recognize the installation source (e.g., trying to install via a third-party launcher or receiving an APK via Bluetooth).
- Corporate policies or parental controls. A device owner profile or parental control app is active on the device and prohibits sideloading.
- APK integrity issues. The file is corrupted or signed with an inconsistent key, but the system mistakenly interprets this as a sources issue (less common).
Method 1: Enabling Global Permission (Android 7.1 and Lower)
- Open Settings → Security (on some firmware: Apps & notifications → Special access).
- Find the "Unknown sources" or "Allow installation of apps from unknown sources" option.
- Toggle it on.
- Confirm the action in the warning that appears.
⚠️ Important: On Android 8.0 (API 26) and higher, this method will not work. The system requires permission to be granted to each source individually.
Method 2: Permission for a Specific App Source (Android 8.0+)
- Go to Settings → Apps & notifications → Special access (or Additional features → Special access).
- Select "Install unknown apps" (or "Allow app installs").
- In the app list, find the app you use to download APKs (e.g., Chrome, Firefox, File Manager).
- Tap on it and enable "Allow from this source".
Method 3: Installation via ADB (for Developers and Advanced Users)
This method bypasses system checks if USB debugging is enabled on the device.
- Install Android SDK Platform-Tools on your computer.
- On the device, enable Developer options (tap "Build number" 7 times in "About phone") and activate USB debugging.
- Connect the device to the PC via USB and allow debugging (a dialog will appear on the phone).
- Open a terminal (command prompt) and run:
adb devices
Ensure your device appears in the list.
- Install the APK file:
adb install path/to/your_app.apk
If the app has a low targetSdkVersion (below 26), you may need:
adb install --bypass-low-target-sdk-block path/to/your_app.apk
Method 4: For Rooted Devices — Modifying System Settings
If you have root access, you can change system settings directly.
Global permission via settings:
su
settings put global install_non_market_apps 1
Permission for a specific package via appops:
su
appops set com.android.chrome REQUEST_INSTALL_PACKAGES allow
Replace com.android.chrome with your source's package name (e.g., com.miui.filemanager for the Xiaomi file manager).
💡 Tip: Reboot your device after making root changes. These settings may reset after a system update.
Prevention
- Verify APK sources. Download apps only from official websites or trusted repositories (F-Droid).
- Don't leave permission enabled permanently. After installing the needed app, turn off "Unknown sources" for better security.
- Use Google Play Protect. Even after a sideload install, run a scan in the Google Play Store → "Play Protect".
- Update your system. On newer Android versions (10+), permissions are managed more strictly, which reduces risks but requires more steps for installing from third-party sources.
FAQ
Q: What if security settings are unavailable (grayed out)? A: A work or school profile (Device Owner) might be active on the device. You'll need to remove the profile in the "Accounts" settings or contact your administrator.
Q: Why does the error persist after enabling the permission? A: Reboot your device. On some firmware (e.g., older Samsung TouchWiz), the change only takes effect after a restart.
Q: Can I temporarily allow installation without changing settings? A: No. The system requires explicit consent. However, the ADB method (Method 3) allows installation without modifying system settings if USB debugging is already active.
Q: Is this error related to the 'App not installed' issue?
A: Partially. Both errors block installation, but INSTALL_FAILED_UNKNOWN_SOURCES specifically prohibits sideloading, whereas App not installed can be caused by signature conflicts, insufficient storage, or APK corruption.