How to Fix “INSTALL_FAILED_USER_RESTRICTED” in Android Studio

Installation failed with message INSTALL_FAILED_USER_RESTRICTED

What Does INSTALL_FAILED_USER_RESTRICTED Mean?

INSTALL_FAILED_USER_RESTRICTED does not usually indicate that the APK itself is broken.

Instead, Android is refusing the installation because the current user or device policy does not permit the requested application installation.

ADB may display an error such as:

adb: failed to install app-debug.apk: Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user]

On other devices, the message may simply be:

Failure [INSTALL_FAILED_USER_RESTRICTED]

Even if the message says “Install canceled by user,” it does not always mean that you manually pressed a Cancel button. Device security software or a user restriction may have rejected the request automatically.

Common Causes

1. Installation Over USB Is Disabled

This is one of the most common causes.

Some Android devices allow ADB debugging but separately restrict APK installation through USB.

As a result, adb devices can report the device normally while APK installation still fails.

2. The Installation Confirmation Was Rejected

Some devices display a confirmation dialog when ADB attempts to install an application.

If you reject that dialog or do not respond before it disappears, the installation may return INSTALL_FAILED_USER_RESTRICTED.

3. Xiaomi, Redmi, or POCO Security Settings

Some Xiaomi-based devices include additional developer security options beyond normal USB debugging.

Depending on the device and OS version, relevant options may include:

• USB debugging
• Install via USB
• USB debugging (Security settings)

If the necessary settings are disabled, Android Studio may recognize the device but fail when it tries to install the APK.

4. The Device Is Managed by a Company or School

Mobile Device Management policies can prohibit application installation, sideloading, ADB installation, or developer settings.

These restrictions may not be removable by the device user.

5. A Work Profile or Secondary User Is Restricted

Android supports multiple users and managed Work Profiles.

The current user may have different application-installation permissions from the owner user.

6. Parental Controls or a Restricted User Are Enabled

Family controls and restricted-user environments can prevent users from installing new applications.

7. The Device Screen Is Locked

Some devices require a user confirmation during ADB installation.

If the device is locked, you may not see or be able to approve the request.

Solution 1: Check the Device Screen

After pressing Run in Android Studio, immediately check the physical Android device.

You may see a confirmation similar to:

Install this application via USB?

Cancel
Install

Approve the installation if you trust the APK and development computer.

Solution 2: Enable USB Debugging

Open Developer options on the Android device and verify that USB debugging is enabled.

A typical procedure is:

1. Open Android Settings.
2. Open About phone or Device information.
3. Tap the build number several times to enable Developer options.
4. Open Developer options.
5. Enable USB debugging.

Reconnect the USB cable and try running the application again.

Solution 3: Enable Install via USB

Some manufacturers provide a separate option for installing applications over USB.

Look in Developer options for a setting such as:

Install via USB

If the option exists, enable it and retry the installation.

Solution 4: Check Xiaomi-Specific Developer Options

On Xiaomi, Redmi, and POCO devices, inspect Developer options for additional USB security settings.

Depending on the software version, you may find options such as:

USB debugging Install via USB USB debugging (Security settings)

Enable the settings required by the device, reconnect USB, and try Android Studio again.

Some MIUI or HyperOS versions may require additional account or network conditions before certain security options can be enabled.

Solution 5: Restart the ADB Connection

After changing device settings, restart ADB:

adb kill-server adb start-server

Then verify the connection:

adb devices

A normal connection looks similar to:

List of devices attached ABC123456 device

Then retry the APK installation:

adb install app-debug.apk

Solution 6: Reauthorize USB Debugging

If the device’s USB debugging authorization is in an unusual state, revoke existing USB debugging authorizations from Developer options.

Reconnect the development computer afterward.

The device should display a prompt similar to:

Allow USB debugging?

Approve the computer if you recognize and trust it.

You may also select the option to always allow debugging from that computer.

Solution 7: Check the Current Android User

On a multi-user Android device, check the active user:

adb shell am get-current-user

You can list users with:

adb shell pm list users

Example:

Users: UserInfo{0:Owner:...} running UserInfo{10:Work:...}

