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
Copy file name to clipboardExpand all lines: support/edge/manageability/update-install-rollback-failures.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.date: 01/07/2026
7
7
---
8
8
# Install, update, or rollback 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 issue 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 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.
11
11
12
12
The following components are involved in Edge installation and update scenarios:
13
13
@@ -56,7 +56,7 @@ You might also see one of the following error codes:
56
56
57
57
## Cause
58
58
59
-
Most Edge and WebView2 installation, update, and rollback failures are caused by one of the following issues:
59
+
Most Edge and WebView2 installation, update, and rollback failures happen because of one of the following problems:
60
60
61
61
- Permission restrictions
62
62
- Network or TLS issues
@@ -65,37 +65,37 @@ Most Edge and WebView2 installation, update, and rollback failures are caused by
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 are often causes of 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 install, update, or rollback failures.
69
69
70
70
## Solution
71
71
72
72
### Common troubleshooting checks
73
73
74
-
Before contacting Microsoft support, you should complete the following common troubleshooting checks. These steps resolve the majority of Microsoft Edge and Edge WebView2 update, installation, or rollback issues.
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.
75
75
76
76
#### Restart the device
77
77
78
-
A system restart clears temporary system states that may block Edge or Edge WebView2 updates.
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
82
- Complete any pending system reboot required by previous updates
83
83
- Release locked files used by Edge or Edge WebView2 processes
84
84
- Reset Windows Installer and related update services
85
85
86
-
After restarting, ensure no Edge or Edge WebView2-based applications are running before retrying the install, update, or rollback operation.
86
+
After restarting, make sure no Edge or Edge WebView2-based applications are running before retrying the install, update, or rollback operation.
87
87
88
88
#### Verify available disk space
89
89
90
-
Insufficient disk space may 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 install, update, or rollback failures. During installation, setup packages need temporary space to extract files and complete the process.
91
91
92
92
_Recommended_: At least 1-2 GB of free disk space on the system drive (usually `C:`).
93
93
94
94
1. Open **File Explorer**.
95
95
1. Check the available space on the system drive.
96
96
1. Free up disk space if needed (for example, remove temporary files or unused applications).
97
97
98
-
#### 3. Run installation as an administrator
98
+
#### Run installation as an administrator
99
99
100
100
Edge and Edge WebView2 install, update, and rollback operations require administrative privileges to:
101
101
@@ -110,13 +110,13 @@ To run the install, update, or rollback as an 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, ensure the account used has local administrator permissions.
113
+
> On managed or enterprise devices, make sure 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 may lock files required during install, update, or rollback operations.
117
+
Running Edge or Edge WebView2-based applications might lock files required during install, update, or rollback operations.
118
118
119
-
Common WebView2-based applications include (but are not limited to):
119
+
Common WebView2-based applications include (but aren't limited to):
> Follow your organization's security policies. If disabling security software is not allowed, contact your IT administrator for assistance.
140
+
> Follow your organization's security policies. If disabling security software isn't allowed, contact your IT administrator for assistance.
141
141
142
-
Some third-party antivirus, endpoint protection, or application control solutions may block:
142
+
Some third-party antivirus, endpoint protection, or application control solutions block:
143
143
144
144
- Installer execution (for example, `msedgeupdate.exe`, `msiexec.exe`)
145
145
- File replacement during update or rollback
146
146
- Service registration or scheduled task creation
147
147
148
148
Follow these steps:
149
149
150
-
1. Temporarily disable third-party security software, if permitted by organizational policy.
150
+
1. Temporarily disable third-party security software, if your organizational policy permits.
151
151
1. Retry the installation or update.
152
152
1. Re-enable security software immediately after completion.
153
153
154
154
### Contact support
155
155
156
-
If the steps in [Common troubleshooting checks](#common-troubleshooting-checks)do not 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. Then, submit them to the Microsoft Support Team for analysis:
157
157
158
158
- Edge installation and update logs
159
159
- Edge policy JSON export
@@ -216,15 +216,15 @@ Follow these steps to collect a Process Monitor log:
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
217
218
218
1. Select the **Capture** icon again to start monitoring.
219
-
1. Retry the install, update, or rollback process to reproduce the issue.
220
-
1.Once the issue occurs, select the **Capture** icon again to stop monitoring.
219
+
1. Retry the install, update, or rollback process to reproduce the problem.
220
+
1.When the problem occurs, select the **Capture** icon again to stop monitoring.
221
221
1. Save the log file:
222
222
1. Go to **File** > **Save**.
223
223
1. In the dialog, select:
224
224
225
225
-**Events to save**: _All events_
226
226
-**Format**: _Native Process Monitor Format (PML)_
227
-
-**Path**: Choose the desired folder to save the log file
227
+
-**Path**: Choose the folder where you want to save the log file
0 commit comments