Skip to content

Commit e07b8c6

Browse files
authored
Revise troubleshooting guide for Edge update failures
Updated the troubleshooting guide for Edge installation, update, and rollback failures to improve clarity and fix minor grammatical issues.
1 parent d0e9a22 commit e07b8c6

1 file changed

Lines changed: 50 additions & 49 deletions

File tree

Lines changed: 50 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
22
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.
44
ms.custom: 'sap:Manageability and Deployment\Installation, Update, Removal, Rollback'
55
ms.reviewer: dili, Johnny.Xu, v-shaywood
66
ms.date: 01/07/2026
77
---
8-
# Install, update, or rollback failures for Edge and Edge WebView2
8+
# Install, update, or roll back failures for Edge and Edge WebView2
99

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.
1111

12-
The following components are involved in Edge installation and update scenarios:
12+
The following components are involved in Edge installation and update scenarios.
1313

1414
| Component | Description |
1515
| --------------------- | ------------------------------- |
@@ -20,19 +20,19 @@ The following components are involved in Edge installation and update scenarios:
2020

2121
## Symptoms
2222

23-
You might experience one or more of the following symptoms:
23+
You experience one or more of the following symptoms:
2424

25-
- Edge or Edge WebView2 installation hangs or rolls back.
26-
- Installation completes but the version doesn't change.
25+
- Edge or Edge WebView2 installation stops responding or rolls back.
26+
- The installation finishes, but the version doesn't change.
2727
- Edge WebView2 Runtime is missing or unexpectedly removed.
2828
- Edge Update service retries repeatedly.
29-
- Silent installation fails with no UI or error prompt.
29+
- Silent installation fails and returns no UI or error prompt.
3030
- Edge automatically rolls back to an older version.
31-
- Application fails to start after Edge WebView2 downgrade.
31+
- The application doesn't start after an Edge WebView2 downgrade.
3232
- MSI errors occur during rollback.
33-
- Edge fails to launch after rollback.
33+
- Edge doesn't start after a rollback.
3434

35-
You might also see one of the following error codes:
35+
You might also see one of the following error codes.
3636

3737
### Installer or MSI errors
3838

@@ -52,11 +52,11 @@ You might also see one of the following error codes:
5252
| `0x80072EE7` | DNS resolution failure |
5353
| `0x80072EFE` | Network connection dropped |
5454
| `0x80072F8F` | TLS or certificate validation failure |
55-
| `0x80004005` | Unspecified error (usually environment-related) |
55+
| `0x80004005` | Unspecified error (usually environment related) |
5656

5757
## Cause
5858

59-
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:
6060

6161
- Permission restrictions
6262
- Network or TLS issues
@@ -65,56 +65,56 @@ Most Edge and WebView2 installation, update, and rollback failures happen becaus
6565
- Residual installation artifacts
6666

6767
> [!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.
6969
7070
## Solution
7171

7272
### Common troubleshooting checks
7373

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.
7575

7676
#### Restart the device
7777

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

8080
Restarting the device helps to:
8181

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
8484
- Reset Windows Installer and related update services
8585

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.
8787

8888
#### Verify available disk space
8989

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.
9191

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`).
9393

9494
1. Open **File Explorer**.
9595
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).
9797

9898
#### Run installation as an administrator
9999

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:
101101

102102
- Write to system directories (for example, `Program Files`)
103103
- Register system components
104104
- Modify services and scheduled tasks
105105

106-
To run the install, update, or rollback as an administrator:
106+
To run the installation, update, or rollback process as an administrator:
107107

108108
1. Right-click the installer file (`.exe` or `.msi`).
109109
1. Select **Run as administrator**.
110110
1. Approve the [User Account Control (UAC)](/windows/security/application-security/application-control/user-account-control/) prompt.
111111

112112
> [!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.
114114
115115
#### Close Edge and Edge WebView2-based applications
116116

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.
118118

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

@@ -128,21 +128,21 @@ Follow these steps:
128128

129129
1. Close all open applications.
130130
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:
132132
- `msedge.exe`
133133
- `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.
136136

137137
#### Temporarily disable third-party security software (if applicable)
138138

139139
> [!IMPORTANT]
140-
> 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.
141141
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:
143143

144144
- Installer execution (for example, `msedgeupdate.exe`, `msiexec.exe`)
145-
- File replacement during update or rollback
145+
- File replacement during an update or rollback operation
146146
- Service registration or scheduled task creation
147147

148148
Follow these steps:
@@ -153,23 +153,23 @@ Follow these steps:
153153

154154
### Contact support
155155

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:
157157

158158
- Edge installation and update logs
159159
- Edge policy JSON export
160160
- Process Monitor (PML) log
161161

162162
#### Collect Edge installation and update logs
163163

164-
Collect logs from the following locations based on your installation type:
164+
Collect logs from the following locations, based on your installation type:
165165

166166
##### Update logs
167167

168168
- If Edge is installed for all users:
169169

170170
`%ALLUSERSPROFILE%\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log`
171171

172-
- If Edge is installed for just you:
172+
- If Edge is installed for only you:
173173

174174
`%LOCALAPPDATA%\Temp\MicrosoftEdgeUpdate.log`
175175

@@ -179,58 +179,59 @@ Collect logs from the following locations based on your installation type:
179179

180180
`%WINDIR%\Temp\msedge_installer.log`
181181

182-
- If Edge is installed for just you:
182+
- If Edge is installed for only you:
183183

184184
`%LOCALAPPDATA%\Temp\msedge_installer.log`
185185

186186
#### Export Edge policy settings
187187

188-
Follow these steps to export the Edge policy information:
188+
To export the Edge policy information, follow these steps:
189189

190-
1. Open Microsoft Edge and go to `edge://policy`.
190+
1. Open Microsoft Edge, and browse to `edge://policy`.
191191
1. Select **Export to JSON**.
192192
1. Save the exported JSON file.
193193

194194
#### Collect a Process Monitor log
195195

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.
197197

198-
Follow these steps to collect a Process Monitor log:
198+
To collect a Process Monitor log, follow these steps:
199199

200-
1. Download [Process Monitor](/sysinternals/downloads/procmon) and unzip it.
200+
1. Download [Process Monitor](/sysinternals/downloads/procmon), and expand it.
201201
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.
203203

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.":::
205205

206206
1. Go to **Edit** > **Clear Display** to clear existing data.
207207

208208
:::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.":::
209209

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+
211212
- File System
212213
- Registry
213214
- Process/Thread
214215
- Network
215216

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.":::
217218

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.
220221
1. When the problem occurs, select the **Capture** icon again to stop monitoring.
221222
1. Save the log file:
222223
1. Go to **File** > **Save**.
223-
1. In the dialog, select:
224+
1. In the dialog box, select:
224225

225226
- **Events to save**: _All events_
226227
- **Format**: _Native Process Monitor Format (PML)_
227228
- **Path**: Choose the folder where you want to save the log file
228229

229230
#### Submit the diagnostic package
230231

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.
232233

233234
## Related content
234235

235236
- [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

Comments
 (0)