Microsoft features stopped working and Webview2 will not reinstall

The symptoms match a corrupted or partially removed Microsoft Edge WebView2 Runtime, where the system still believes WebView2 is installed but the binaries, registry entries, and EdgeUpdate folder are missing. This can break modern Microsoft apps that depend on WebView2.

Use the following steps to fully remove the broken WebView2 registration and then reinstall it cleanly.

1. Remove the stale WebView2 registration from the registry
2. Open Registry Editor (regedit.exe) as an administrator.
3. Navigate to the WebView2 client registration key (on 64-bit Windows):
   • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}
4. If the {F3017226-FE2A-4295-8BDF-00C3A9A7E4C5} key exists, delete that key.
5. Also check under:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}
   • HKEY_CURRENT_USER\Software\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5} and delete the key if present.

This removes the registration that can cause the installer to think WebView2 is already installed when the runtime is actually missing.

2. Ensure no WebView2 processes are running

Before reinstalling, make sure nothing is using WebView2:

1. Restart the device.
2. Open Task Manager.
3. On the Processes tab and Details tab, confirm there are no msedge.exe or msedgewebview2.exe processes.
4. If any are present, end those processes.
5. Temporarily disable third‑party security software (if applicable)

Security software can block WebView2 installation and updates.

1. If organizational or local security policy allows, temporarily disable any third‑party antivirus or endpoint protection.
2. Plan to re‑enable it immediately after WebView2 is installed.
3. Reinstall WebView2 Runtime using the standalone installer
4. Download the Evergreen Standalone x64 WebView2 Runtime installer from the official WebView2 download page.
5. Right‑click the installer and select Run as administrator.
6. Complete the installation.
7. Restart the device again.

After this clean reinstall, Microsoft 365 apps and other WebView2‑based applications should be able to start and render content normally.

5. If installation still fails

If the standalone installer still reports that WebView2 is already installed or fails silently after the registry cleanup:

1. Verify available disk space (at least 1–2 GB free on the system drive).
2. Confirm again that no WebView2‑based apps (such as Microsoft Teams, new Outlook, or Widgets) are running.
3. Collect diagnostic logs for Microsoft Support:
   • Edge/WebView2 installation and update logs from:
     • %WINDIR%\Temp\msedge_installer.log or %LOCALAPPDATA%\Temp\msedge_installer.log
     • %ALLUSERSPROFILE%\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log or %LOCALAPPDATA%\Temp\MicrosoftEdgeUpdate.log
   • Export Edge policy via edge://policy → Export to JSON.
   • Capture a Process Monitor (Procmon) log while reproducing the failed installation.
4. Package these logs and open a ticket via the Microsoft Edge Support page so the support team can analyze the environment‑specific cause.

References:

• WebView2 end-user FAQ
• Distribute your app and the WebView2 Runtime
• Install, update, or roll back failures for Edge and Edge WebView2
• Teams needs Edge WebView2 to be installed but installation fails, saying that the Runtime is already installed. - Microsoft Q&A
• Firmware updated caused microsoft office to stop working - Microsoft Q&A