MicrosoftEdgeUpdate.exe
Also called microsoftedgeupdate, edge update, edgeupdate
Microsoft Edge updater. It is the Omaha-style update client for Edge. It is not msedge.exe and it is not the WebView2 runtime.
What you need to know
This updates Edge, it is not msedge.exe and not WebView2.
MicrosoftEdgeUpdate.exe is the Edge (and often WebView2) Omaha updater. Scheduled tasks launch it. msedge.exe is the browser. msedgewebview2.exe is the embed runtime.
- Safe?
- Yes, from Edge Update
- Is it the browser?
- No. That is msedge.exe
- Is it WebView2?
- No. That is msedgewebview2.exe
What is MicrosoftEdgeUpdate.exe?
MicrosoftEdgeUpdate.exe updates Edge. It is not msedge.exe and it is not WebView2. The same Omaha binary can serve Edge and the WebView2 runtime as update clients.
What does it do?
It checks, downloads, and applies Edge channel updates through the edgeupdate / edgeupdatem services. It does not render tabs. msedge.exe does that. It does not host an embed. msedgewebview2.exe does that.
Why is it running?
MicrosoftEdgeUpdateTaskMachineUA or a similar task ran, or edge://settings/help asked for an update. A forever-running copy from the wrong folder is the path check.
Is it safe?
Usually safe
Program Files (x86)\Microsoft\EdgeUpdate is the updater. A MicrosoftEdgeUpdate.exe on the desktop is not. The browser and WebView2 stay different filenames.
A legitimate copy normally runs from:
C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe
- Omaha updater
- Browser: msedge.exe
- Runtime: msedgewebview2.exe
Can I end it?
Stops this update pass
Ending MicrosoftEdgeUpdate.exe stops the current check or apply. Edge tabs stay. The task will start it again. Pause updates with Edge or org policy if you need that.
Can I remove it?
Do not delete the updater folder
Do not delete MicrosoftEdgeUpdate.exe. Edge and WebView2 security fixes travel through this client. Removing msedge.exe is a different, unsupported fight.
Should it start with Windows?
Scheduled tasks and the edgeupdate services start it. It is not a browser Startup tab.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Short while checking or patching
- Memory
- Small
- Disk
- Installer payload
- Network
- Update check and download
File information
| Executable name | MicrosoftEdgeUpdate.exe |
|---|---|
| Common legitimate path | C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe |
| Publisher | Microsoft Corporation |
| Signature expectation | Signed by Microsoft Windows |
Common problems
People end msedge to stop "Edge Update"
Tabs close. The updater task still runs later. This filename is the client.
Confused with WebView2
WebView2 can update through the same Omaha stack. The runtime process is still msedgewebview2.exe.
Troubleshooting
Diagnose before you change anything destructive.
Task Scheduler > MicrosoftEdgeUpdateTaskMachineUA
The action should point at EdgeUpdate\MicrosoftEdgeUpdate.exe. That is not msedge.exe.
edge://settings/help for a manual check
Do not download an "Edge updater" from a filename site.
Technical details
Technical details
| Image name | MicrosoftEdgeUpdate.exe |
|---|---|
| Role | Microsoft Edge Omaha updater |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Microsoft Learn: configure Microsoft Edge · msedgeupdate.admx is the Edge Update template
- Microsoft Learn: Edge Update policies · edgeupdate services and tasks
- Microsoft Learn: WebView2 · Runtime is a different image
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.