Microsoft Edge Crashing, Slow, or Not Loading, Every Fix
Why Microsoft Edge Keeps Crashing or Not Loading
I've seen this pattern repeat itself hundreds of times. Someone sits down at their machine, opens Microsoft Edge, and, nothing. A blank white screen stares back at them. Or Edge loads halfway, then freezes solid. Or worse, it crashes the second it tries to open a page that worked perfectly fine yesterday. You didn't change anything. You didn't install anything suspicious. It just broke.
Here's what's actually going on under the hood. Microsoft Edge is a Chromium-based browser, which means it manages processes the way Chrome does, spinning up separate processes for each tab, each extension, and each renderer. When one of those processes encounters a memory conflict, a corrupted profile cache, a misbehaving extension, or a blocked network endpoint, the whole experience falls apart. The error messages Edge gives you, things like "Hmm, can't reach this page," "Edge is not responding," or a blank gray or white pane, are almost deliberately unhelpful. They don't tell you which process failed, which extension is the culprit, or whether the issue is local or server-side.
The people who run into Microsoft Edge crashing or not loading issues most often fall into a few categories. First, enterprise users on domain-joined machines where Group Policy is doing something unexpected, blocking a sidebar URL, restricting extensions, or silently preventing Edge from authenticating. Second, users who've just received a Windows Update or an automatic Edge update that introduced a regression. Third, home users who've accumulated years of cached data, dozens of extensions, and a browser profile that's quietly become corrupted over time.
The Copilot sidebar not loading in Edge is its own sub-category of "not loading" problems. If you click the Copilot icon and get a blank pane, a Refresh button, a Sign in prompt, or a Try again screen, that's almost always an authentication token failure or a blocked service endpoint, not a browser crash. It looks like a crash, but the fix is completely different.
Microsoft Edge not responding on Windows 11 has also spiked in support tickets since Edge 145 and 146 rolled out, specifically because of changes to how the Copilot sidebar URLs are handled internally. If you're in an environment with the EdgeSidebarAppUrlHostBlockList policy set to a wildcard, those Edge 146 URL changes will silently kill Copilot Chat, and it's not obvious at all why.
The good news: almost every scenario that causes Edge to crash, run slow, or refuse to load has a known fix. This guide walks through all of them, from the thirty-second fix that resolves most cases to the Group Policy and registry-level solutions you need for managed enterprise environments. Browse all Microsoft fix guides →
The Quick Fix, Try This First for Microsoft Edge Not Loading
Before you spend an hour digging through settings, try this. It resolves about 60% of cases where Microsoft Edge is crashing, blank, or running slow, and it takes under two minutes.
Open Edge and paste this into the address bar:
edge://settings/resetYou'll land on the Reset Settings page. Click Restore settings to their default values. Confirm when prompted. This wipes your startup page preference, new tab settings, search engine choice, and pinned tabs, but it does not touch your bookmarks, saved passwords, history, or installed extensions. It does, however, reset extension states, which is often exactly what's needed when an extension has silently corrupted Edge's rendering pipeline.
After the reset, close Edge completely. Don't just click X, make sure Edge is fully exited. Open Task Manager (Ctrl + Shift + Esc), click the Processes tab, and look for any Microsoft Edge or msedge.exe entries still running. Right-click each one and choose End task. Then reopen Edge fresh.
If Edge is crashing before you can even get to the address bar, try launching it in InPrivate mode first. Hold Ctrl + Shift + N while clicking the Edge icon, or right-click the taskbar icon and choose New InPrivate window. InPrivate mode disables all extensions by default. If Edge loads fine in InPrivate but crashes in a normal window, you have an extension causing the problem, and the Step 2 section below will walk you through isolating exactly which one.
Still not loading? Check your internet connection isn't the culprit. Open Command Prompt and run:
ping 8.8.8.8 -n 4If you see four replies with no packet loss, your network is fine. If you see "Request timed out," fix your connection first, Edge can't load anything without one, and some Edge errors look identical whether the problem is local or network-side.
edge://restart URL is your best friend when Edge is sluggish or acting up but not fully crashed. Type it in the address bar and hit Enter, Edge closes every tab and window and restarts itself cleanly, preserving your session. It's faster than a manual close-and-reopen and clears in-memory state that a normal close sometimes leaves behind.
I know "have you tried updating it" sounds patronizing. But Edge crashing after a Windows Update is often caused by a version mismatch between the browser and a system component, and the fix is simply getting Edge to its latest release, which patches those incompatibilities. Microsoft ships Edge updates frequently, and automatic updates don't always fire on schedule, especially in enterprise environments where update policies constrain them.
Open Edge and navigate to:
edge://settings/helpThis page shows your current Edge version and triggers an automatic check for updates. If an update is available, it downloads and installs right there. You'll see a Restart to update button appear when it's ready. Click it.
If Edge won't open at all, you can update it through the Microsoft Edge update tool directly. Open a PowerShell window as Administrator and run:
Start-Process "C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" -ArgumentList "/update" -WaitOn 64-bit systems, the update executable is sometimes under C:\Program Files\Microsoft\EdgeUpdate\ instead. After the update completes, reboot your machine, some Edge component updates require a fresh system session to apply correctly.
In enterprise environments, if you're seeing Edge install or update failures, Microsoft's official guidance is to check the Windows Event Log under Application and Services Logs → Microsoft → Windows → EdgeUpdate for specific error codes. Error codes in the 0x80 range typically indicate network or proxy blocks on Edge's update servers. You'll need to work with your network team to whitelist Edge's update endpoints if that's the case.
When it works: Edge opens normally, loads pages without crashing, and the version number on edge://settings/help matches the latest listed on Microsoft's release notes page.
Extensions are the single most common cause of Edge running slow or crashing on specific pages. A lot of extensions, particularly ad blockers, password managers, and productivity tools, inject JavaScript into every page you load. When that injected code conflicts with a page's own scripts, you get freezes, crashes, or pages that never finish loading. The browser won't tell you which extension is the culprit. You have to find it yourself.
Navigate to:
edge://extensionsToggle off every extension except one. Then visit the page or trigger the scenario that was causing Edge to crash. If it still crashes, that remaining extension isn't the problem, disable it too, and enable the next one. Work through them one at a time until you find the extension that reproduces the crash. Then disable that extension permanently, or check the extension developer's site for an update that addresses Edge compatibility.
A faster approach if you have many extensions: disable all of them at once, confirm Edge is stable, then re-enable them in batches of three. This binary search process cuts the diagnostic time significantly when you're dealing with ten or more extensions.
One important edge case: extensions behave differently in InPrivate browsing. By default, extensions are blocked in InPrivate windows. If you want to allow a specific extension to run in InPrivate mode, you have to explicitly enable it per extension, and in managed environments, that requires Group Policy. If your organization uses the ExtensionSettings policy, your IT admin controls which extensions can run in InPrivate, not you. Trying to toggle it manually will appear to work, but the Group Policy will override it on the next browser restart.
When it works: Edge loads pages normally with the problematic extension disabled. You've identified your culprit.
A bloated or corrupted cache is one of the most reliable causes of Microsoft Edge running slow, or loading pages that look broken, outdated, or blank. Edge stores cached files for every site you visit. Over time, some of those cached files become stale or corrupted, and instead of loading the fresh version of a page, Edge keeps serving the broken cached version in a loop.
Open Edge and press Ctrl + Shift + Delete. The Clear browsing data panel appears. Set the Time range to All time, not just the last hour or day. Check the following boxes:
- Browsing history
- Download history
- Cookies and other site data
- Cached images and files
Leave passwords and autofill data unchecked unless you suspect those are contributing. Click Clear now.
For more aggressive cache clearing, particularly when the above doesn't fully resolve Edge not loading pages, you can delete the cache directory directly. Close Edge completely first (check Task Manager to confirm no Edge processes are running), then open File Explorer and navigate to:
%LOCALAPPDATA%\Microsoft\Edge\User Data\Default\CacheSelect everything inside that folder and delete it. Don't delete the folder itself, just its contents. When Edge restarts, it rebuilds a fresh cache from scratch.
If cookies are causing authentication loops or sign-in problems, clearing them fixes the symptom but also signs you out of every site. Make sure you have your passwords saved before doing this, or Edge's built-in password manager will refill your credentials automatically on next sign-in.
When it works: Pages that were loading blank, stuck, or incorrectly now load properly. Edge feels noticeably faster on sites you visit frequently.
If the Copilot icon is visible in your Edge sidebar but clicking it gives you a blank pane, a Refresh prompt, a Sign in button, or a Try again screen, this is a specific and well-documented failure mode, not a generic browser crash. The fixes are different depending on which symptom you're seeing, so read carefully.
Blank pane or Refresh button: This usually means the Copilot Chat service endpoint is unreachable from your device. Consumer accounts use the endpoint at https://edgeservices.bing.com/edgesvc/shell. Open a new Edge tab and navigate to that URL directly. If it doesn't load, a firewall rule or network policy is blocking it. Contact your network administrator, you'll need that host whitelisted. If it does load but Copilot still shows a blank pane after multiple retries, check the Microsoft 365 Service health dashboard. Copilot has its own service health status, and outages do happen. The Copilot service also sends a heartbeat signal approximately every 15 seconds, if no heartbeat is received, the pane auto-refreshes. If it keeps refreshing without ever loading, the service is down or blocked at the network level.
Sign in or Try again button: This points to an authentication token failure. Select the Sign in button if it's visible and complete the login flow. If you see Try again instead, sign out of your Edge profile entirely, go to edge://settings/profiles, click your profile, and choose Sign out. Then sign back in. For enterprise Entra ID (formerly Azure AD) accounts, the Copilot pane depends on the Bing AAD enrollment cookie being present in the browser. If that cookie is missing or was cleared, authentication fails silently. Sign out and back in to regenerate it.
Also verify your account meets the basic requirements: Copilot in Edge requires a desktop edition of Windows (Home, Pro, or Enterprise). It does not work in Xbox, PWA windows, or Web App windows. Child accounts cannot use Copilot regardless of other settings.
When it works: Clicking the Copilot icon opens the chat interface and responds to your input without showing error screens.
When none of the above steps fix Microsoft Edge crashing or not loading, the issue is often a corrupted browser profile. Your Edge profile stores your preferences, local storage for web apps, extension data, and session state. If any of those files become corrupted, which can happen after a power loss, a failed update, or a forced process kill, Edge can become unstable in ways that no amount of cache clearing will fix.
First, try creating a new profile to test. Click the profile icon in the top-right corner of Edge (it looks like a person silhouette) and choose Add profile, then Add. A new Edge window opens with a clean profile. If Edge runs perfectly in the new profile but crashes in your old one, the old profile data is the problem.
To recover, back up your old profile data first. Navigate to:
%LOCALAPPDATA%\Microsoft\Edge\User Data\Copy the Default folder to a safe location (Desktop or an external drive). Then, with Edge fully closed, rename the original Default folder to Default.old. Restart Edge, it will auto-create a fresh Default folder and a clean profile. You can manually copy back specific items from Default.old (like your Bookmarks file) if you need them.
If you'd rather not lose any profile data, Edge also has a built-in repair option accessible through Windows Settings. Go to Settings → Apps → Installed apps, find Microsoft Edge, click the three-dot menu next to it, and choose Modify. The Edge repair wizard runs and attempts to fix the installation without removing your profile. This is worth trying before the full profile reset.
When it works: Edge opens normally, loads pages without crashing, and maintains a stable session across restarts.
Advanced Troubleshooting for Microsoft Edge Crashes and Loading Failures
If you've worked through every step above and Edge is still crashing or not loading in your environment, you're likely dealing with a policy, network, or registry-level issue. This section is primarily aimed at IT admins and power users comfortable with Group Policy, Event Viewer, and registry editing.
Diagnosing Edge Crashes with Event Viewer
When Edge crashes, Windows logs the event. Open Event Viewer (press Windows + R, type eventvwr.msc, hit Enter), then navigate to Windows Logs → Application. Filter for events with Source = Application Error and look for entries where the faulting application name is msedge.exe. The faulting module name in those entries tells you a lot, if it's msedge.dll, the crash is internal to Edge. If it's a third-party DLL, a software injection tool (like some antivirus products) is hooking into Edge's process and causing the crash.
The EdgeSidebarAppUrlHostBlockList Policy Issue (Edge 146+)
This is the enterprise scenario I see most often right now. Organizations that locked down the Edge sidebar using the wildcard block list policy (EdgeSidebarAppUrlHostBlockList = *) need to update their EdgeSidebarAppUrlHostAllowList after upgrading to Edge 146. The internal URLs that Copilot Chat uses changed in that release.
To check your current policy configuration, navigate to:
edge://policyLook for EdgeSidebarAppUrlHostBlockList and EdgeSidebarAppUrlHostAllowList. If the block list is set to *, your allow list must include all of these:
edge://hub-app-store
edge://discover-chat
edge://commercial-copilot-chat
chrome-untrusted://commercial-copilot-chatThe first two were required in Edge 145 and earlier. The last two are new requirements from Edge 146 onward. If they're missing from your allow list, Copilot Chat will silently fail to load, and the error you see in the sidebar gives you no indication that a policy is blocking it.
Update the allow list through Group Policy Editor (gpedit.msc), Intune, or your MDM solution. After pushing the updated policy, restart Edge and navigate to edge://policy again to confirm the new values appear before testing Copilot.
Checking for Network-Level Blocks
If Edge can't reach specific service endpoints, either for page loading or for Copilot, use PowerShell to test connectivity directly:
Test-NetConnection -ComputerName edgeservices.bing.com -Port 443A TcpTestSucceeded : True result means the endpoint is reachable. If it returns False, your firewall, proxy, or DNS configuration is blocking the connection, and Edge's error messages will tell you nothing about that.
Hardware Acceleration and GPU Driver Conflicts
Edge uses GPU hardware acceleration for rendering by default. On machines with outdated or buggy GPU drivers, this causes Edge to crash or display visual artifacts on video and graphic-heavy pages. Disable hardware acceleration as a diagnostic step by going to edge://settings/system and toggling off Use hardware acceleration when available. Restart Edge. If the crashes stop, your GPU driver is the root cause, update it through Device Manager or your GPU manufacturer's software.
msedge.dll or a specific renderer process. Document the Event Viewer error codes, your Edge version from edge://settings/help, and your OS build number. Then contact Microsoft Support directly. For enterprise environments with Microsoft 365 subscriptions, you can open a support ticket with priority routing, which gets you an actual engineer rather than a scripted support flow.
Prevention & Best Practices for Microsoft Edge Stability
Fixing Edge once is satisfying. Having to fix it every three months because the same problem keeps coming back is not. Here's how you keep Microsoft Edge running fast and stable over the long term.
Keep Edge on automatic updates. I know some users disable automatic updates because they've been burned by a bad release. That's understandable. But the risk of running an outdated Edge version, in terms of security vulnerabilities and accumulating compatibility bugs, outweighs the occasional rough update. If you're in an enterprise environment where you manage updates centrally, set up a staged rollout policy so you can validate a new Edge version on a test group before pushing it fleet-wide. Microsoft documents this through the Microsoft Edge management service.
Audit your extensions regularly. Every extension you add is another process running alongside every page you load. Set a reminder every 90 days to go to edge://extensions and remove anything you haven't used in the past month. Extensions that haven't been updated in over a year by their developers are high-risk candidates for incompatibility issues on newer Edge builds.
Don't let your cache accumulate indefinitely. Edge doesn't have a native "clear cache on close" setting exposed prominently, but you can configure it. Go to edge://settings/clearBrowsingDataOnClose and enable clearing cached images and files when Edge closes. This adds a few seconds to your close time but keeps the cache lean and means you're never debugging a problem caused by a months-old cached file.
For enterprise environments: if you manage the Edge sidebar with policies, document every entry in your EdgeSidebarAppUrlHostAllowList and set a review trigger whenever your organization upgrades Edge to a new major version. The URL changes that broke Copilot in Edge 146 are exactly the kind of thing that slips through when policy documentation isn't kept current with browser releases.
- Enable Sleeping tabs at
edge://settings/system, inactive tabs get suspended after a period you set, dramatically cutting memory usage when you have many tabs open. - Run
edge://crashesperiodically to see if Edge has been silently logging crashes you weren't aware of. Each crash entry has a crash ID you can report to Microsoft or use to correlate with Event Viewer entries. - If you're on a domain-joined machine, run
gpresult /h gpresult.htmlfrom an elevated Command Prompt and open the resulting file, it shows every Group Policy setting applied to your machine, including any that affect Edge. - Keep your Windows graphics drivers current. Edge's rendering pipeline is tightly coupled to GPU drivers, and outdated drivers are a top cause of Edge crashes on pages with video content or WebGL.
Frequently Asked Questions
Why does Microsoft Edge keep crashing only on certain websites?
Site-specific crashes in Edge almost always point to either a misbehaving extension that conflicts with that site's JavaScript, or a hardware acceleration issue affecting how Edge renders that site's graphics or video. Start by opening the same site in an InPrivate window, if it loads fine, an extension is the culprit. If it still crashes in InPrivate, go to edge://settings/system and disable hardware acceleration. Test the site again. If that fixes it, your GPU driver needs updating. Check Device Manager for driver updates, or download the latest driver directly from Intel, NVIDIA, or AMD's website depending on your GPU.
My Edge Copilot sidebar shows a blank white screen, how do I fix it?
A blank Copilot pane in the Edge sidebar means Edge opened the Copilot panel but couldn't connect to the backend service. First, check that you have an active internet connection. Then open a new tab and navigate directly to https://edgeservices.bing.com/edgesvc/shell, this is the consumer Copilot endpoint. If that page doesn't load, a firewall or network rule is blocking it. If it does load but Copilot still shows blank, sign out of your Edge profile at edge://settings/profiles and sign back in. Also verify your account isn't classified as a Child account, which can't access Copilot regardless of other settings.
Edge is using too much memory and making my PC slow, what do I do?
Edge's high memory usage is almost always caused by a combination of too many open tabs and extensions that run background processes. Enable Sleeping Tabs by going to edge://settings/system and turning on the option, you can set inactive tabs to sleep after as little as 5 minutes, and sleeping tabs use a fraction of the memory of active ones. Also audit your extensions at edge://extensions and remove anything unused. If memory usage is still extreme after that, check edge://task-manager (Shift + Esc) to see which specific tab or extension process is consuming the most RAM, it's often one specific culprit, not Edge overall.
After updating to Edge 146, Copilot Chat stopped loading in our company's browser, why?
Edge 146 introduced two new internal URLs that Copilot Chat uses: edge://commercial-copilot-chat and chrome-untrusted://commercial-copilot-chat. If your organization has the EdgeSidebarAppUrlHostBlockList policy set to * (block everything), these new URLs need to be explicitly added to your EdgeSidebarAppUrlHostAllowList or Copilot Chat will fail to load silently. Go to edge://policy on an affected machine to check your current allow list values. Add the missing URLs through Group Policy, Intune, or your MDM solution, then restart Edge to apply. Both new entries are required, adding only one won't be enough.
Edge opens but pages show "Hmm, can't reach this page", is it a DNS problem?
That error in Edge means Edge couldn't resolve or connect to the requested host, but the cause isn't always DNS. Start with the basics: open Command Prompt and run ping google.com. If you get replies, DNS is working fine. If you get "Ping request could not find host," open ncpa.cpl, right-click your active network adapter, choose Properties, then IPv4 Properties, and manually set your DNS servers to 8.8.8.8 and 8.8.4.4. Also run ipconfig /flushdns in an elevated Command Prompt to clear any stale DNS cache entries. If pings work but Edge still can't reach pages, the issue may be a proxy configuration, check edge://settings/system and click Open your computer's proxy settings to verify no unexpected proxy is configured.
The Copilot icon is completely missing from my Edge sidebar, not just blank, but gone
If the Copilot icon is entirely absent from the Edge sidebar, the first things to check are whether the sidebar itself is enabled and whether a Group Policy is hiding Copilot. Go to edge://settings/sidebar and make sure the sidebar toggle is on. Then look at edge://policy, specifically the HubsSidebarEnabled and CopilotPageContext policy values. If either is set by your organization, you may not be able to enable Copilot without IT making a policy change. Also confirm your Edge version is current at edge://settings/help, older Edge versions on some regional builds restricted Copilot availability, and updating to the latest release often restores the icon without any other changes needed.