How to Fix Google Play Store Error 961
What error 961 means
Error 961 is one of the Google Play Store’s murkier error codes. The message reads “App could not be downloaded due to an error. (961)” — it appears mid-install or mid-update, the download dies, and the pop-up tells you nothing about why. Unlike the heavyweight Play Store errors such as 492 or 495, error 961 has no official documentation from Google, so everything we know about it comes from the trail of reports left by people who hit it.
The most distinctive pattern in those reports is timing: many people see error 961 immediately after purchasing a paid app. The theory, and the fix that works, is that the purchase itself hiccupped — the payment authorization failed partway, or the purchase record never synced correctly between the Play Store and Google’s servers. The store then tries to install an app whose purchase is stuck in a broken state, and instead of explaining that, it throws error 961. In these cases the fastest fix has nothing to do with your phone’s settings: open the Play Store, tap your profile icon, go to Payments & subscriptions > Budget & history, find the app, and use Report a problem to request a refund. Google gives you a 15-minute grace period after a purchase during which your card is not charged, so act quickly — and then try the download again.
When error 961 has nothing to do with a purchase, it behaves like the usual Play Store failure family: corrupted cache or data in the store app, a wedged download record in the Download Manager, stale state in Google Play Services, or a glitchy link between your phone and your Google account. The six steps below run through that repair sequence from least to most disruptive, and every one of them is safe — nothing you do here deletes your apps, photos, or files.
Common causes
- Broken app purchase: the payment authorization glitched or the purchase record did not sync, leaving the install in an impossible state — the most common trigger for 961.
- Corrupted Play Store cache or data: broken temporary files in the store app poison its install flow, producing cryptic error codes on every retry.
- Wedged Download Manager record: the system component that fetches app files keeps a broken half-record of the download and fails identically each time.
- Stale Google Play Services or account state: the background framework and your Google account connection share install state with the store, so glitches there surface as obscure errors like 961.
- Faulty Play Store update or network interference: a bad store update can cause 961 on its own, and restrictive Wi-Fi or captive portals can mangle Play Store traffic in ways that produce one-off error codes.
How to fix error 961 — step by step
Work through these fixes in order. Start with step 1 if you bought the app just before the error appeared; otherwise jump straight to step 2.
- Request a refund if the error appeared right after a purchase. Many error 961 cases trace back to a payment glitch during an app purchase, and the install fails because the transaction never completed cleanly. Google gives you a 15-minute grace period after buying an app, during which your card is not charged and you can reverse the purchase. Open the Play Store, tap your profile icon, go to Payments & subscriptions, then Budget & history, find the app, and tap Report a problem to request the refund. Once the refund goes through, try downloading the app again.
- 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 stuck download processes and gives the Play Store a clean start. Once the phone is back on, open the Play Store and retry the install. If a temporary hiccup caused error 961, this is the fastest way past it.
- 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 install or update.
- 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 fail every retry with the same cryptic error 961. Retry the download afterward.
- Uninstall Play Store updates and clear Play Services cache. Sometimes a bad Play Store update itself causes error 961. In Settings > Apps > See all apps, tap Google Play Store, tap the three-dot menu, and choose Uninstall updates, then confirm — the Play Store reverts to its factory version and updates itself again over a stable connection. Then find Google Play Services in the same app list, tap Storage & cache, and tap Clear cache (cache only, not all data). Restart your phone and try the download again.
- Remove and re-add your Google account, then wipe the cache partition. 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 — this rebuilds the link between your phone and Google’s servers and clears account-level purchase glitches. If error 961 still persists, boot into recovery mode (power off, then hold Power and Volume Up together), choose Wipe cache partition, and select Reboot system now. This clears system-level cache without touching your files or apps.
Did this fix it? Quick checklist
- The app installs or updates without the 961 pop-up
- The Play Store opens, browses, and searches normally
- No “App could not be downloaded” errors on retry
- Paid apps show as purchased with the correct purchase status
If error 961 still appears after all six steps, wait a few hours and try again — some cases clear on their own when the underlying purchase or server-side glitch settles. If it is still there the next day, contact Google support through the Play Store app (tap your profile icon > Help & feedback) and reference both the error code and the purchase; for paid apps, this is the fastest route to a resolution.
Frequently asked questions
What does Google Play Store error 961 mean?
Error 961 is a Google Play Store download error that appears as “App could not be downloaded due to an error. (961)” when an install or update fails. It is not an officially documented code — most reports describe it striking during app installs or updates, and a large share of cases trace back to a payment glitch when the app was just purchased.
Why does error 961 often happen right after buying an app?
A lot of error 961 reports come from people who had just purchased a paid app. If the payment authorization failed partway or the purchase record did not sync correctly, the Play Store tries to install an app whose purchase is in a broken state and throws error 961. That is why requesting a refund and re-buying — or waiting for the purchase record to settle — fixes it in these cases.
Will clearing Play Store data delete my installed apps?
No. Clearing cache and storage for the Google Play Store only removes the store’s temporary files — your installed apps, photos, and personal files stay exactly where they are. You will just need to accept the Play Store terms again when you reopen it.
What if error 961 keeps coming back?
If error 961 survives every step — refund, restart, cache and data clears, Play Store reset, account refresh, and cache-partition wipe — try the download on a different network (mobile data versus Wi-Fi), since restrictive networks can interfere with Play Store traffic. For paid apps, contact Google support through the Play Store app (tap your profile icon > Help & feedback) and reference the error code and the purchase.