Gmail Not Working on PC After an Update? Fix Loading, Login, and Clicking Issues Fast

Quick answer: Fix a Gmail after update issue on PC by clearing site data for mail.google.com (cookies + cache) and testing Gmail in a clean browser session with extensions disabled.

If Gmail works in Incognito/private mode but not normal mode, the cause is almost always corrupted site data, a cookie/permission change, or an extension/security tool blocking requests.

Quick Fix Checklist

• Classify the issue first (don’t guess):
  • Login/account: sign-in loop, keeps asking for password, 2‑step prompt never completes, “Cookies are disabled”.
  • Browser/app state: Gmail loads but Compose/Send/Search doesn’t work, UI broken, blank white page, constant refresh.
  • Network/transport: stuck loading, “This site can’t be reached”, attachments never upload, timeouts.
  • Service-side: same failure on multiple devices/browsers/networks, or Google reports an incident.
• Reproduce once and write down the exact symptom (blank page vs sign-in loop vs can’t send). This prevents doing broad fixes that don’t match the problem.
• Test Incognito/private mode (extensions usually off). If it works there, go straight to extensions + site data.
• Test another browser (Chrome/Edge/Firefox) and another network (mobile hotspot vs Wi‑Fi) to isolate browser vs network policy.
• Check Google Workspace Status Dashboard if multiple devices are affected: https://www.google.com/appsstatus/dashboard/

Causes (realistic, not generic)

• Cached assets mismatching the new Gmail version: after an update, old cached scripts/styles can break the UI, cause blank pages, or make buttons stop responding.
• Browser compatibility regression: updates can change cookie rules, tracking protection, GPU rendering, or security policies that Gmail relies on.
• Settings reset or permission changes after update: third-party cookies blocked, pop-ups/redirects blocked, JavaScript restricted, or site permissions changed.
• Extension/plugin conflict exposed by the update: ad blockers, privacy tools, script injectors, password managers, and antivirus web shields can block Gmail requests.
• Network filtering or TLS inspection: corporate gateways, DNS filters, proxies/VPNs, or antivirus “HTTPS scanning” can break Google auth redirects or block Gmail endpoints.

Symptom on PC	Most likely cause	Best first fix
Works in Incognito/private mode but not normal mode	Extension conflict or corrupted site data	Disable extensions + clear site data for mail.google.com
Works on one network but not another	Network filtering, DNS, proxy/VPN, or TLS inspection	Test hotspot, remove proxy/VPN, check firewall/web shield logs
Can’t sign in / sign-in loop	Cookie/session blocked, third-party cookies policy, stale tokens	Allow cookies for Google + clear cookies for accounts.google.com
Gmail loads but Send/Attach/Compose fails	Blocked requests (extensions/security) or broken cached scripts	Disable blockers, then check DevTools Console/Network for blocked calls
Blank white page / missing panels / flicker after update	GPU/hardware acceleration or cached UI assets	Hard refresh + clear cache for mail.google.com + toggle hardware acceleration
Fails on multiple devices and browsers	Service-side outage or account/policy issue	Check status + test another Google account + review account security alerts

Step-by-Step Fix

0) Choose the right path (30-second classifier)

• If you can’t sign in: do Step 1 first (cookies/session).
• If Gmail opens but actions fail: do Step 2 (extensions/blocked requests).
• If it’s blank/broken/stuck loading: do Step 3 (cache + rendering).
• If it depends on the network: do Step 4 (DNS/proxy/filtering).

1) If you cannot sign in: fix account/session and cookies first

• Clear only Google/Gmail site data (targeted):
  • Remove site data for: mail.google.com, accounts.google.com, google.com.
  • Close all browser windows, reopen, then sign in again.
• Allow cookies needed for Google sign-in:
  • If third-party cookies are blocked, add exceptions for [*.]google.com and [*.]googleusercontent.com (names vary by browser).
  • Temporarily set tracking protection to Standard for testing.
• Allow pop-ups/redirects for Google (often missed):
  • Some sign-in flows open a redirect or prompt that can be blocked after an update.
  • Add an allow rule for pop-ups/redirects on accounts.google.com and mail.google.com, then retry.
• Check Windows date/time sync (uncommon but real): if Windows time/timezone is wrong, Google sign-in can fail due to certificate/token validation. Set time and timezone to automatic, then retry.

2) If Gmail loads but actions fail: isolate extensions and blocked requests

• Run a clean session test (fastest proof):
  • Create a new browser profile (not just a new tab) and sign into Gmail there.
  • If it works in the new profile, your main profile has an extension/policy/cache problem.
• Disable extensions in batches:
  • Turn off ad blockers, privacy blockers, script managers, password managers, antivirus browser add-ons, and “shopping/coupon” extensions first.
  • Reload Gmail and retest Compose, Search, Send, and Attach.
• Whitelist Gmail in blockers (specific):
  • Allow requests to mail.google.com, accounts.google.com, apis.google.com, and *.googleusercontent.com.
  • If your blocker has “cosmetic filtering”, disable it for Gmail to prevent UI elements from being hidden.
