How to Fix Microsoft Edge Too Many Redirects Error

Encountering the frustrating Microsoft Edge "Too Many Redirects" error? You're not alone! This common issue, often shown as ERR_TOO_MANY_REDIRECTS, blocks access to websites due to endless redirect loops. Don't worry—our straightforward guide will get you back online in minutes. Follow these proven steps, tailored for the latest Microsoft Edge versions, and say goodbye to redirect headaches forever. Let's dive in! ✅

Microsoft Edge Too Many Redirects error screen

What Causes the "Too Many Redirects" Error in Microsoft Edge?

This error happens when a website's server keeps redirecting your browser in a loop, overwhelming Edge's limits. Key culprits include:

  • 🕸️ Corrupted browser cache and cookies from faulty sites.
  • 🔌 Faulty extensions interfering with page loads.
  • 🌐 Misconfigured DNS settings or proxy/VPN conflicts.
  • 🛡️ Overzealous antivirus or firewall rules.
  • 📝 Altered hosts file entries blocking domains.

Understanding these helps you target fixes efficiently. Ready to troubleshoot? Start with the quickest wins below. 👇

Step-by-Step Fixes for Microsoft Edge "Too Many Redirects"

1️⃣ Quick Fix: Clear Cache and Cookies

The #1 cause? Stale data. Here's how to wipe it:

  1. Open Microsoft Edge and press Ctrl + Shift + Delete.
  2. Select "All time" and check Cookies and other site data + Cached images and files.
  3. Click Clear now. Restart Edge and test the site.

Pro tip: Do this for all time to ensure a clean slate. 80% of users fix it here! 🎉

2️⃣ Disable Extensions One by One

Extensions like ad blockers can trigger loops. Disable them:

  1. Go to edge://extensions/.
  2. Toggle off all extensions.
  3. Reload the page. Re-enable one by one to identify the culprit.

3️⃣ Reset Edge Settings to Default

If basics fail, reset without losing data:

  1. Type edge://settings/reset.
  2. Click Restore settings to their default values.
  3. Confirm and restart. This fixes most misconfigurations.
Clearing cache in Microsoft Edge to fix redirects

4️⃣ Flush DNS and Reset Network

Network glitches? Command prompt to the rescue (Run as Admin):

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset

Restart your PC. This refreshes DNS caches causing loops.

5️⃣ Check Hosts File and Proxy Settings

Edit hosts file (C:\Windows\System32\drivers\etc\hosts):

  • Open in Notepad as Admin.
  • Remove suspicious lines for the affected site.
  • Save and flush DNS again.

Disable proxy: edge://settings/system > Turn off "Use a proxy server."

Common Cause Quick Fix Success Rate
Cache/Cookies Clear via Ctrl+Shift+Delete ⭐⭐⭐⭐⭐ 80%
Extensions Disable at edge://extensions/ ⭐⭐⭐⭐ 70%
DNS/Proxy Flush DNS commands ⭐⭐⭐⭐ 65%

6️⃣ Advanced Fixes: Antivirus, VPN, and Reinstall

  • 🔒 Temporarily disable antivirus real-time protection.
  • 🌍 Turn off VPN/proxy and test.
  • 📥 Update Edge: edge://settings/help.
  • 🔄 Last resort: Uninstall/reinstall via Windows Settings > Apps.

For official guidance, check Microsoft's support: Microsoft Edge Help.

Prevent Future Microsoft Edge "Too Many Redirects" Errors

Stay redirect-free:

  • ✅ Regularly clear cache weekly.
  • ⭐ Vet extensions—stick to trusted ones.
  • 🛡️ Keep Edge and Windows updated.
  • 📱 Test in InPrivate mode (Ctrl + Shift + N) for quick checks.

Still Stuck? Next Steps

If nothing works, it might be site-side. Contact the website admin or try Chrome/Firefox. Share your fix in comments below—what worked for you? 😊 We've helped thousands—your smooth browsing awaits!

Bookmark this for quick reference. Happy browsing! 🚀

Leave a Comment

Build a Local SUSE Update Server with RMT on SLES 15

Build a Local SUSE Update Server with RMT on SLES 15

Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.

Join SLES 15 to Active Directory with SSSD in YaST

Join SLES 15 to Active Directory with SSSD in YaST

Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.

Enable SLES Live Patching and Verify a Kernel Fix

Enable SLES Live Patching and Verify a Kernel Fix

Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.

Apply the SLES 15 STIG Safely with OpenSCAP

Apply the SLES 15 STIG Safely with OpenSCAP

Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.

Restore Cockpit Access to SUSE Linux Enterprise Server

Restore Cockpit Access to SUSE Linux Enterprise Server

Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.

Configure Reliable Ethernet Failover with SLES 15 Bonding

Configure Reliable Ethernet Failover with SLES 15 Bonding

Create a redundant Ethernet connection on SLES 15 with YaST and Wicked, configure active-backup bonding, and verify both ports and failover.

Build a Reusable AutoYaST Profile for SLES 15 Installs

Build a Reusable AutoYaST Profile for SLES 15 Installs

Turn an existing SLES 15 system into a reviewed AutoYaST profile, validate it, and use it to deploy a test server with fewer manual steps.

SLES 15 KVM Setup: Make Selected VMs Start at Boot

SLES 15 KVM Setup: Make Selected VMs Start at Boot

Install the SLES 15 KVM and libvirt tools, enable the right host service, and configure selected virtual machines to start after a reboot.