Here’s a symptom → cause → fix map you can use without guessing.
Before you change anything: if it works in one browser but not another, you’ve already proven your account is fine. The issue is almost always the browser’s privacy, storage, or extension behavior.
1. Symptom: The refund page keeps reloading or you get a sign-in loop
Most likely causes (browser-specific)
- Third-party cookies blocked (Chrome with stricter settings, Firefox Enhanced Tracking Protection on “Strict”, or Safari-style cross-site restrictions).
- Cookie partitioning / tracking prevention breaks the sign-in handoff between Microsoft domains.
- Extension interference (ad blocker, privacy tool, “cookie cleaner”, script blocker).
Fix map (start here)
- Try a private window first (Chrome Incognito / Firefox Private). If it works there, an extension or stored site data is the culprit.
- Temporarily allow cookies for Microsoft domains. In practice, you’re aiming to allow sign-in cookies across: account.microsoft.com, login.live.com, microsoft.com.
- Disable extensions just for the refund attempt (especially ad blockers and privacy add-ons). If you don’t want to disable them globally, pause them for Microsoft sites only.
- Clear site data for Microsoft only (not your whole browser history): remove cookies/site data for the Microsoft and Live/login domains, then retry.
If the loop only happens in Firefox, check Enhanced Tracking Protection for the page and switch it from Strict to Standard for that session.
2. Symptom: Blank page, missing buttons, or the page looks “half loaded”
Most likely causes (browser-specific)
- Content blockers are blocking scripts needed to render the refund flow (common with uBlock-style filters, tracking protection, or hardened settings).
- Cached broken assets (old scripts/styles cached, especially after an update).
- Corporate device policies (managed browser settings, security software injecting filtering).
Fix map
- Hard refresh the page (Ctrl+F5) to force a clean reload of scripts and styles.
- Disable “strict” blocking for the site and reload. In Firefox, try turning off Enhanced Tracking Protection for that specific site as a test.
- Create a clean browser profile (Chrome/Firefox) and retry there. This is a fast way to rule out hidden settings and extensions without losing your main setup.
- Switch browsers for the transaction step only: if Chrome is half-loading, try Firefox; if Firefox is blocking, try Chrome or Edge. The goal is to complete the refund request, then you can revert.
If you’re on a work or school PC, a managed policy can re-break the page after every reset. In that case, the “clean profile” test is especially useful to confirm it’s policy-related.
3. Symptom: The page says you’re not eligible, but you’re sure you are
Most likely causes
- Wrong Microsoft account is signed in (common when multiple accounts are cached in one browser).
- Region/store mismatch because the browser session is tied to a different locale than the purchase.
- Session confusion after password resets or recent sign-in changes (stale tokens).
Fix map
- Open the refund page in a private window and sign in carefully to the account that made the purchase.
- Sign out everywhere in that browser, then sign in once. (Avoid hopping between accounts in the same window.)
- Use one browser for one account temporarily: for example, do personal account in Chrome, work account in Firefox, to avoid cookie collisions.
If it shows “not eligible” in every browser and every private window, it may be a real eligibility rule (time window, consumable item, or usage). But if it differs by browser, it’s almost always session state.
4. Symptom: Clicking “Request a refund” does nothing (or a new page never opens)
Most likely causes (browser-specific)
- Pop-ups or redirects blocked (the flow may open a new step or use cross-domain redirects).
- Security/privacy extensions blocking “open in new tab” actions or redirect chains.
Fix map
- Allow pop-ups/redirects for Microsoft pages just long enough to complete the request.
- Try the same click using keyboard (Ctrl+Enter on links, or open in new tab). Sometimes blockers treat scripted clicks differently than direct navigation.
- Turn off “block redirects” style features in privacy tools for that site, then reload.
When this is browser-only (works in Firefox but not Chrome, or vice versa), it’s almost never a Microsoft service outage—it’s the handoff being blocked.
5. Symptom: It works in one browser but not another (quick decision rule)
Use this as a fast shortcut:
- If Chrome fails but Firefox works: look for cookie/redirect restrictions in Chrome settings, plus extensions.
- If Firefox fails but Chrome works: Enhanced Tracking Protection (especially Strict) or a privacy add-on is usually the difference.
- If neither works in normal windows but private windows work: stored site data or an extension is the root cause—clear Microsoft site data and re-enable extensions one by one.
- If nothing works anywhere: switch networks (or disable VPN) once to test; then consider contacting Microsoft support with the order number.
Final thoughts
Refund flows are extra sensitive to cookies, redirects, and tracking protection because they rely on secure sign-in handoffs across domains. That’s why the exact same Microsoft page can behave differently in Chrome, Firefox, and Safari-style privacy models.
If you only need the refund done today, the most practical move is: private window → disable blockers for Microsoft domains → complete the request → revert your settings.