ArcGIS Pro requires Microsoft Edge Webview2 but it is already installed

[WoodRiverWolfProj]

Hey all,

I am trying to install ArcGIS Pro onto a fairly old computer running Windows 10. Initially, when I tried to run the installer I could get through the initial step of creating a file location for ArcGIS, then I would get the message that "ArcGIS Pro requires Microsoft Edge Webview2 Runtime x64" and could proceed no further with the installation. I checked that the webview2 application is installed on my computer and Windows is fully updated. Also tried to install Webview2 using the standalone installer and it says that Webview2 is already installed on my computer. Next I fully removed Webview2 and Microsoft Edge from my computer and downloaded both again. This time, I was able to fully install ArcGIS Pro to the point where it starts to launch, only to get the same message. Does anyone know why ArcGIS is not able to use Webview2 and how I can troubleshoot this?

[DanPatterson]

something to check, although not much is referenced about webview2 in the support site

How To: Configure the ArcGIS pro Chromium WebView2 Control to Use the WebView2 Evergreen R

[ChelseaRozek]

Hopefully this can help someone else: I was having the same issue, but running the webview2 installer again as an administrator got it to work. Per the documentation: "A per-machine installation (the default) of ArcGIS Pro requires a per-machine installation of WebView2 Runtime. To do this, right-click the WebView2 installer and click Run as administrator."

[RichardDaniels]

We ran into a similar issue with updating machines for ArcGIS Pro 3.4 to 3.5, the solution as stated above is to download and install the newest available version of Microsoft Edge WebView2 runtime (x64) 'as administrator'. However, of NOTE is on March 12, 2026 Microsoft released an update for 80 issues, then then released a new version on March 20th and March 23rd. Usually they only have 1 release per month. This means the 20th edition 146.0.3856.72 had a significant 'problem'. If you have this installed version, update to build 146.0.3865.78 or higher then retry your ArcGIS Pro installation.

To check your version in regEdit see HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientState and look in each subkey. Version 78 has a subkey of . \ClientState\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}

[RichardDaniels · Accepted solution]

After days I tracked down our environment. Microsoft Edge Browser includes WebView2 controls and IT Admin's falsely believe this meets the requirements for WebView2. However, the Microsoft .NET WebView2 Runtime is NOT the same as the WebView2 control deployed with Edge (and part of the Edge stable release updates). The runtime can be several releases ahead of the browser's version of the control. Because of this, we should be using the WebView2 Runtime installers, Evergreen version preferred, available at Microsoft Edge WebView2 | Microsoft Edge Developer.

[RichardDaniels]

Hopefully the following issue is resolved at ArcGIS Pro 3.6, but we had 100 machines out of 900 that would not install and showed the WebView2 error (as well as the .Net Desktop Runtime 8.0.x error in sequence). I believe the errors being shown are actually in reverse order to what one expect. For example, order of errors shown is WebView2, .Net Desktop Runtime, older version of software installed but cannot be removed.

We made several hacks to the ArcGIS Pro.msi to address this, but as a last resort on a known-bad machine we ran the following command to get Verbose logs.

To include additional debugging details and flush every line to the log immediately (useful if the installer crashes), use:
msiexec /i "C:\path\to\ArcGIS Pro.msi" /L*vx! "C:\path\to\install.log"

In this log we found that 

The UI (client) sequence custom action CheckforDotNetWindowsDesktopRuntime does find the Desktop Runtime 8.0.25 and sets DOTNETDESKTOPRUNTIME_FOUND=TRUE:

Microsoft.WindowsDesktop.App 8.0.25 [...]

.NET requirement has been met.

PROPERTY CHANGE: ... DOTNETDESKTOPRUNTIME_FOUND ... 'TRUE'

However, when the install moves to the server (execute) sequence, Windows Installer doesn’t carry over that property. This means the property set in the UI sequence is not secure and therefore not visible to the execute sequence, so the server-side detection decides the prereq is missing even though the runtime exists. This is standard MSI behavior unless the property is listed in SecureCustomProperties or passed via CustomActionData for deferred CAs. (The symptom and cause are consistent with MSI property scoping rules.)

Our Solution? Edit the ArcGIS Pro. msi and change the default value of the DOTNETDESKTOPRUNTIME_FOUND property to TRUE (this is found in the properties table in the msi).