x86
user scopeMicrosoftEdgeWebView2RuntimeInstallerX86.exe
- SHA-256
- 5bbb6af39c781887733f6ed67c4c5df9693f276df8daba72cb0046b05e2b45a1
Microsoft Edge WebView2 Runtime · earlier release
Microsoft Edge WebView2 Runtime 149.0.4022.80
The URL Microsoft Corporation published for this release, and the SHA-256 of every file in it, so you can prove the copy you have is that one and not something else wearing the same name.
This is not the current release
Microsoft Edge WebView2 Runtime is now on version 151.0.4129.101. An older build stops getting security fixes, so install one only when you have a reason: a plugin that broke, a machine that cannot run the new one, a bug you need to reproduce. If you just want Microsoft Edge WebView2 Runtime, take the current version.
Files in Microsoft Edge WebView2 Runtime 149.0.4022.80
x64
user scopeMicrosoftEdgeWebView2RuntimeInstallerX64.exe
- SHA-256
- 24172d2178212167522b91995b95dd5d2dadc8e7310591535d194524eea090e8
arm64
user scopeMicrosoftEdgeWebView2RuntimeInstallerARM64.exe
- SHA-256
- c7fb7a192ee8aeadd09ac0da50ea08c036f28e5a38b1827aa5c9292805be3bb5
Which one of these you want
This release shipped in more than one architecture, and the wrong one fails in a way that is not obvious: it either refuses to start or installs and then misbehaves. Take x64 unless the machine is genuinely 32-bit or ARM. Here is how to check which one your Windows is — and note that x86 means 32-bit, which is the part that catches people out.
The scope label says who the installer writes for. A user build installs into your own profile and needs no administrator rights; a machine build installs for everyone and does. On a work laptop where you cannot elevate, the user build is often the only one that will run at all. Silent install switches are on the same data.
Check the file you have
Windows does this without installing anything. In PowerShell:
Get-FileHash .\MicrosoftEdgeWebView2RuntimeInstallerX86.exe -Algorithm SHA256
Compare what it prints with the value above. If they match, your copy is byte-for-byte the one Microsoft Corporation published. If they do not, it is a different file, whatever it is called and wherever it came from. Paste a hash into the verifier and it will tell you which release it belongs to.
If PowerShell is blocked by policy on the machine, the same thing works from plain cmd with certutil -hashfile MicrosoftEdgeWebView2RuntimeInstallerX86.exe SHA256. On macOS or Linux it is shasum -a 256 MicrosoftEdgeWebView2RuntimeInstallerX86.exe.
If the link no longer works
Publishers retire old releases, and we do not host copies, so a link from an earlier version can stop working without notice. Two ways it fails: an honest 404, or — more confusing — the server answers normally but hands you the current downloads page instead of the file. If what arrives is a few kilobytes of HTML rather than an installer, that is what happened.
The hash on this page stays useful either way. It still identifies Microsoft Edge WebView2 Runtime 149.0.4022.80 wherever you find a copy, which is the whole point of publishing it: you can accept a file from somewhere else and still prove it is the one Microsoft Corporation built.
Releases either side of this one
Every Microsoft Edge WebView2 Runtime release we index · where this data comes from