How to Stop Microsoft Edge from Reinstalling Automaticaly

Are you fed up with Microsoft Edge reinstalling automatically every time you delete it? 😤 You're not alone. This stubborn browser keeps coming back via Windows Updates or system processes, frustrating millions of users. But don't worry— we've got your back with proven, safe methods that work on the latest Windows versions. Follow these steps to reclaim control and enjoy a clutter-free PC. Let's dive in and banish Edge for good! 👍

Why Does Microsoft Edge Reinstall Automatically?

Microsoft bundles Edge deeply into Windows. It reinstalls through:

  • Windows Updates (especially Edge WebView2 runtime).
  • EdgeUpdate service running in the background.
  • System reset or feature updates.

Understanding this helps you target the root cause. Now, let's fix it step-by-step. These methods are tested on current Windows builds—no guesswork.

Method 1: Complete Uninstall + Block Edge Updates (Easiest for Home Users)

This stops Microsoft Edge from reinstalling automatically by removing it fully and disabling its updater. Perfect for Windows 10/11 Home.

  1. ✅ Uninstall Edge: Go to Settings > Apps > Installed apps. Search "Microsoft Edge," click the three dots, and select Uninstall. Repeat for all Edge versions (stable, beta, etc.).
  2. 🔒 Kill EdgeUpdate Service: Press Win + R, type services.msc. Find "Microsoft Edge Update service," right-click > Properties > Stop > Set Startup type: Disabled.
  3. 🛡️ Registry Tweak (Power User): Open Registry Editor (Win + R > regedit). Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate. Create DWORD DoNotUpdateToEdgeWithChromium = 1. Also add under HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate.
  4. 📂 Delete Remnants: Navigate to C:\Program Files (x86)\Microsoft\Edge\Application and %LOCALAPPDATA%\Microsoft\Edge. Delete folders (take ownership if needed).

Reboot and test—no more auto-reinstalls! If Edge sneaks back, proceed to advanced methods.

Step-by-step screenshot showing Microsoft Edge uninstall process and registry edit to stop reinstalling automatically

Method 2: Group Policy Editor (Pro/Enterprise Power Move)

For Windows Pro or higher, Group Policy is your best friend to prevent Microsoft Edge auto reinstall.

  1. Press Win + R > gpedit.msc.
  2. Navigate: Computer Configuration > Administrative Templates > Windows Components > Microsoft Edge Update.
  3. Enable Update policy override default > Set to Updates disabled.
  4. Bonus: Under Windows Update > Manage updates offered from Windows Update > Enable Do not include drivers with Windows Updates (blocks Edge bundles).
Policy PathSettingEffect
Microsoft Edge UpdateUpdates disabledBlocks all Edge reinstalls
Windows Components/AppRuntimeBlock non-admin app installsPrevents WebView2 auto-install
Windows UpdateSelect when updates installManual control over Edge pushes

This locks it down enterprise-style. 💪 Pro tip: Apply to both User and Computer configs for full coverage.

Method 3: PowerShell Script for Total Annihilation

Want automation? Use this script to stop Microsoft Edge from reinstalling automatically forever.

iwr -useb https://raw.githubusercontent.com/OttoYiu/edge-about-blank/master/edgeaboutblank.ps1 | iex

Or custom script:

  1. Run PowerShell as Admin.
  2. Get-AppxPackage *edge* | Remove-AppxPackage
  3. Stop-Service -Name "MicrosoftEdgeUpdate" -Force
  4. Set-Service -Name "MicrosoftEdgeUpdate" -StartupType Disabled

For WebView2 (common culprit): wmic product where name='Microsoft Edge WebView2 Runtime' call uninstall.

PowerShell commands and Group Policy screenshots to block Microsoft Edge from reinstalling automatically

Method 4: Block via Hosts File & Firewall (Nuclear Option)

Extra layer: Edit C:\Windows\System32\drivers\etc\hosts (Admin Notepad):

127.0.0.1 edgeupdates.microsoft.com
127.0.0.1 msedge.api.cdp.microsoft.com

Firewall: Block outbound for EdgeUpdate.exe in Windows Defender Firewall.

Troubleshooting Common Issues

  • ❌ Still Reinstalling? Check for pending Windows Updates—pause them via Settings > Update & Security.
  • Safe Mode Uninstall: Boot to Safe Mode for stubborn remnants.
  • WebView2 Persists: Use Microsoft's WebView2 docs for manual removal.

Final Thoughts: Freedom Achieved! 🎉

Congrats—you've mastered how to stop Microsoft Edge from reinstalling automatically! Pick Method 1 for quick wins or combine for ironclad protection. Your PC feels lighter already, right? 😊 Stay vigilant with updates, and if issues pop up, revisit these steps. Share your success in comments below—what browser are you switching to? Chrome? Firefox? Let's keep the conversation going!

These fixes are based on latest Windows behaviors and Microsoft policies. Always back up Registry before edits.

Leave a Comment

Enable FIPS Mode on SLES 15 and Verify the Boot State

Enable FIPS Mode on SLES 15 and Verify the Boot State

Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.

Set Up a LUKS-Encrypted Data Volume on SLES

Set Up a LUKS-Encrypted Data Volume on SLES

Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.

Build a Custom AppArmor Profile on SUSE Linux

Build a Custom AppArmor Profile on SUSE Linux

Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.

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.