If the device has a Work Profile or additional users, determine whether the target user is subject to application-installation restrictions.

Solution 8: Inspect User Restrictions

You can inspect user-related system information with:

adb shell dumpsys user

Review the output for restrictions related to installing applications.

Solution 9: Check the Work Profile

A managed Work Profile may have stricter application installation rules than the personal profile.

Corporate policy can disable sideloading or ADB-based installation into the managed environment.

For development testing, use a personal profile or dedicated development device where permitted.

Solution 10: Contact the Device Administrator

If the Android device is managed by a company or school, the administrator may have configured policies such as:

• Blocking unknown application sources
• Blocking ADB installation
• Disabling Developer options
• Restricting applications in a Work Profile
• Allowing only approved applications

In this situation, the administrator must change the policy if development installation is required.

Solution 11: Check the USB Cable and USB Mode

A bad USB connection is not usually the direct meaning of USER_RESTRICTED, but an unstable connection can interfere with authorization and confirmation workflows.

Try the following:

• Use a USB cable that supports data transfer.
• Try a different USB port.
• Connect directly instead of through a USB hub.
• Try File Transfer mode on the device.
• Disconnect and reconnect the USB cable.

Solution 12: Restart the Device

If you changed Developer options but the installation behavior did not change, restart the Android device.

Then restart ADB:

adb kill-server adb start-server adb devices

Run the application from Android Studio again.

Can This Happen on an Android Emulator?

INSTALL_FAILED_USER_RESTRICTED is especially common with manufacturer security settings on physical devices, but user restrictions can theoretically affect other Android environments as well.

If it happens on a normal Android Studio AVD, try:

• Restarting the Emulator.
• Using Wipe Data.
• Creating a new AVD.
• Checking whether you configured multiple users or unusual device policies.

If the Error Says “Install canceled by user”

You may see:

Failure [INSTALL_FAILED_USER_RESTRICTED: Install canceled by user]

Check the physical device first.

This message can appear after you reject an installation dialog, but similar behavior can also occur when the device security system refuses USB installation.

On manufacturer-customized Android versions, check installation-over-USB settings in addition to ordinary USB debugging.

If USB Debugging Is Enabled but Installation Still Fails

A common situation looks like this:

adb devices → device

Android Studio
→ device detected

Run
→ INSTALL_FAILED_USER_RESTRICTED

In this situation, the USB debugging connection itself is working.

The problem is more likely to be permission to install APKs through that connection.

Check these items in order:

1. The installation confirmation on the device.
2. Install via USB settings.
3. Manufacturer-specific USB security settings.
4. Work Profile and device-management restrictions.

Use ADB Directly to Isolate the Problem

If Android Studio reports the error, try installing the APK directly:

adb install app-debug.apk

If the same error appears:

Failure [INSTALL_FAILED_USER_RESTRICTED]

the issue is likely related to the device installation policy rather than Android Studio itself.

If the Error Still Occurs

If INSTALL_FAILED_USER_RESTRICTED continues, verify the following:

• Check for an installation confirmation dialog on the device.
• Make sure USB debugging is enabled.
• Enable Install via USB if your device provides that option.
• Check manufacturer-specific USB security settings.
• Reauthorize USB debugging.
• Check restrictions on the active Android user.
• Check whether a Work Profile is managed.
• Check company or school MDM policies.
• Check parental controls or restricted-user settings.
• Restart both the device and ADB.

Summary

The Android Studio INSTALL_FAILED_USER_RESTRICTED error usually means that the Android device is refusing the ADB installation because of a user restriction or device security policy.

Start by checking the physical device immediately after pressing Run in Android Studio.

Then inspect Developer options for settings such as:

USB debugging Install via USB Manufacturer-specific USB security settings

A practical troubleshooting order is:

1. Approve the installation confirmation on the device.
2. Verify USB debugging.
3. Check Install via USB.
4. Reauthorize the development computer.
5. Restart ADB.
6. Check Android users and Work Profiles.
7. Check device-management restrictions.
8. Use another development device if the policy cannot be changed.

If adb devices already shows the device normally but Android Studio still cannot install the app, focus on device-side installation permissions rather than basic USB connectivity.