Microsoft Visual C++ 2013 Redistributable (x64): Fix Stubborn Install Errors in 5 Steps

The Microsoft Visual C++ 2013 Redistributable (x64) is a critical runtime library for apps built with Visual Studio 2013, but installation errors can derail projects fast.

If you’ve ever hit a blocked setup or cryptic error code, you’re not alone—even pros stumble here. The good news? Most issues vanish with the right steps, and I’ll show you exactly how to bypass them without reinventing the wheel.

Common Microsoft Visual C++ 2013 (x64) install errors & root causes

The Microsoft Visual C++ 2013 Redistributable (x64) is a critical runtime library for applications built with Visual Studio 2013. Yet, users often encounter frustrating errors like 0x80070643, 0x643, or 0x80073712 during installation.

These issues typically stem from corrupted downloads, conflicting software, or incomplete installations. Understanding the root cause is half the battle—let’s break it down.

Error 0x80070643 often appears when the installer fails to register components properly. This usually happens if the Windows Installer service is interrupted or if previous installations left behind registry fragments.

Meanwhile, 0x643 typically signals a permission issue, where your user account lacks the necessary admin privileges to modify system files.

0x80073712, on the other hand, is a classic sign of a corrupted download or a conflict with an existing Visual C++ redistributable version. Even after multiple attempts, these errors persist because the underlying issues—like leftover files or system corruption—aren’t addressed. Let’s dive into the specifics.

Many users assume these errors are random, but they’re almost always tied to one of three core issues: corrupted files, permission problems, or conflicting software. For example, if you downloaded the x64 version but your system has an older x86 redistributable installed, the installer may fail silently.

Always verify your system’s architecture (x64 vs. x86) before proceeding.

Another common pitfall is downloading the redistributable from third-party sites. While some mirrors claim to offer the same files, they often bundle adware or outdated versions. Always grab the installer directly from Microsoft’s official site to avoid these headaches.

Even then, corrupted downloads can slip through—use tools like SHA-256 checksums to verify file integrity.

Conflicting software, like antivirus programs or Windows Update, can also derail installations. Some security suites aggressively scan installers, flagging them as threats even when they’re legitimate. If you’re seeing errors mid-install, try disabling your antivirus temporarily or adding an exception for the Visual C++ installer.

Even after fixing the immediate issue, leftover files from failed installations can cause 0x80070643 or similar errors to reappear. That’s why tools like the Visual C++ Cleanup Tool (created by Microsoft) are invaluable.

This utility removes all traces of previous redistributables, giving you a clean slate for reinstallation. I’ve used it dozens of times—it’s saved me from countless headaches.

One mistake I see often is ignoring the error logs generated during failed installations. These logs (usually saved to %temp%) contain goldmines of information about what went wrong.

Open Event Viewer under Windows Logs > Application to find detailed entries about installation failures. Pay special attention to entries with Error or Warning severity levels.

If you’re running Windows 11, some users report additional hurdles due to strict app compatibility checks. The solution? Use Compatibility Mode to run the installer as if it were on Windows 7.

Right-click the installer, select Properties > Compatibility, and check the box for Run this program in compatibility mode for:. This trick works surprisingly well for older redistributables.

Finally, don’t overlook the power of a simple system reboot. Many installation errors stem from temporary system locks or services that need restarting. Before diving into complex fixes, try shutting down your PC, waiting 30 seconds, and rebooting. You’d be amazed how often this resolves seemingly stubborn issues.

5 Step-by-step fixes for stubborn Microsoft Visual C++ 2013 (x64) errors

When the Microsoft Visual C++ 2013 Redistributable (x64) installer throws errors like 0x80070643 or 0x643, it’s often due to leftover files from failed installations or system conflicts. Before diving into complex fixes, start with the simplest solutions—like repairing the installation through Control Panel—before moving to deeper troubleshooting.

I’ve used these steps to resolve stubborn errors on Windows 7 through Windows 11, including legacy systems in my uncle’s basement workshop.

Always back up your registry before making changes, as manual edits can cause system instability. If you’re unsure, create a system restore point first—this is your safety net if something goes wrong.

The steps below are ordered from least to most invasive, so tackle them in sequence until the issue resolves. Most users fix their problems within the first two steps, but stubborn cases may require deeper intervention.

If you’re still stuck after Step 5, the issue might stem from a corrupted Windows Installer service. Try resetting it via Command Prompt (Admin) with msiexec /regserver. For enterprise environments, consider deploying the redistributable via Group Policy or SCCM with proper logging enabled.

Pro tip: If you’re installing this for a specific app (like an older game or legacy software), check its documentation for specific redistributable requirements. Some apps need both the x86 and x64 versions, even on 64-bit systems.

Always download from Microsoft’s official archive—third-party mirrors often host corrupted or bundled files.

Remember, patience is key. I’ve seen Visual C++ errors resolved in minutes with these steps, but complex cases might take longer. If all else fails, consider upgrading to a newer Visual C++ Redistributable (like 2015-2022) if your software supports it—many modern apps work fine with later versions.