You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Troubleshoot Edge Update, Installation, and Rollback Failures
3
-
description: Learn how to troubleshoot and resolve installation, update, or rollback failures for Microsoft Edge and Edge WebView2 with step-by-step guidance.
3
+
description: Learn how to troubleshoot and resolve installation, update, or roll back failures for Microsoft Edge and Edge WebView2.
4
4
ms.custom: 'sap:Manageability and Deployment\Installation, Update, Removal, Rollback'
5
5
ms.reviewer: dili, Johnny.Xu, v-shaywood
6
6
ms.date: 01/07/2026
7
7
---
8
-
# Install, update, or rollback failures for Edge and Edge WebView2
8
+
# Install, update, or roll back failures for Edge and Edge WebView2
9
9
10
-
When you install, update, or rollback Microsoft Edge or Microsoft Edge WebView2, you might encounter an problem that prevents the operation from completing. This article helps you collect the diagnostic information the [Microsoft Support Team](TODO) needs to analyze and help resolve the problem.
10
+
When you install, update, or roll back Microsoft Edge or Microsoft Edge WebView2, you encounter a problem that prevents the operation from finishing. This article helps you collect the diagnostic information that the [Microsoft Support Team](TODO) needs to analyze and help resolve the problem.
11
11
12
-
The following components are involved in Edge installation and update scenarios:
12
+
The following components are involved in Edge installation and update scenarios.
Most Edge and WebView2 installation, update, and rollback failures happen because of one of the following problems:
59
+
Most Edge and WebView2 installation, update, and rollback failures occur because of one of the following problems:
60
60
61
61
- Permission restrictions
62
62
- Network or TLS issues
@@ -65,56 +65,56 @@ Most Edge and WebView2 installation, update, and rollback failures happen becaus
65
65
- Residual installation artifacts
66
66
67
67
> [!NOTE]
68
-
> In enterprise environments, [Group Policy Object (GPO)](/windows-server/identity/ad-ds/manage/group-policy/group-policy-overview), [Mobile Device Management (MDM)](/windows/client-management/mdm-overview), and security policies often cause install, update, or rollback failures.
68
+
> In enterprise environments, [Group Policy Object (GPO)](/windows-server/identity/ad-ds/manage/group-policy/group-policy-overview), [Mobile Device Management (MDM)](/windows/client-management/mdm-overview), and security policies often cause installation, update, or rollback failures.
69
69
70
70
## Solution
71
71
72
72
### Common troubleshooting checks
73
73
74
-
Before contacting Microsoft support, complete the following common troubleshooting checks. These steps resolve most Microsoft Edge and Edge WebView2 update, installation, or rollback problems.
74
+
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.
75
75
76
76
#### Restart the device
77
77
78
78
A system restart clears temporary system states that might block Edge or Edge WebView2 updates.
79
79
80
80
Restarting the device helps to:
81
81
82
-
- Complete any pending system reboot required by previous updates
83
-
- Release locked files used by Edge or Edge WebView2 processes
82
+
- Complete any pending system restart that's required by previous updates
83
+
- Release locked files that are used by Edge or Edge WebView2 processes
84
84
- Reset Windows Installer and related update services
85
85
86
-
After restarting, make sure no Edge or Edge WebView2-based applications are running before retrying the install, update, or rollback operation.
86
+
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.
87
87
88
88
#### Verify available disk space
89
89
90
-
Insufficient disk space might cause Edge or Edge WebView2 install, update, or rollback failures. During installation, setup packages need temporary space to extract files and complete the process.
90
+
Insufficient disk space might cause Edge or Edge WebView2 installaion, update, or rollback failures. During installation, setup packages need temporary space to extract files and complete the process.
91
91
92
-
_Recommended_: At least 1-2 GB of free disk space on the system drive (usually `C:`).
92
+
_Recommended_: At least 1-2 GB of free disk space on the system drive (usually `drive C`).
93
93
94
94
1. Open **File Explorer**.
95
95
1. Check the available space on the system drive.
96
-
1. Free up disk space if needed (for example, remove temporary files or unused applications).
96
+
1. Free up disk space if it's necessary (for example, remove temporary files or unused applications).
97
97
98
98
#### Run installation as an administrator
99
99
100
-
Edge and Edge WebView2 install, update, and rollback operations require administrative privileges to:
100
+
Edge and Edge WebView2 installation, update, and rollback operations require administrative privileges to:
101
101
102
102
- Write to system directories (for example, `Program Files`)
103
103
- Register system components
104
104
- Modify services and scheduled tasks
105
105
106
-
To run the install, update, or rollback as an administrator:
106
+
To run the installation, update, or rollback process as an administrator:
107
107
108
108
1. Right-click the installer file (`.exe` or `.msi`).
109
109
1. Select **Run as administrator**.
110
110
1. Approve the [User Account Control (UAC)](/windows/security/application-security/application-control/user-account-control/) prompt.
111
111
112
112
> [!NOTE]
113
-
> On managed or enterprise devices, make sure the account you use has local administrator permissions.
113
+
> On managed or enterprise devices, make sure that the account you use has local administrator permissions.
114
114
115
115
#### Close Edge and Edge WebView2-based applications
116
116
117
-
Running Edge or Edge WebView2-based applications might lock files required during install, update, or rollback operations.
117
+
Running Edge or Edge WebView2-based applications might lock files that are required during installation, update, or rollback operations.
118
118
119
119
Common WebView2-based applications include (but aren't limited to):
120
120
@@ -128,21 +128,21 @@ Follow these steps:
128
128
129
129
1. Close all open applications.
130
130
1. Open **Task Manager**.
131
-
1.Confirm there are no running processes such as:
131
+
1.Verify that there are no running processes such as:
132
132
-`msedge.exe`
133
133
-`msedgewebview2.exe`
134
-
1. End any remaining processes if necessary.
135
-
1. Retry the install, update, or rollback operation.
134
+
1. End any remaining processes, if it's necessary.
135
+
1. Retry the installation, update, or rollback operation.
> Follow your organization's security policies. If disabling security software isn't allowed, contact your IT administrator for assistance.
140
+
> Follow your organization's security policies. If the policies don't allow you to disable security software, contact your IT administrator for assistance.
141
141
142
-
Some third-party antivirus, endpoint protection, or application control solutions block:
142
+
Some third-party antivirus, endpoint protection, or application control solutions block the following actions:
143
143
144
144
- Installer execution (for example, `msedgeupdate.exe`, `msiexec.exe`)
145
-
- File replacement during update or rollback
145
+
- File replacement during an update or rollback operation
146
146
- Service registration or scheduled task creation
147
147
148
148
Follow these steps:
@@ -153,23 +153,23 @@ Follow these steps:
153
153
154
154
### Contact support
155
155
156
-
If the steps in [Common troubleshooting checks](#common-troubleshooting-checks) don't resolve your problem, collect and package the following diagnostic logs. Then, submit them to the Microsoft Support Team for analysis:
156
+
If the steps in [Common troubleshooting checks](#common-troubleshooting-checks) don't resolve your problem, collect and package the following diagnostic logs, and then, submit them to Microsoft Support for analysis:
157
157
158
158
- Edge installation and update logs
159
159
- Edge policy JSON export
160
160
- Process Monitor (PML) log
161
161
162
162
#### Collect Edge installation and update logs
163
163
164
-
Collect logs from the following locations based on your installation type:
164
+
Collect logs from the following locations, based on your installation type:
@@ -179,58 +179,59 @@ Collect logs from the following locations based on your installation type:
179
179
180
180
`%WINDIR%\Temp\msedge_installer.log`
181
181
182
-
- If Edge is installed for just you:
182
+
- If Edge is installed for only you:
183
183
184
184
`%LOCALAPPDATA%\Temp\msedge_installer.log`
185
185
186
186
#### Export Edge policy settings
187
187
188
-
Follow these steps to export the Edge policy information:
188
+
To export the Edge policy information, follow these steps:
189
189
190
-
1. Open Microsoft Edge and go to `edge://policy`.
190
+
1. Open Microsoft Edge, and browse to `edge://policy`.
191
191
1. Select **Export to JSON**.
192
192
1. Save the exported JSON file.
193
193
194
194
#### Collect a Process Monitor log
195
195
196
-
[Process Monitor](/sysinternals/downloads/procmon) is a Windows monitoring tool that captures real-time file system, registry, and process/thread activity.
196
+
[Process Monitor](/sysinternals/downloads/procmon) is a Windows monitoring tool that captures real-time file system, registry, and process and thread activity.
197
197
198
-
Follow these steps to collect a Process Monitor log:
198
+
To collect a Process Monitor log, follow these steps:
199
199
200
-
1. Download [Process Monitor](/sysinternals/downloads/procmon) and unzip it.
200
+
1. Download [Process Monitor](/sysinternals/downloads/procmon), and expand it.
201
201
1. Run `Procmon.exe`.
202
-
1. When Process Monitor starts, data capture begins automatically. Select the **Capture** icon in the toolbar to stop the initial capture.
202
+
1. When Process Monitor starts, data capture begins automatically. To stop the initial capture, select the **Capture** icon on the toolbar.
203
203
204
-
:::image type="content" source="./media/update-install-rollback-failures/procmon-capture-icon.png" alt-text="Screenshot of Process Monitor with the Capture button highlighted.":::
204
+
:::image type="content" source="./media/update-install-rollback-failures/procmon-capture-icon.png" alt-text="Process Monitor showing the Capture button highlighted.":::
205
205
206
206
1. Go to **Edit** > **Clear Display** to clear existing data.
207
207
208
208
:::image type="content" source="./media/update-install-rollback-failures/procmon-clear-display.png" alt-text="Screenshot of Process Monitor with the Clear Display option highlighted.":::
209
209
210
-
1. Make sure the following options are enabled to capture all activity types:
210
+
1. To capture all activity types, make sure that the following options are enabled:
211
+
211
212
- File System
212
213
- Registry
213
214
- Process/Thread
214
215
- Network
215
216
216
-
:::image type="content" source="./media/update-install-rollback-failures/procmon-activity-types.png" alt-text="Screenshot of Process Monitor with the File System, Registry, Process/Thread, and Network activity types selected.":::
217
+
:::image type="content" source="./media/update-install-rollback-failures/procmon-activity-types.png" alt-text="Process Monitor showing the File System, Registry, Process/Thread, and Network activity types selected.":::
217
218
218
-
1.Select the **Capture** icon again to start monitoring.
219
-
1.Retry the install, update, or rollback process to reproduce the problem.
219
+
1.To start monitoring, select the **Capture** icon again.
220
+
1.Reproduce the problem by retrying the installation, update, or rollback process.
220
221
1. When the problem occurs, select the **Capture** icon again to stop monitoring.
221
222
1. Save the log file:
222
223
1. Go to **File** > **Save**.
223
-
1. In the dialog, select:
224
+
1. In the dialog box, select:
224
225
225
226
-**Events to save**: _All events_
226
227
-**Format**: _Native Process Monitor Format (PML)_
227
228
-**Path**: Choose the folder where you want to save the log file
228
229
229
230
#### Submit the diagnostic package
230
231
231
-
After packaging the collected logs, submit the files to the [Microsoft Support Team](TODO). The support team will analyze the logs and help you resolve the problem.
232
+
After you package the collected logs, submit the files to the [Microsoft Support Team](TODO). The support team analyzes the logs and helps you resolve the problem.
232
233
233
234
## Related content
234
235
235
236
-[Sysinternals](/sysinternals)
236
-
-[Troubleshooting with the Windows Sysinternals Tools](/sysinternals/resources/troubleshooting-book)
237
+
-[Troubleshooting with the Windows Sysinternals Tools](/sysinternals/resources/troubleshooting-book)
0 commit comments