Why does Intune show error 0xC7D24FBA when installing an Android app, and how can we fix it?

Question

Why does Intune show error 0xC7D24FBA when installing an Android app, and how can we fix it?

Aravindh Kanagaraj (EPS) 0

An Android app deployed through Intune and Managed Google Play fails to install on some Samsung devices, including devices running Android 16. Intune reports:

0xC7D24FBA — The application failed to install, possibly due to insufficient storage space or an unreliable network connection. The installation will be retried automatically.

The app was previously installed on some affected devices but is no longer present. An administrator attempted to reinstall it remotely, but installation failed. The devices have sufficient free storage, and the issue persists across multiple networks, including Wi-Fi.

What could cause this error when storage and internet connectivity appear to be working, and how can we identify and fix the underlying issue?

0 comments

1 answer

Your answer

Answer 1

Intune does not document 0xC7D24FBA as a Samsung or Android 16–specific failure, so use the affected device’s Managed Apps details and Intune client logs to identify the underlying Google Play or Android package-installer failure before changing the deployment.

The similar documented code 0xC7D14FBA—note 14, not 24—means an APK was deleted after download and applies only to legacy Device Administrator enrollment. It should not be assumed to explain this Managed Google Play failure.^1^

1. Capture the per-device installation details

In the Microsoft Intune admin center, open Troubleshoot + support.
Select the affected user, then select the Samsung device.
Open Managed Apps and select the failed application.
Capture the error details, resolved assignment intent, timestamps, and application version when present.
Initiate a device Sync, then reproduce the installation once.

Managed Google Play applications should be investigated under Managed Apps, not Discovered Apps.^2^ ^3^

As an optional early check, an administrator can open Microsoft 365 admin center → Show all → Support → Help & support, describe the app deployment problem, enter the affected user, and run the Intune app deployment diagnostic. It reports detected configuration issues but does not modify the tenant.^2^

2. Reproduce with client logging enabled

Verbose Company Portal logging records more detail and is enabled by default. On a work-profile device, verify it under badged Company Portal → Settings → Troubleshooting → Verbose Logging.^4^

After reproducing the failure, upload the appropriate client logs:

Personally owned or corporate-owned work profile: open the badged Company Portal → Menu → Help → Send logs → Send logs, then email.
Fully managed device using Microsoft Intune: open Microsoft Intune → Menu → Help → Get Support → Upload Logs, then select Email.
Record the generated incident ID.

These logs may contain additional diagnostic details, but Microsoft Support may need to correlate them with Google Play or Android installer events; uploading them does not guarantee that the administrator can directly read a native installer error.^5^

3. Apply the fix indicated by the evidence

Use the Managed Apps details or logs to choose the matching branch:

Managed Google Play synchronization or entitlement: Verify that the Intune tenant remains connected to Managed Google Play and that the app is still approved and assigned. To resynchronize an approved app, go to Apps → All apps → Create → Managed Google Play app, select the app in the embedded store, choose Select, and then Sync. Refresh the app list afterward.^6^
Signing-certificate mismatch: If the evidence shows an existing or residual package signed with a different certificate, Android cannot upgrade it. Confirm that the new release uses the original signing certificate. Otherwise, uninstall the old package and redeploy the new one.^1^
Warning: Uninstalling can erase local application data, settings, or unsynchronized work. Back up or synchronize business data and test on a non-production device first.
Device incompatibility: If Google Play reports the app as unavailable or incompatible only on the affected model/OS version, have the publisher inspect the app’s Android API requirements, architecture/native libraries, and manifest hardware requirements. Do not infer incompatibility solely from 0xC7D24FBA.
Duplicate deployment channels: Check whether the same package is assigned both as a Managed Google Play app and as a directly uploaded Android LOB app. Direct LOB deployment takes precedence, and mixed deployment channels can produce inconsistent status reporting. Temporarily eliminate the duplicate channel during diagnosis.^6^
Google Play client-state error: If logs point to Play Store cache or stored-data problems, on the device open Settings → Apps → Google Play Store → Force stop → Storage → Clear cache. Repeat for Google Play services, then retry. If unresolved, clear Google Play Store data as the next step; this resets its local stored state.^7^

If the same app/version fails only on Samsung Android 16 after synchronization, assignment, signing, and Play client state have been ruled out, submit the incident ID, affected models, OS builds, app package/version, enrollment mode, and failure timestamps to Microsoft Support. The available documentation does not establish this code as a confirmed Samsung Android 16 known issue.

References