Install, update, or roll back failures for Edge and Edge WebView2

Summary

When you install, update, or roll back Microsoft Edge or Microsoft Edge WebView2, you might encounter a problem that prevents the operation from completing. Common symptoms include the installation stopping or rolling back unexpectedly, the version not changing after an update, the Edge WebView2 Runtime being removed, silent installation failures with no UI or error prompt, or MSI errors. This article provides common troubleshooting steps to help you resolve these issues. If those steps don't resolve the problem, this article also explains how to collect diagnostic information to submit to the Microsoft Support Team for further analysis.

The following components are involved in Edge installation and update scenarios.

Symptoms

You experience one or more of the following symptoms:

• Edge or Edge WebView2 installation stops responding or rolls back.
• The installation finishes, but the version doesn't change.
• Edge WebView2 Runtime is missing or unexpectedly removed.
• Edge Update service retries repeatedly.
• Silent installation fails and returns no UI or error prompt.
• Edge automatically rolls back to an older version.
• The application doesn't start after an Edge WebView2 downgrade.
• MSI errors occur during rollback.
• Edge doesn't start after a rollback.

You might also see one of the following error codes.

Installer or MSI errors

Edge Update errors

Cause

Most Edge and WebView2 installation, update, and rollback failures occur because of one of the following problems:

• Permission restrictions
• Network or TLS issues
• Security software interference
• System component corruption
• Residual installation artifacts

Solution

Common troubleshooting checks

Before you contact Microsoft Support, complete the following common troubleshooting checks. These steps resolve most Microsoft Edge and Edge WebView2 installation, update, and rollback problems.

Restart the device

A system restart clears temporary system states that might block Edge or Edge WebView2 updates.

Restarting the device helps to:

• Complete any pending system restart that's required by previous updates
• Release locked files that are used by Edge or Edge WebView2 processes
• Reset Windows Installer and related update services

After a restart, make sure that no Edge or Edge WebView2-based applications are running before you try the installation, update, or rollback operation again.

Verify available disk space

Insufficient disk space might cause Edge or Edge WebView2 installation, update, or rollback failures. During installation, setup packages need temporary space to extract files and complete the process.

Recommended: At least 1-2 GB of free disk space on the system drive (usually drive C).

1. Open File Explorer.
2. Check the available space on the system drive.
3. Free up disk space if it's necessary (for example, remove temporary files or unused applications).

Run installation as an administrator

Edge and Edge WebView2 installation, update, and rollback operations require administrative privileges to:

• Write to system directories (for example, Program Files)
• Register system components
• Modify services and scheduled tasks

To run the installation, update, or rollback process as an administrator:

1. Right-click the installer file (.exe or .msi).
2. Select Run as administrator.
3. Approve the User Account Control (UAC) prompt.

Close Edge and Edge WebView2-based applications

Running Edge or Edge WebView2-based applications might lock files that are required during installation, update, or rollback operations.

Common WebView2-based applications include (but aren't limited to):

• Microsoft Edge
• Microsoft Teams
• Outlook (new client)
• Windows Widgets
• Custom line-of-business applications

Follow these steps:

1. Close all open applications.
2. Open Task Manager.
3. Verify that there are no running processes such as:
   • msedge.exe
   • msedgewebview2.exe
4. End any remaining processes, if it's necessary.
5. Retry the installation, update, or rollback operation.

Temporarily disable third-party security software (if applicable)

Some third-party antivirus, endpoint protection, or application control solutions block the following actions:

• Installer execution (for example, msedgeupdate.exe, msiexec.exe)
• File replacement during an update or rollback operation
• Service registration or scheduled task creation

Follow these steps:

1. Temporarily disable third-party security software, if your organizational policy permits.
2. Retry the installation or update.
3. Re-enable security software immediately after completion.

Additional support

If the resources on the support page don't help resolve your issue, you can create a Microsoft support request. When you create a support request, collect and package the following diagnostic logs to attach to your request:

• Edge installation and update logs
• Edge policy JSON export
• Process Monitor (PML) log

Use the steps in the following sections to collect these logs and submit a support ticket.

Collect Edge installation and update logs

Collect logs from the following locations, based on your installation type:

Update logs

• If Edge is installed for all users:

  %ALLUSERSPROFILE%\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log

• If Edge is installed for only you:

  %LOCALAPPDATA%\Temp\MicrosoftEdgeUpdate.log

Installation logs

• If Edge is installed for all users:

  %WINDIR%\Temp\msedge_installer.log

• If Edge is installed for only you:

  %LOCALAPPDATA%\Temp\msedge_installer.log

Export Edge policy settings

To export the Edge policy information, follow these steps:

1. Open Microsoft Edge, and browse to edge://policy.
2. Select Export to JSON.
3. Save the exported JSON file.

Collect a Process Monitor log

Process Monitor is a Windows monitoring tool that captures real-time file system, registry, and process and thread activity.

To collect a Process Monitor log, follow these steps:

1. Download Process Monitor, and expand it.

2. Run Procmon.exe.

3. When Process Monitor starts, data capture begins automatically. To stop the initial capture, select the Capture icon on the toolbar.

   

4. Go to Edit > Clear Display to clear existing data.

   

5. To capture all activity types, make sure that the following options are enabled:

   • File System
   • Registry
   • Process/Thread
   • Network

   

6. To start monitoring, select the Capture icon again.

7. Reproduce the problem by retrying the installation, update, or rollback process.

8. When the problem occurs, select the Capture icon again to stop monitoring.

9. Save the log file:

   1. Go to File > Save.

   2. In the dialog box, select:

      • Events to save: All events
      • Format: Native Process Monitor Format (PML)
      • Path: Choose the folder where you want to save the log file

Submit the diagnostic package

To get help from Microsoft Support, follow these steps:

1. Package all the collected diagnostic logs into a single compressed folder (for example, a .zip file).
2. Go to the Microsoft Edge Support page, and create a support ticket.
3. When you create the support ticket, attach the packaged diagnostic logs so the support team can analyze them and help you resolve the problem.

Related content

• Sysinternals
• Troubleshooting with the Windows Sysinternals Tools