Downloads of v 105.0.1343.53:


Last Update:

29 Sep 2022

Package Maintainer(s):

Software Author(s):

  • Microsoft


webview2-runtime webview2

WebView2 Runtime (Install)

  • 1
  • 2
  • 3

105.0.1343.53 | Updated: 29 Sep 2022



Downloads of v 105.0.1343.53:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
WebView2 Runtime (Install) 105.0.1343.53

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install WebView2 Runtime (Install), run the following command from the command line or from PowerShell:


To upgrade WebView2 Runtime (Install), run the following command from the command line or from PowerShell:


To uninstall WebView2 Runtime (Install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade webview2-runtime -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade webview2-runtime -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install webview2-runtime
    name: webview2-runtime
    version: '105.0.1343.53'
    state: present

See docs at

chocolatey_package 'webview2-runtime' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '105.0.1343.53'

See docs at

cChocoPackageInstaller webview2-runtime
    Name     = "webview2-runtime"
    Version  = "105.0.1343.53"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'webview2-runtime':
  ensure   => '105.0.1343.53',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 29 Sep 2022.


The Microsoft Edge WebView2 control allows you to embed web technologies (HTML, CSS, and JavaScript) in your native apps. The WebView2 control uses Microsoft Edge as the rendering engine to display the web content in native apps.

With WebView2, you can embed web code in different parts of your native app, or build all of the native app within a single WebView instance.


NOTE: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.

$ErrorActionPreference = 'Stop'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'EXE' #only one of these: exe, msi, msu
  url           = ''

  softwareName  = 'Microsoft Edge WebView2*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique

  checksum      = '69a70d81c56c0fedf43d7a07ee0f8ad006383ec06733748ac83b0401bf937ddb'
  checksumType  = 'sha256'

  silentArgs    = '/silent /install'
  validExitCodes= @(0)

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop'

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Microsoft Edge WebView2 Runtime'
  fileType      = 'EXE'
  # MSI
  silentArgs    = '--uninstall --msedgewebview --system-level --verbose-logging --force-uninstall'
  validExitCodes = @(0, 19)   # no matter the combination of switches I use, 19 is always the exit code

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
    $packageArgs['file'] = ($key.UninstallString).replace(' --uninstall --msedgewebview --system-level --verbose-logging', '')

    Uninstall-ChocolateyPackage @packageArgs
elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
WebView2 Runtime (Install) 105.0.1343.50 1510 Sunday, September 25, 2022 Approved
WebView2 Runtime (Install) 105.0.1343.42 2043 Sunday, September 18, 2022 Approved
WebView2 Runtime (Install) 105.0.1343.33 1995 Sunday, September 11, 2022 Approved
WebView2 Runtime (Install) 105.0.1343.27 1668 Tuesday, September 6, 2022 Approved
WebView2 Runtime (Install) 105.0.1343.25 1275 Sunday, September 4, 2022 Approved
WebView2 Runtime (Install) 104.0.1293.70 2026 Sunday, August 28, 2022 Approved
WebView2 Runtime (Install) 104.0.1293.63 1970 Monday, August 22, 2022 Approved
WebView2 Runtime (Install) 104.0.1293.54 2007 Sunday, August 14, 2022 Approved
WebView2 Runtime (Install) 104.0.1293.47 1443 Monday, August 8, 2022 Approved

This package has no dependencies.

Discussion for the WebView2 Runtime (Install) Package

Ground Rules:

  • This discussion is only about WebView2 Runtime (Install) and the WebView2 Runtime (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or WebView2 Runtime (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus