Fix New Outlook WebView2 Error | Autopilot & Intune Guide

Fix “Microsoft Outlook Needs to Update a Dependency” on Autopilot Devices

• Why This Happens

  The New Outlook for Windows is built on Microsoft Edge WebView2. If the Evergreen WebView2 Runtime is missing, outdated, or corrupted, Outlook cannot render its UI and shows a dependency prompt. Microsoft recommends the Evergreen model, which auto‑updates and is shared across apps for reduced footprint and maintenance. [1](https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution)[2](https://developer.microsoft.com/en-gb/microsoft-edge/webview2?form=ML2F1I)

  Learn more about runtime distribution options and best practices for enterprise deployment. [3](https://learn.microsoft.com/en-us/microsoft-edge/webview2/samples/wv2deploymentvsinstallersample)

  End‑User Fix Steps

  1. Click “OK” → Allow the installation when prompted (UAC may appear).
  2. Run Windows Update: Settings → Windows Update → Check for updates, install all patches, reboot.
  3. If no admin rights: contact IT to install the Microsoft Edge WebView2 Runtime (Evergreen).
  4. Manual install (optional): download the Evergreen Standalone installer from Microsoft and run it, then relaunch Outlook. [1](https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution)
  5. Restart Outlook: close completely, toggle Try the new Outlook, relaunch.

  IT Admin Deployment (Autopilot & Intune)

  Recommended: deploy the Evergreen WebView2 Runtime as a required app during Autopilot so devices are ready on first sign‑in. [3](https://learn.microsoft.com/en-us/microsoft-edge/webview2/samples/wv2deploymentvsinstallersample)

  Silent Install

  MicrosoftEdgeWebview2Setup.exe /silent /install
  

  Winget Automation

  winget install --id Microsoft.EdgeWebView2Runtime -e --silent
  

  Intune Detection Rule

  %ProgramFiles(x86)%\Microsoft\EdgeWebView\Application\*\msedgewebview2.exe
  

  Verify Runtime Version (PowerShell)

  $paths = @(
    "$Env:ProgramFiles(x86)\Microsoft\EdgeWebView\Application\msedgewebview2.exe",
    "$Env:ProgramFiles\Microsoft\EdgeWebView\Application\msedgewebview2.exe"
  )
  $paths | Where-Object { Test-Path $_ } | ForEach-Object {
    (Get-Item $_).VersionInfo | Select-Object FileName, ProductVersion
  }
  

  Evergreen is the default/proven approach for most orgs; Fixed Version is for strict version‑locking scenarios only. [2](https://developer.microsoft.com/en-gb/microsoft-edge/webview2?form=ML2F1I)

  Can Windows Update Fix This?

  Often, yes. Keeping Windows and Edge serviced ensures the WebView2 runtime remains compatible and current. Many environments see resolution after installing pending updates and rebooting. Evergreen runtime servicing aligns closely with Edge’s cadence and benefits from automatic updates on supported devices. [2](https://developer.microsoft.com/en-gb/microsoft-edge/webview2?form=ML2F1I)

  Still Failing? Try These

  • Repair Microsoft 365 Apps: Settings → Apps → Microsoft 365 → Modify → Quick Repair.
  • Update or Repair Edge: edge://settings/help or Control Panel → Repair.
  • Check security controls: ensure endpoint policies aren’t blocking WebView2 install/updates.

  FAQ

  Why does New Outlook need WebView2?
  It embeds modern web content with Edge’s engine for feature velocity and consistency with Outlook on the web. [3](https://learn.microsoft.com/en-us/microsoft-edge/webview2/samples/wv2deploymentvsinstallersample)

  Do I need WebView2 for Outlook in the browser?
  No. Outlook on the web runs inside your browser and doesn’t require the runtime. [3](https://learn.microsoft.com/en-us/microsoft-edge/webview2/samples/wv2deploymentvsinstallersample)

  Evergreen vs Fixed Version?
  Evergreen auto‑updates (recommended) while Fixed Version locks to a specific build for compatibility control. [2](https://developer.microsoft.com/en-gb/microsoft-edge/webview2?form=ML2F1I)