• Advanced fix: reset the browser’s site permissions for Gmail (helps after updates that change permission defaults):
  • Open the site info/lock icon in the address bar on Gmail.
  • Reset permissions, then re-allow what you need (notifications, pop-ups/redirects if required for sign-in prompts).
• Uncommon but realistic fix: disable HTTPS scanning/TLS inspection in antivirus or corporate security tools.
  • Look for “HTTPS scanning”, “Encrypted connections scanning”, “Web Shield”, or “SSL/TLS inspection”.
  • Temporarily disable it and retest Gmail. If it fixes the issue, add a permanent exception for Google domains instead of leaving scanning off.

3) If the page is blank, broken, or stuck loading: fix cached assets and rendering

• Hard refresh Gmail: open Gmail and use Ctrl+F5 (Windows) to force reload of assets.
• Clear cached files for Gmail (not all browsing history):
  • Use your browser’s site data controls to remove cache for mail.google.com, then reload.
• Turn off hardware acceleration (targeted test):
  • Chrome/Edge: Settings → System → disable “Use hardware acceleration” → relaunch.
  • This can fix post-update rendering glitches (white page, flicker, missing UI panels).
• Try the basic HTML view alternative (quick isolation test):
  • If the standard UI is broken, try opening Gmail again after clearing site data; if you can access mail in another browser, the issue is local UI/scripts rather than your account.

4) If it works on one network but not another: isolate routing/filtering

• Compare networks: test Gmail on a mobile hotspot. If hotspot works but office/home Wi‑Fi fails, it’s a network policy/DNS/filtering issue.
• Disable VPN/proxy for the test:
  • Windows proxy settings and browser-level proxies can break Google auth redirects after updates.
  • Turn off VPN, then check Windows Settings → Network & Internet → Proxy.
• Check DNS filtering logs: if you use Pi-hole/NextDNS/AdGuard DNS, review logs for blocked Google endpoints and allowlist them.
• Captive portal check (edge case): on some networks, you must accept a Wi‑Fi login page first. Open a non-HTTPS site or your router’s captive portal page, complete sign-in, then retry Gmail.

5) Use browser diagnostics before repeating fixes (advanced)

• Check DevTools Console errors:
  • Open Gmail → press F12 → Console.
  • Look for blocked script errors, CSP violations, or extension-related messages.
• Check Network tab for failing calls:
  • Open F12 → Network → reload Gmail.
  • Note red/failed requests and status codes:
  • 401/403: auth/cookies/policy issue
  • (blocked): extension or browser privacy feature
  • 5xx: service-side or upstream network issue

Still Not Working

• Do a controlled “known-good” test (fastest way to stop guessing):
  • New browser profile + no extensions + default settings.
  • Test on a different network (hotspot).
  • If that works, the problem is local (profile/extension/security/network policy).
• Edge cases to check on the PC:
  • Storage full: if your browser profile disk is full/near full, site data writes can fail and Gmail can behave unpredictably.
  • Security software web protection: temporarily disable “web protection” modules (not just real-time file scanning) and retest.
  • Windows hosts file: if Google domains are mapped/blocked, Gmail may not load. (Common on heavily customized or previously infected systems.)
  • Managed device policies: on work/school PCs, policies can block cookies, JavaScript, or Google domains after updates. Ask IT to review web filter/TLS inspection logs for blocked Google endpoints.
• Escalation steps (when basic fixes fail):
  • Update the browser to the latest version, then restart the PC (not just the browser).
  • Reset browser settings (keeps bookmarks, but may disable extensions and reset site permissions). Use this if a new profile works but your main profile doesn’t.
  • Reinstall the browser (last resort for one-browser-only failures). If possible, back up bookmarks/sync first.
  • Try Gmail in another account on the same PC/browser. If a different account works, focus on account security prompts, recent password changes, or unusual activity checks.
  • Check Google Account security for alerts and recent sign-in blocks: https://myaccount.google.com/security
  • Contact support / admin: Workspace users should contact their Google Workspace admin with timestamps, network used, and any Console/Network errors.
• What to collect before escalating (saves time):
  • Exact error text + time it happened
  • Browser name/version and Windows version
  • Whether Incognito works
  • Whether hotspot works
  • DevTools Console + Network screenshot (showing failed requests)

If you want the fastest next step: share the exact symptom (login loop vs blank page vs can’t send), your browser/version, and whether it works in Incognito and on a hotspot. That combination usually identifies the correct fix path immediately.

If the Problem Started After an Update

If the problem started right after an update, the timing strongly suggests a compatibility or local data issue.

Why this happens

Updates can change permissions, invalidate saved sessions, or leave behind temporary cached data that no longer matches the latest app or system version.

How to fix it

1. Restart the device first to clear temporary glitches triggered by the update.
2. Check whether a follow-up patch is already available for the app or system.
3. Sign out and sign back in if the app still opens but a specific function fails.
4. Clear cache or reinstall the app if the issue appears tied to corrupted local data.
5. Look for reports from other users to confirm whether the update introduced a wider bug.

Important notes

• If many users report the same issue after the same update, a vendor-side patch may be required.
• Do not reset the whole device too early if simpler update-related fixes have not been tested yet.

Frequently Asked Questions