MicrosoftEdgeUpdate.exe Keeps Crashing? Check Updates Before Disabling It

MicrosoftEdgeUpdate.exe is Microsoft’s Edge updater. If it keeps crashing, first check whether Edge can still finish an update. Open edge://settings/help, note the browser version and any error, then complete a requested restart. One crash entry and a browser that updates successfully need a different response from a repeated failure that leaves updates unfinished. Do not permanently disable the updater or delete its folder to clear an error history: that can remove the update path you are trying to repair.

Check the update outcome before changing anything

The useful question is not just “Did the process crash?” It is “What happened when I checked for an update?” The About Microsoft Edge page distinguishes an available download, a pending restart and an up-to-date browser. Metered connections can also require a download decision. [1]

1. Open Settings and more → Help and feedback → About Microsoft Edge, or enter edge://settings/help in the address bar.
2. Record the version and the exact status or error. If a download is offered, allow it on a suitable connection. Save your work before restarting the browser.
3. Return to the same page after the restart. Compare the result with the note you made. A version need not change when there was no newer update available.

• An old crash entry, but About Edge now reports up to date: leave updating enabled. Watch for a new failure at a new time rather than trying to erase the old event.
• An update is waiting for download or restart: complete that step, then recheck. A pending action is different from a failed installation.
• The same update error returns after restart: keep the exact code and time. Follow the repair section below, then compare the result.
• Only an app using WebView2 is failing: check that app and its runtime separately. A working Edge browser does not establish that every embedded browser app is healthy.

A Windows Error Reporting entry or a file named crashpad_log is a starting point for investigation, not a malware verdict. Match its timestamp and faulting application to the actual symptom. If the whole PC freezes or restarts, an updater event recorded nearby does not by itself identify the cause.

Check the actual file, not just its name

In Task Manager, locate the updater and choose Open file location. Open the executable’s Properties and inspect its digital signature details. Record the full location, signer and file version; do not launch an unfamiliar copy just to see what it does. A Microsoft-looking filename is easy to imitate, while an expected folder and a valid signature are useful checks rather than a complete assessment of the computer.

Keep three components separate: msedge.exe is the browser, msedgewebview2.exe belongs to the embedded WebView2 runtime, and MicrosoftEdgeUpdate.exe is the updater. Their version numbers are not interchangeable. If your problem is CPU use by the runtime, use the WebView2 safety and high-CPU guide.

Installation scope matters, too. An installation for your Windows account uses different diagnostic locations from one installed for all users. Do not decide that a missing machine-wide log means the updater is fake; first check whether you are looking at the correct scope.

Repair a recurring update failure safely

Save your work and restart Windows once if an installation or system restart is pending. Check that the system drive has room for an update and that the connection works. Close Edge and the applications you can safely close before retrying. Microsoft lists locked components, permissions and network problems among the possible update failure causes; these are branches to investigate, not a diagnosis based on the filename. [3]

On a personal Windows PC, use the supported Edge repair path if the browser remains broken:

1. Close Edge for every signed-in user.
2. Open Settings → Apps → Installed apps → Microsoft Edge → Modify.
3. With an internet connection and administrator permission, select Repair. Microsoft says repair should preserve browser data and settings. [2]
4. Open About Edge again and record the result. Success means the update check completes and any required restart is finished; merely closing an error dialog does not establish success.

If Modify is unavailable on a work or school device, contact IT. Do not bypass management policies, set permanent antivirus exclusions, download a replacement EXE from a file catalogue, or remove EdgeUpdate services and scheduled tasks. If a security tool explicitly blocks a verified Microsoft file, preserve the alert and ask the administrator or vendor to investigate that specific block.

If repair fails, avoid repeating it without learning anything new. Use this short worksheet for the next attempt:

• Before: Windows version, Edge browser version, exact About-page status, updater file version and full path.
• Attempt: action taken and local time, including whether Windows or only Edge was restarted.
• After: About-page status and version, any new error code, and the matching event timestamp.

For example, an unchanged version plus “up to date” can be normal. An unchanged version after an offered update, followed by the same installation error, is useful evidence of a failed attempt. Keep those two outcomes separate when describing the problem.

Collect the log that matches your installation

For persistent failures, Microsoft documents these locations. Paste the appropriate path into File Explorer; the percent-wrapped names are Windows environment variables. [3]

• All-users update log: %ALLUSERSPROFILE%\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log
• Current-user update log: %LOCALAPPDATA%\Temp\MicrosoftEdgeUpdate.log
• All-users installer log: %WINDIR%\Temp\msedge_installer.log
• Current-user installer log: %LOCALAPPDATA%\Temp\msedge_installer.log

Use entries around the recorded attempt, not an unrelated old error somewhere in the file. On a managed device, send IT the worksheet and the matching logs through an approved support channel. A policy export from edge://policy may also help. Review diagnostic files before sharing them publicly because they can contain device, account or network details.

If the file looks suspicious

A copy arriving with an unknown installer, a signature that fails validation, or recurring security-tool alerts deserves a separate malware check. Stop using the unknown download and follow the EXE verification guide. Do not allow a detected file solely because it uses Microsoft’s updater name.

If a suspicious installer already ran, deleting that one download may leave other components or startup entries behind. Download and install Gridinsoft Anti-Malware, update its database, run a Full Scan, review the detections, apply cleanup and restart. Then recheck both the original symptom and About Edge. A scan can help find malicious components; it is not a repair for every legitimate updater error and cannot prove that no compromise occurred.

Should you disable MicrosoftEdgeUpdate.exe?

Permanent disabling is a poor fix for a crashing updater: it can stop the error-producing activity while leaving updates unfinished. Not using Edge as your default browser does not make the WebView2 runtime unnecessary for other applications. Keep the legitimate update mechanism enabled, verify the actual outcome, and escalate a reproducible failure with its logs rather than treating a quieter event history as a repaired PC.

References

1. Microsoft. Microsoft Edge update settings. Microsoft Support. Accessed September 30, 2026.
2. Microsoft. What to do if Microsoft Edge isn’t working. Microsoft Support. Accessed September 30, 2026.
3. Microsoft. Install, update, or roll back failures for Edge and Edge WebView2. Microsoft Learn. Updated January 28, 2026; accessed September 30, 2026.