Edge is Microsoft’s own browser, native on ARM64, preinstalled on your Snapdragon laptop — and it keeps crashing. Tabs die, the whole window vanishes, or it will not even launch. The browser that is supposed to be the best citizen on this hardware is the one misbehaving, which makes it extra maddening.

Because Edge is native ARM64 out of the box, crashes are rarely about emulation. The usual suspects are a corrupted profile, the Adreno GPU driver fighting hardware acceleration, a damaged update, a bad extension, or corrupted system files underneath. Edge also carries extra Windows integration (SmartScreen, Defender hooks) that can crash it in ways Chrome never sees.

This guide gives you six fixes in order: launch it safely to diagnose, fix the GPU path, clean the profile, repair the installation, check the system underneath, and handle the last external suspects. Meeting-recap features crashing alongside the browser share roots with Copilot Teams meeting recap issues , so note any pattern.

Why this happens

  • Corrupted Edge profile: The most common cause — damaged history, cookies, or preference files crash the browser at launch or kill tabs randomly.
  • GPU driver conflict: Hardware acceleration against a buggy Adreno driver crashes the renderer; Edge leans on the GPU harder than most apps.
  • Damaged Edge update: An interrupted or partial Edge update leaves mixed binaries that crash unpredictably.
  • Bad extension: Extensions run natively but can still corrupt memory or hook APIs badly — one bad extension crashes the whole browser.
  • Corrupted system files: Edge depends on Windows components (WebView2-adjacent plumbing, SmartScreen); damaged system files crash it at startup.
  • SmartScreen or Defender hook issue: The SmartScreen reputation check runs in-process; a damaged SmartScreen cache can take Edge down with it.
  • Insufficient resources under load: Too many heavy tabs on a machine with aggressive memory management triggers tab kills that look like crashes.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Launch Edge with GPU acceleration disabled

This diagnostic launch separates GPU crashes from everything else in one step. If Edge runs fine with the GPU path off, you have a driver problem; if it still crashes, the profile or installation is the suspect.

  1. Right-click the Edge shortcut, choose Properties, and in the Target field add a space and --disable-gpu after the closing quote.
  2. Launch Edge from that shortcut and use it for 10–15 minutes, including your crash-trigger sites.
  3. If it is stable, the GPU path is the problem — remove the flag later and fix the driver (Fix 2).
  4. If it still crashes with the flag, skip to Fix 3 — the profile is the likely culprit.
  5. Remember to remove --disable-gpu from the shortcut once fixed, or you will run software rendering forever. Dock-related display crashes share GPU roots, like USB-C dock dual monitor issues .

Fix 2: Update the graphics driver and toggle efficiency mode

A buggy Adreno driver is the classic Edge-on-Snapdragon crash cause, and Windows Update’s optional drivers are where the fixed ones arrive. Edge’s efficiency mode also changes process behavior in ways that can stabilize — or destabilize — crashing builds.

  1. Open Settings > Windows Update > Advanced options > Optional updates and install every driver update offered.
  2. If your laptop maker (Dell, HP, Lenovo, Samsung, Surface) has a newer graphics driver on their support site, install that instead — OEM drivers are tuned for your exact machine.
  3. In Edge, go to edge://settings/system and try toggling Efficiency mode — test both on and off, since it changes background tab handling.
  4. In the same page, toggle Use graphics acceleration when available and test each state for 15 minutes.
  5. Settle on the stable combination. If acceleration must stay off for stability, retest after each future driver update — the real fix is a driver, not the toggle.

Fix 3: Clean the corrupted profile

Profile corruption is the top cause of persistent Edge crashes, and it survives reinstalls when sync restores the damaged data. The clean-profile test proves it in two minutes.

  1. Click the profile icon and choose Add profile, or launch an InPrivate window, and use Edge there for a while.
  2. If the new profile is stable, your main profile is corrupt — go to edge://settings/reset.
  3. Click Restore settings to their original defaults — this keeps favorites, history, and passwords while disabling extensions and clearing temp data.
  4. If crashes continue, close Edge, open %LOCALAPPDATA%\Microsoft\Edge\User Data, rename Default to Default.bak, and relaunch.
  5. Sign in to sync — your data returns from the cloud, the corruption stays in the .bak folder. Delete it after a stable week. Microsoft’s Windows support pages cover profile-adjacent Windows repairs.

