32-bit
burnmachine scopedownload.visualstudio.microsoft.com · publisher domain- File name
- VC_redist.x86.exe
- SHA-256
- f0bab33a302b3cdb2e11113760d016f54fd3d2632c65ba7834fac4f0abd7f1a3
by Microsoft Corporation · Proprietary
The Microsoft Visual C++ v14 Redistributable Package (x86)
The 32-bit half of the Visual C++ 2015-2022 runtime. On 64-bit Windows people install only the x64 package and then wonder why a program still reports a missing DLL: plenty of applications are 32-bit and need this one specifically.
This is the same runtime as the x64 package, compiled for 32-bit applications. Both install side by side and neither replaces the other.
The rule is simple: match the application, not the operating system. A 32-bit program on 64-bit Windows needs the x86 runtime, and there is no downside to having both installed.
On a 64-bit machine the x64 package looks like the obvious choice, and it is only half the answer. A large amount of desktop software is still built as 32-bit, so the x86 runtime is needed just as often.
These URLs are the ones Microsoft Corporation declares in its own manifest. We do not proxy or shorten them, and we do not host a copy.
Run this against the file on disk. If the output does not match the hash below, the file is not what Microsoft Corporation published. Delete it.
Windows · PowerShell
Get-FileHash "VC_redist.x86.exe" -Algorithm SHA256macOS · Linux
shasum -a 256 "VC_redist.x86.exe"Expected output
f0bab33a302b3cdb2e11113760d016f54fd3d2632c65ba7834fac4f0abd7f1a3
Got a different hash, or one you cannot place? Paste it into the hash checker and it will tell you which program and version it belongs to, past releases included.
If a program reported one of these as missing, this is the package it belongs to. Installing it puts the file where it goes, registered properly, which downloading the DLL on its own does not.
| Signal | Finding | Points |
|---|---|---|
| SHA-256 hash published | 1 of 1 installers ship a SHA-256 hashWithout a published hash there is no way to prove the file you downloaded is the file the publisher built. | 30 / 30 |
| Binary provenance | 1 on the publisher's own domainThe strongest signal against a repackaged installer: the file should come from the publisher, not from a mirror nobody vouches for. | 35 / 35 |
| Served over HTTPS | 1 of 1 over HTTPSAn installer fetched over plain HTTP can be modified in transit. | 15 / 15 |
| Licence declared | ProprietaryA declared licence tells you what you are actually allowed to do with the software. | 5 / 5 |
Yes, in the sense we can actually verify: the installer downloads from microsoft.com, which is a domain we have tied to Microsoft Corporation.
The installer on this page comes with the SHA-256 Microsoft Corporation declared, so you do not have to take our word for it: hash the file you downloaded and compare.
What this does not tell you is whether the software itself is any good, or whether you want what it does once installed. A publisher can ship something you would rather not run and the download is still authentic. We answer the question we can measure and leave the other one to you.
If Windows says “Windows protected your PC” when you run it, that is SmartScreen reporting reputation, not a malware verdict — it shows up on perfectly legitimate software from small publishers and on releases that are simply new. The reverse matters more: no warning does not mean the file was checked.
How the 100/100 score is calculated · why the source matters more than the reputation
Windows ships with a package manager, and this program is in it. The identifier below is the one Microsoft's repository uses, which is also where the download URL and hash on this page come from.
Install
winget install --id Microsoft.VCRedist.2015+.x86 --exactUpgrade later
winget upgrade --id Microsoft.VCRedist.2015+.x86Why --exact: without it winget matches on name as well as identifier, and a search that returns more than one package makes it stop and ask rather than install. Pinning the identifier is what makes the command safe to put in a script.
Not installing anything, or getting an error back? The commands that actually come up covers upgrading everything at once, what --include-unknown is for, and why winget can be missing from a machine that should have it.
The version history of Microsoft Visual C++ v14 Redistributable (x86), each release with the download URL the publisher declared at the time and the SHA-256 to check it against. Useful when an update breaks something and you need to downgrade to a build that worked.
We do not host any of these files and never re-upload them, which is the difference between this and an old-version download site.
B6AB675F0A27E6600F9726E75DEA08D99C15F8EA4B842A2A1D988FA9529D39B9
E7267C1BDF9237C0B4A28CF027C382B97AA909934F84F1C92D3FB9F04173B33E
0C09F2611660441084CE0DF425C51C11E147E6447963C3690F97E0B25C55ED64
435A0DE411B991E2BFC7FD1D5439639E7B32206960D3099370E36172018F52FE
C4E3992F3883005881CF3937F9E33F1C7D792AC1C860EA9C52D8F120A16A7EB1
DD1A8BE03398367745A87A5E35BEBDAB00FDAD080CF42AF0C3F20802D08C25D4
ED1967C2AC27D806806D121601B526F84E497AE1B99ED139C0C4C6B50147DF4A
A32DD41EAAB0C5E1EAA78BE3C0BB73B48593DE8D97A7510B97DE3FD993538600
510FC8C2112E2BC544FB29A72191EABCC68D3A5A7468D35D7694493BC8593A79
C61CEF97487536E766130FA8714DD1B4143F6738BFB71806018EEE1B5FE6F057
AD573D3198853FC71137A88E51ABDE844B84F29B0CE6DD91BBEC661BC0143B36
5365A927487945ECB040E143EA770ADBB296074ECE4021B1D14213BDE538C490
8AE59D82845159DB3A70763F5CB1571E45EBF6A1ADFECC47574BA17B019483A0
CE4843A946EE3732EB2BFC098DB5741DC5495C7BEA204E11D379336DCC68E875
BB66E74A41ECF5DC09487608E477ACC4F78A38A0EC4FFE3100069C8A067DA29A
CF92A10C62FFAB83B4A2168F5F9A05E5588023890B5C0CC7BA89ED71DA527B0F
2ACBFE92157C1CF1A7B524A9325824046D83DBFA3FEB1CBD4DD02A42E020F77C
37E08B5D6EDC325ACD805AD35CEE6506ADAF88ACCC7086BE2E771E69400AADE8
B7AE307237F869E09F7413691A2CD1944357B5CEE28049C0A0D3430B47BB3EDC
C160CF4F7405B3AE263A46EC87445F3E851CD64389AEF4A2C2D9029127DF40D5
The file names, so you can tell what you have. Their hashes are in the hash checker and in the downloadable archive.
Publishers take old builds offline without warning, so a link here can stop working even though the hash stays correct forever. If you already have the file, the hash is what matters: it tells you whether what you have is what they published.
Every Microsoft Visual C++ v14 Redistributable (x86) version with a published manifest, newest first. The most recent ones are listed above with their file names and hashes.
Matched on the categories Microsoft Corporation and others declare in their own manifests, so the grouping is theirs rather than ours. Each one has its official URL and hash on the same terms as this page.
Not related to Microsoft Visual C++ v14 Redistributable (x86) — just other entries, each with its own official URL and published hash.