How to Fix Google Play Store Error 975

By ErrorFix · Updated October 22, 2026 · 6 min read

What error 975 means

Error 975 is a Google Play Store error that stops an app from downloading or updating. The message reads “App could not be downloaded due to an error. (975)” — terse, unhelpful, and gone the moment you dismiss it. Retry the download and the same pop-up returns. Unlike well-known Play Store errors, 975 carries almost no community history: it is the rarest error code in the Play Store’s catalog, appearing in error lists as a footnote with the honest disclaimer that no remedy has been confirmed.

Because Google has never documented 975, there is no official explanation of what trips it. The pattern from the few reports that exist is that it behaves like a transient failure rather than a persistent device problem. People describe it striking suddenly on a phone where the Play Store worked fine hours earlier, sometimes during periods when Google’s own services were having a wobbly day. That points the finger at temporary glitches — a half-formed download record in the Download Manager, stale sync state in Google Play Services, or an account handshake that failed partway — rather than anything wrong with the phone, the app, or the account itself.

That diagnosis shapes the approach. There is no single targeted fix for 975 because there is no documented cause to target. Instead, the right move is the full Play Store repair sequence, run in order from least disruptive to most disruptive, ending with a direct report to Google. Every step below is safe, reversible, and deletes nothing you care about — and for the majority of people who hit this error, one of the middle steps clears it within half an hour.

Common causes

• Corrupted Play Store cache or data: broken temporary files in the store app poison its download flow — the most likely cause, since it produces the widest range of error codes.
• Wedged Download Manager record: the system component that fetches app files keeps a broken half-record of the download and fails the same way on every retry.
• Stale Google Play Services data: the background framework behind Play Store installs shares download state with the store, so corrupted state there can surface as obscure error codes like 975.
• Account connection glitch: a partially broken handshake between your phone and Google’s servers can block downloads even when everything on the phone looks healthy.
• Network interference: restrictive workplace, school, or captive-portal Wi-Fi can mangle Play Store traffic in ways that produce one-off error codes.

How to fix error 975 — step by step

Work through these fixes in order. Because 975 has no confirmed fix, run the whole sequence — most people are fixed by step 5.

1. Restart your phone. Press and hold the Power button (or swipe down from the top of the screen and tap the power icon), then tap Restart. A reboot clears temporary download state and gives the Play Store a clean start. Once the phone is back on, open the Play Store and retry the download. Error 975 is rare enough that simple temporary glitches are the most common trigger, so start here.
2. Clear the Google Play Store’s cache and data. Open Settings, then go to Apps (or Apps & notifications), then See all apps. Tap Google Play Store, then Storage & cache. Tap Clear cache first, then Clear storage (or Clear data) and confirm. This wipes the store’s temporary files without removing your installed apps or your Google account. Reopen the Play Store and retry the download.
3. Clear the Download Manager’s data. In Settings > Apps > See all apps, tap the three-dot menu, choose Show system, find Download Manager, then tap Storage & cache and Clear data. The Download Manager is the system component that fetches the actual app files, and a wedged download record there can produce unusual errors like 975. Retry the download afterward.
4. Clear the Google Play Services cache. In Settings > Apps > See all apps, find Google Play Services, tap Storage & cache, and tap Clear cache — clear only the cache, not all data, since Play Services holds account and sync state other Google apps depend on. Play Services does much of the download work behind the Play Store, and stale state there can surface as rare error codes. Restart your phone and try the download again.
5. Remove and re-add your Google account. Go to Settings > Passwords & accounts, tap your Google account, then Remove account. Restart the phone, go back to Settings > Passwords & accounts, tap Add account > Google, and sign in again with the same account. This rebuilds the account connection between your phone and Google’s servers, which resolves the server-side account glitches that rare errors like 975 often come down to.
6. Switch networks and contact Google support. Try the download on mobile data if you were on Wi-Fi, or on a different Wi-Fi network — some networks interfere with Play Store traffic in ways that produce odd errors. If error 975 persists through every step, contact Google support through the Play Store app (tap your profile icon > Help & feedback). Because 975 is the rarest Play Store error and has no officially documented fix, reporting it directly to Google is the one step nobody should skip.

Did this fix it? Quick checklist

• The app downloads or updates without the 975 pop-up
• The Play Store opens, browses, and searches normally
• No “App could not be downloaded” errors on retry
• Downloads complete over both Wi-Fi and mobile data

If error 975 still appears after all six steps, wait a few hours and try again — rare errors like this sometimes clear on their own when the underlying server-side glitch resolves. If it is still there the next day, the Google support report you filed in step 6 is the path forward; there is no deeper fix documented anywhere.