[Problem/Bug]: Webview2 installation via Evergreen Bootstrapper not working on multiple machines

What happened?

Hi,
I am trying to install Webview2 on users machine via the Evergreen Bootstrapper(https://go.microsoft.com/fwlink/p/?LinkId=2124703). But for a lot of users we are seeing errors.

The top errors are:

1. HTTP 403 (GOOPDATE_E_NETWORK_FORBIDDEN) — 75.3%
2. 0xA0430729 — 8.2%
3. Connection aborted — 4.2%
4. Captive portal — 2.4%
5. Request timeout — 2.2%

The most affected OS versions are Windows 10 21H2, 1809/Server 2019, 22H2, 1607/Server 2016, and 1709.
We’d appreciate your guidance on a few points:

• Are the 403 errors or 0xA0430729 associated with any known WebView2/EdgeUpdate server-side or OS-specific restrictions, or are they more likely caused by client-side network, proxy, or firewall configurations?

• Do these errors primarily indicate that the Evergreen Bootstrapper is unable to download the WebView2 Runtime, or could they also indicate that the Runtime itself cannot be installed on these machines?

• As a fallback, we’re considering using the Evergreen Standalone Installer. Would you expect the standalone installer to resolve most of these cases, particularly the 403/download-related failures? Are there specific OS versions or error scenarios where the standalone installer would likely fail as well?

Any help is really appreciated. Thanks in advance.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

No response

SDK Version

No response

Framework

Win32

Operating System

Windows 10

OS Version

No response

Repro steps

Try installing via webview2 via Evergreen Bootstrapper(https://go.microsoft.com/fwlink/p/?LinkId=2124703).

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

Start with the Evergreen Bootstrapper linked in the issue and reproduce the reported installation failures on the listed Windows versions. Compare the HTTP 403, 0xA0430729, connection, captive-portal, and timeout cases with the Evergreen Standalone Installer. Done would require determining whether the failures are download or installation related and documenting the affected scenarios.