On Windows, Apple refund pages can get “stuck” showing an old status, endless loading, or a vague error—especially if you’ve recently switched networks, used a VPN, or signed into multiple Apple IDs.

Envelope with loading ring icon indicating refund status pending

Most of the time it’s not that the refund disappeared; it’s the browser session or network path showing you the wrong thing.

Use this if/then tree in order. Stop as soon as your refund status loads correctly.

1. If you see a spinner, blank area, or “Something went wrong”

This usually happens when a script or cookie needed to fetch your refund status is blocked, stale, or mismatched.

  • Then: Try a Private/Incognito window first and sign in again.
  • Then: If it works in Private/Incognito, your normal profile likely has a cookie/cache conflict (go to section 2).
  • Then: If it still fails in Private/Incognito, it’s more likely network filtering, DNS, VPN/proxy, or an extension affecting all sessions (go to section 3).

Shield and cracked cookie icon for privacy and cookie issues

2. If it works in Private/Incognito (cookie/session mismatch)

Why it happens: Apple’s refund tools rely on session cookies and sometimes cross-site components. A stale cookie, corrupted cache entry, or blocked third-party cookie can keep you signed in “halfway” and the status call never completes.

Do the smallest reset that targets the refund site.

  • Then: Clear site data for Apple domains (cookies + site storage) in your main browser profile, and reload.
  • Then: Fully close and reopen the browser (not just the tab) and sign in again.
  • Then: Temporarily allow third-party cookies or cross-site tracking protections only for the Apple refund/sign-in flow, then revert after checking status.
  • Then: If you use multiple profiles (work/personal), try a different profile to avoid mixed sign-in states.

One small tell: if you’re repeatedly asked to sign in, or you sign in successfully but land back on the same page, that’s almost always a cookie/session loop.

3. If it fails even in Private/Incognito (network path or extensions)

Why it happens: VPNs, proxies, security software, DNS filters, and some ad blockers can block the endpoints that return refund status. Because Incognito still uses the same network and often the same system-level filters, the problem stays.

  • Then: Turn off VPN temporarily and try again.
  • Then: If you’re on a work/school network, try a different connection (mobile hotspot is fine for a quick test).
  • Then: Pause ad blocker/privacy extensions for the refund page and retry.
  • Then: Check Windows date/time is set automatically (an incorrect clock can break secure sessions and cause silent reloads).
  • Then: Try a different browser on Windows (Edge vs Chrome vs Firefox). If only one fails, it’s usually extension or per-browser privacy settings.

Disconnected network cable and blocked VPN icon

4. If the page loads, but the refund status looks wrong (wrong purchase, “not found”, old status)

Why it happens: refund tools are tied to the Apple ID used for the purchase, and sometimes to the region/storefront. If you’re signed into a different Apple ID than the one that paid, you may see no request, the wrong request, or a status that doesn’t match your email receipt.

  • Then: Sign out completely, close the browser, reopen, and sign in with the Apple ID that appears on the purchase receipt.
  • Then: If you have Family Sharing, confirm who was billed (organizer vs family member). Use the billed account to check refund status.
  • Then: If you recently changed region, make sure you’re signing into the correct storefront for that purchase.
  • Then: Give it a little time: status pages can lag behind the email confirmation by several hours (sometimes longer during high volume).

A practical check: search your email for the Apple receipt and compare the Apple ID on that receipt to the one you’re currently signed into.

Final thoughts

Refund pages on Windows most often fail because the browser is holding onto an old session (fixed by clearing site data) or because a VPN/filter blocks the status request (fixed by switching networks or pausing the VPN).

If you still can’t see a status after trying a different browser and a different network, it’s usually time to contact Apple Support with your order/receipt details so they can locate the request from their side.