Fix 4: Repair or reinstall Edge

When the browser binaries themselves are damaged — interrupted update, disk error, partial install — no profile trick helps. Edge has a built-in repair path that most people never find.

  1. Go to Settings > Apps > Installed apps, find Microsoft Edge, click the three dots, and choose Modify.
  2. Click Repair in the Edge setup dialog and let it re-download and repair the installation.
  3. If Modify is unavailable, download the ARM64 Edge installer from microsoft.com/edge on the laptop and run it over the top — it repairs in place.
  4. For a full nuke, uninstall Edge (via the installer or winget uninstall Microsoft.Edge), delete %LOCALAPPDATA%\Microsoft\Edge, restart, and reinstall fresh.
  5. Sign in, reinstall only essential extensions, and test for a day before restoring everything.

Fix 5: Repair Windows system files underneath

Edge leans on Windows components harder than third-party browsers — SmartScreen, cryptographic services, the app platform. Corrupted system files crash Edge at launch with no useful error, and the fix is at the OS level.

  1. Open Terminal (Admin) and run sfc /scannow, then restart.
  2. If SFC finds unfixable damage, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow again, then restart.
  3. Temporarily disable SmartScreen in edge://settings/privacy to test whether the reputation service is the crash trigger.
  4. Check Windows Security > App & browser control for reputation-based protection blocks related to Edge.
  5. If a specific Windows update coincides with the crashes’ start, check your laptop maker’s support page for a patched driver bundle — OS and driver fixes ship together on ARM. Samsung’s NPU driver saga shows the pattern: Galaxy Book5 NPU driver issues .

Fix 6: Audit extensions and external hooks

The last layer is everything attached to Edge from the outside: extensions, antivirus browser hooks, and enterprise policy. One bad actor here crashes an otherwise healthy browser.

  1. Go to edge://extensions and disable everything, then re-enable one by one with testing between.
  2. Temporarily disable your antivirus’s browser/web protection and test for 15 minutes — if crashes stop, add Edge exclusions or switch to Defender.
  3. Check edge://policy for enterprise policies forcing settings that conflict (common on work laptops).
  4. Disable Startup boost and background Edge processes in edge://settings/system as a test — they can crash-loop on damaged installs.
  5. If one specific site still kills native Edge with a clean profile and no extensions, report it via Help and feedback > Report an issue and note the ARM64 build.

Closing

Edge crashes on Snapdragon laptops are fixable and almost never mean the hardware is bad — profile corruption, a GPU driver argument, or a damaged update covers nearly every case. The --disable-gpu diagnostic in Fix 1 tells you which road you are on within minutes. Work the list, and Edge goes back to being the fast, cool-running native browser it was meant to be on your machine.

Frequently asked questions

Is Edge native on ARM64 Windows 11?
Yes. Microsoft ships a native ARM64 build of Edge, and it is the default browser on Snapdragon laptops — it installs natively out of the box. Crashes on the native build are almost never an architecture problem; they are profile, GPU, or update issues.
Why does Edge crash immediately on launch?
Launch crashes are usually a corrupted profile, a bad GPU driver interaction, or a damaged Edge installation from an interrupted update. Starting Edge with GPU acceleration disabled (via a command-line flag) is the fastest way to identify which one it is.
Will resetting Edge delete my passwords and favorites?
Resetting settings keeps your favorites, history, and passwords — it only disables extensions and clears temporary data. A full profile wipe removes local data, but anything synced to your Microsoft account comes back when you sign in again.
Should I just use Chrome instead of fixing Edge on ARM?
You can, but Edge’s native ARM64 build is deeply integrated with Windows on ARM and generally the best-optimized browser for Snapdragon laptops. The crashes are fixable, and a repaired Edge usually outperforms emulated alternatives.