Microsoft Edge Webview2 Runtime: Offline Installer Repack

The official offline installer supports these critical switches:

Create a batch file or PowerShell script called Deploy-WebView2.ps1:

# Check if already installed
$check = Get-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\F3017226-FE2A-4295-8BDF-00C3A9A7E4C5" -Name "pv" -ErrorAction SilentlyContinue
if ($check.pv -ge "118.0.2088.76") 
    Write-Host "WebView2 version requirement already met. Exiting."
    exit 0
The "Microsoft Edge WebView2 Runtime Offline Installer Repack" is essentially a solution to a deployment convenience problem. While Microsoft provides all the necessary files for free via the Fixed Version download, the lack of a standard "one-click" offline MSI leads users to seek repacks.
For the most secure and stable environment, administrators should utilize the official Fixed Version binaries and script the installation to ensure compatibility with their specific software requirements.
Repackaging the Microsoft Edge WebView2 Runtime is a common task for IT administrators who need to deploy the component in restricted, offline, or enterprise environments where the standard bootstrapper cannot reach Microsoft's servers. 1. Official Offline Installer Acquisition
The first step in any repackaging process is obtaining the correct source file. Microsoft provides two main "Evergreen" options for the WebView2 Runtime:
Evergreen Bootstrapper: A tiny (~2MB) file that downloads the runtime during installation. Not suitable for offline repackaging.
Evergreen Standalone Installer: A complete installer package (approx. 150MB+) that includes all necessary files for a specific architecture (x64, x86, or ARM64). This is the required source for an offline repack. 2. Silent Installation Switches
To "repack" or wrap the installer for silent deployment via tools like SCCM, Intune, or custom scripts, use the following command-line switches with the Standalone Installer:
/silent: Runs the installation without showing a user interface.
/install: Commands the executable to perform the installation.
Elevation: Running these from an elevated command prompt (Administrator) ensures a per-machine installation, which is standard for enterprise environments. 3. Repackaging Methods
Depending on your deployment tool, "repackaging" typically follows one of these workflows: Wrapping for Microsoft Intune (Win32 App) microsoft edge webview2 runtime offline installer repack
If you are using Intune, you must wrap the .exe into an .intunewin file using the Microsoft Win32 Content Prep Tool.
Place the MicrosoftEdgeWebView2RuntimeInstallerX64.exe in a dedicated source folder. Run IntuneWinAppUtil.exe.
Specify the source folder, the setup file name, and an output folder.
Upload the resulting .intunewin file to Intune and set the install command to MicrosoftEdgeWebView2RuntimeInstallerX64.exe /silent /install. Creating a "Fixed Version" Package
For environments requiring absolute stability without automatic updates, you can package a Fixed Version of the runtime.
Download the "Fixed Version" CAB or ZIP from the official download page.
Extract the contents using a command like expand -f:* [filename].cab [destination].
Include the extracted folder directly within your application's directory. This allows your app to use its own local copy of WebView2 without installing a system-wide component. 4. Verification and Troubleshooting
After deployment, you can verify the installation by checking Apps & Features or the registry.
Registry Key: The installation status and version are typically stored under HKLM\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\F3017226-FE2A-4295-8BDF-00C3A9A7E4C5.
Repair: If an offline installation fails or becomes corrupted, re-running the Standalone Installer with administrator privileges will often overwrite and repair the existing runtime. AI responses may include mistakes. Learn more
How to install WebView2 on your Windows Machine | FenixPyre Docs Create a batch file or PowerShell script called
Repacking the Microsoft Edge WebView2 Runtime offline installer
is a common practice for IT administrators who need to deploy the runtime in restricted environments, such as air-gapped systems or machines with limited internet access. Microsoft Learn Understanding the Offline Installer The offline installer—officially known as the Evergreen Standalone Installer
—is a self-contained package that includes all the binaries necessary to install the WebView2 Runtime without an active internet connection. This differs from the "Bootstrapper," which is a tiny file that downloads the runtime during the installation process. Microsoft Developer Why Repack the Installer? Repacking is typically done to: Bundle with Applications
: Include the runtime as part of a larger software suite's setup, ensuring the dependency is met automatically. Silent Deployment
: Pre-configure the installer for silent, unattended installation across hundreds of machines via enterprise management tools. Version Control
: In specific cases, developers use a "Fixed Version" repack to ensure their app always uses a specific, tested version of the runtime rather than the auto-updating "Evergreen" version. Microsoft Learn Core Components for Repacking
To create a repack, you primarily need the official standalone files from the Microsoft WebView2 Developer page Architecture Specifics
: You must select the correct installer for the target system: (64-bit), or Silent Install Commands
: When repacking for enterprise tools (like SCCM or InTune), use the following command for a silent, per-machine installation:
MicrosoftEdgeWebView2RuntimeInstallerArch.exe /silent /install Microsoft Learn Distribution Methods Evergreen Standalone (Recommended)
: The installer is run once, and the runtime thereafter updates itself automatically through the Microsoft Edge Update service. Fixed Version
: You decompress the runtime binaries (using tools like WinRAR or the or custom scripts
command) and include them directly within your application's folder structure. Your app then points to this specific folder instead of the system-wide runtime. Microsoft Learn Important Considerations OS Support
: WebView2 is built into Windows 11 but must be installed manually on Windows 10 and older supported server versions. Legacy Systems
: For older OS versions like Windows 7 or Server 2012 R2, you may need to source specific legacy versions (e.g., version 109) from the Microsoft Update Catalog Disk Space
: The runtime and the Microsoft Edge browser share binaries when they are on the same version, which helps minimize the total disk footprint. Microsoft Learn PowerShell scripts for automating this deployment or more details on Fixed Version integration? How to Install Microsoft Edge WebView2 Runtime (2026) 26 Feb 2026 —

if ($LASTEXITCODE -eq 0)  Write-Host "Installation successful." 
else  Write-Host "Installation failed with code $LASTEXITCODE"; exit 1 

Microsoft distributes three types of WebView2 installers:

| Type | File Size | Requires Admin | Supports Silent Install | Use Case | |------|-----------|----------------|------------------------|----------| | Online Bootstrapper | ~2 MB | Yes | Yes | Internet-connected machines | | Standalone Offline (EXE) | ~150–200 MB | Yes | Yes (/silent) | Air-gapped / enterprise deployment | | Embedded (DLLs) | N/A (part of app) | No | N/A | Per-process embedding |

Limitations of Official Offline Installer:

When searching for a "repack," caution is required:

WebView2 is a machine-wide component. The repackaged installer must execute in the System Context (Administrator privileges). A repack ensures this by default

For organizations requiring absolute version locking (ignoring Windows Update), the repack involves distributing the Fixed Version Runtime binaries.