Microsoft Edge Webview2 Runtime Offline Installer Repack ((install)) May 2026

Microsoft Edge WebView2 is a developer's best friend, but managing its installation in air-gapped or restricted environments can be a headache. Repacking the offline installer ensures your application runs smoothly without needing an active internet connection. Why Use the Offline Installer?

The standard WebView2 "Evergreen" bootstrapper is tiny because it downloads the actual runtime during installation. In many corporate or secure settings, this isn't an option. No Internet Required: Perfect for offline workstations.

Version Control: Lock your app to a specific runtime version.

Reliability: Eliminates "download failed" errors during setup.

Simplified Deployment: Bundle the runtime directly with your app's MSI or EXE. Step 1: Download the Fixed Version

To repack WebView2, you need the Fixed Version binaries rather than the Evergreen installer. Visit the Microsoft Edge WebView2 download page. Look for the Fixed Version section.

Select the architecture (x64, x86, or ARM64) and the version you need. Download the CAB or ZIP package. Step 2: Extract and Structure

Once you have the package, you need to extract the files so your installer can point to them.

Extract the package: Use a tool like 7-Zip to unpack the contents.

Verify contents: You should see a folder containing msedgewebview2.exe and several DLLs.

Placement: Put these files in a subfolder within your application's directory (e.g., /redist/webview2/). Step 3: The Repacking Process

When building your installer (using WiX, Inno Setup, or Advanced Installer), you have two main strategies for the repack:

Method A: Internal DistributionInclude the extracted Fixed Version files directly in your application folder. Your code must then point the CoreWebView2Environment to this local folder path instead of the system-wide installation.

Method B: Silent Offline InstallIf you prefer a system-wide install, use the Evergreen Standalone Installer. It is a larger executable (~150MB) that contains all necessary files. Command: MicrosoftEdgeWebview2Setup.exe /silent /install

Benefit: Updates automatically if the machine eventually hits the web. Best Practices 💡

Check Architecture: Ensure you match the installer to your app’s target (x64 vs x86).

Cleanup: If using a temporary folder for the installer during setup, ensure it deletes itself after completion. microsoft edge webview2 runtime offline installer repack

Testing: Always test on a "clean" VM that has never had Edge or WebView2 installed to verify the offline flow works.

If you'd like me to provide specific scripts or configuration code for your repacking process:

Mention your preferred installer framework (e.g., WiX, Inno Setup, MSIX). Specify the programming language of your main application.

Tell me if you need a silent install script for enterprise deployment.

For an offline repack of the Microsoft Edge WebView2 Runtime , you should use the Evergreen Standalone Installer

, which contains all necessary files for a full installation without an internet connection. Microsoft Learn Recommended Installer Evergreen Standalone Installer : Available in : Download directly from the Microsoft Edge WebView2 Developer Page Microsoft Developer Silent Installation Commands

To run the installer silently as part of a script or larger setup package, use the following syntax. Installation Type Silent Install

MicrosoftEdgeWebView2RuntimeInstallerX64.exe /silent /install Silent Uninstall

MicrosoftEdgeWebView2RuntimeInstallerX64.exe /silent /uninstall flag must come to avoid known bugs in some versions of the bootstrapper.

: Running these commands from an elevated (Administrator) command prompt triggers a per-machine install. Running without elevation defaults to a Microsoft Learn Repacking Tips offline upgrade edge or runtime webview version

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. Microsoft Edge WebView2 is a developer's best friend,

/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)

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

Why You Need the Offline Installer

By default, many applications attempt to download the WebView2 Runtime via the "Evergreen" method when they are first launched. This requires an active internet connection. Do not download random “WebView2 offline repack” from

However, in enterprise environments, secure networks, or during Windows deployment (OOBE), internet access may be restricted. If the runtime is missing, the dependent application will fail to launch, often presenting a cryptic error message or crashing silently. The Offline Installer (or "Fixed Version") allows you to pre-install this dependency without requiring a connection to Microsoft's servers.

Part 6: Deployment Scenarios for the Repack

Once your repack is ready, here is where it shines:

7. Recommendation

Do not download random “WebView2 offline repack” from file-sharing sites or torrents.
Always obtain the official offline installer from Microsoft:
https://developer.microsoft.com/en-us/microsoft-edge/webview2/
(Look for “Evergreen Standalone Installer” → x64/x86/arm64)

If you need silent deployment, use the official EXE with built-in switches:

MicrosoftEdgeWebView2RuntimeInstaller.exe /silent /install

For advanced repacking (internal use only), take the official MSI from the extracted temp folder and wrap it with your own script/tool like Advanced Installer, PSADT, or WinRAR SFX.

Would you like a sample script or instructions for creating a safe internal repack of the WebView2 offline installer?

Microsoft Edge WebView2 Runtime Repack typically refers to a modified or unofficial version of the WebView2 Runtime

installer. These "repacks" are often created by third-party developers to simplify the installation process in offline environments where the standard Microsoft Evergreen Bootstrapper

(which requires an active internet connection to download files) cannot be used. Microsoft Learn Key Features of a Repack Offline Capability

: Includes all necessary binaries within a single executable, allowing installation on machines without internet access. Simplified Deployment : Often configured for silent installation (

flags), making them popular for IT admins or inclusion in software bundles. Version Control

: Some repacks use a "Fixed Version" of the runtime, ensuring that applications always run on a specific, tested environment rather than automatically updating to a potentially breaking new version. Microsoft Developer Pros & Cons

WebView2 online and offline installation require elevation #490

2. The "Evergreen Standalone" Bootstrapper

Some repacks are simply the Evergreen Bootstrapper (a small file that downloads the latest version) bundled with the offline files. This creates a single, large executable that installs the latest runtime immediately without checking the internet at the moment of install.

2. Problem Statement

Feature: Microsoft Edge WebView2 Runtime — Offline Installer Repack

Step 4: Embed and Compress

Using a tool like WinRAR (SFX module) or 7-Zip:

  1. Add the official MicrosoftEdgeWebView2RuntimeInstallerX64.exe and your script to an archive.
  2. Configure the SFX to run powershell.exe -ExecutionPolicy Bypass -File Deploy-WebView2.ps1 upon extraction.
  3. Set the extraction path to %temp%\WebView2Repack.

4.2 Method A: The Script Wrapper (PSAppDeployToolkit)

For modern endpoint management, wrapping the executable in a PowerShell framework is often preferred over recompiling the binaries into an MSI, as it respects the original Microsoft EULA and update mechanism logic.

Workflow:

  1. Download the Standalone Installer.
  2. Create a deployment share structure (Source/Files).
  3. Place MicrosoftEdgeWebView2RuntimeInstallerX64.exe in the Files directory.
  4. Utilize PSAppDeployToolkit to invoke the installation silently.

Command Line Arguments: The official standalone installer supports silent installation switches.

# Standard Silent Installation
Start-Process -FilePath "MicrosoftEdgeWebView2RuntimeInstallerX64.exe" -ArgumentList "/silent", "/install" -Wait