Visual C++ DLL download
MSVCP and VCRUNTIME files installed by Microsoft Visual C++ Redistributable packages.
Find the right source for common DLL files, understand why a file is missing, and repair the software that installed it. DLLDownload.wiki prioritizes publisher packages and official recovery instructions over anonymous file mirrors.
Each page explains the file family, the supported recovery source, and the fixes to try before replacing individual files.
| DLL file | Component | Recommended source | Status | Open page |
|---|---|---|---|---|
| msvcp140.dll | Microsoft Visual C++ 2015-2022 Runtime | Microsoft Visual C++ Redistributable | Official package available | |
| amd_ags_x64.dll | AMD GPU Services (AGS) | Game package or AMD GPUOpen AGS | Publisher source available | |
| msvcp100.dll | Microsoft Visual C++ 2010 Runtime | Visual C++ 2010 SP1 Redistributable | Official package page | |
| msvcp110.dll | Microsoft Visual C++ 2012 Runtime | Visual C++ 2012 Update 4 Redistributable | Official package page | |
| vcruntime140.dll | Microsoft Visual C++ 2015-2022 Runtime | Microsoft Visual C++ Redistributable | Official package available | |
| vcruntime140_1.dll | Microsoft Visual C++ 2015-2022 Runtime | Microsoft Visual C++ Redistributable | Official package available | |
| xinput1_3.dll | Legacy DirectX End-User Runtime | DirectX End-User Runtime Web Installer | Official package page | |
| d3dx9_43.dll | Legacy DirectX 9 helper library | DirectX End-User Runtime Web Installer | Official package page | |
| steam_api64.dll | Steamworks API integration | Steam game verification | Restore through Steam | |
| onlinefix64.dll | Third-party game modification component | Original software source only | No verified public source |
Our DLL download and missing DLL fixes directory separates a filename lookup from a trustworthy recovery decision. A search can identify the likely component, but it cannot inspect the program on your PC, confirm who created a binary, or decide which architecture your application needs. That is why every DLL download result begins with ownership, package, and compatibility information.
Use a DLL download page to answer three questions before changing Windows: Which product normally supplies the file? Is there an official package or legitimate repair workflow? Does the affected application require x86, x64, or a game-specific build? Answering those questions is more reliable than choosing a mirror by filename.
The directory covers Microsoft Visual C++ runtimes, optional legacy DirectX helpers, graphics SDK components, Steam game files, and high-demand third-party filenames. When no verified public source exists, the page says so directly and provides recovery steps instead of presenting an unsafe DLL download button.
A missing DLL usually belongs to a larger runtime, driver, game client, or application. Starting with that owner is safer than searching for an isolated binary.
MSVCP and VCRUNTIME files installed by Microsoft Visual C++ Redistributable packages.
Older Visual Studio 2010 and 2012 components still required by established desktop software.
Legacy DirectX helper libraries used by games without replacing the DirectX built into Windows.
Vendor or platform components that should be restored through the SDK, game launcher, or original installer.
A missing-DLL message describes a symptom, not always the root cause. The file may have been removed by an incomplete update, quarantined by security software, left behind after an uninstall, or requested by an application built for a runtime that is not installed.
Downloading a same-named file from an unknown mirror can introduce a different build, the wrong processor architecture, or malicious code. It can also hide the real issue until the next update. Our pages therefore begin with the package or product responsible for the component.
Follow the steps in order. Stop when the application opens normally; stacking unrelated downloads makes diagnosis harder.
Note the DLL filename, application name, and when the error appears. Similar filenames such as vcruntime140.dll and vcruntime140_1.dll belong to related but distinct runtime generations.
Use Apps & features, the game launcher's verify function, or the application's installer. This restores the exact files expected by that product.
For MSVCP and VCRUNTIME errors, install the relevant Microsoft Visual C++ package. For XInput or D3DX errors, use Microsoft's legacy DirectX runtime installer.
If a file disappeared suddenly, review Windows Security or your antivirus quarantine. Restore only when the file came from software you trust and the detection has been investigated.
Use DISM and System File Checker for protected Windows components. These tools validate system files against Windows servicing sources rather than anonymous mirrors.
Our source policy: We link to official publisher pages or documented recovery workflows when available. We do not label a file safe merely because its name matches a missing-file message, and we do not provide cracks, bypass tools, or fabricated scan badges.
Short answers to the decisions that matter before installing or replacing a DLL file.
A filename alone cannot prove safety. Prefer the software publisher's installer, Microsoft redistributable, game-client verification, or Windows repair tools. Unknown standalone mirrors can provide altered, outdated, or incompatible files.
Usually you should not choose a folder manually. Install or repair the package that owns the DLL so it places every dependency correctly. Copying files into System32, SysWOW64, or an application folder can override serviced versions.
The affected application may be 32-bit and need the x86 runtime even on 64-bit Windows. Application architecture determines the dependency package.
No. SFC repairs protected Windows components. It does not install third-party game files, Visual C++ redistributables, optional legacy DirectX SDK libraries, or application plugins.
Only specific COM libraries are designed for registration. Visual C++ runtime files and many game DLLs are not repaired with regsvr32. Use the owning installer instead.
The file may be malicious, modified, uncommon, or behaviorally suspicious. Review the exact detection and original source before restoring it. Do not create broad exclusions simply to suppress an alert.
No. Microsoft's legacy DirectX end-user runtime adds optional side-by-side helper libraries required by older games without replacing the modern Windows DirectX core.