How do I fix the error code 1714?

Error 1714 during the Desktop development with C++ installation is resolved by identifying the older Visual C++ Redistributable named in the setup log, removing that exact version through Windows Installer—or restoring its original installer so it can uninstall—and then retrying Visual Studio.

1. Identify the package that cannot be removed

1. In the error dialog, select View logs.
2. Search the newest log for:
   • Error 1714
   • System Error 1612
   • Minimum Runtime
3. Record the complete product name, architecture, and version, for example:
   • Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.xx.xxxxx
   • Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.xx.xxxxx

For VC Redistributables, error 1714 means Windows Installer cannot remove the previous version because its cached installation package is corrupted, missing, or inaccessible.^1^

Since deleting components did not help, do not delete additional MSI files, package-cache folders, or registry entries manually.

2. Remove or restore that exact VC Redistributable

1. Open Settings → Apps → Installed apps.
2. Find the exact Visual C++ Redistributable and architecture reported in the log.
3. Select … → Uninstall.
4. If Windows offers an installer troubleshooter, allow it to repair the uninstall information.
5. Restart Windows and rerun the Visual Studio Community installer.

If normal removal fails because the original MSI is missing:

1. Obtain the same older VC Redistributable version and architecture reported in the log from Microsoft’s Visual Studio/Dev Essentials downloads.
2. Never use an unsigned Redistributable or one obtained from a third-party download site.
3. Run that installer and select Uninstall.
4. Restart Windows and retry the Visual Studio installation.^1^

If Windows still cannot remove the entry, use Microsoft’s Program Install and Uninstall troubleshooter, choose Uninstalling, and select the exact product from the log. It repairs corrupted registry keys and incomplete uninstall information that can block installation or removal.^2^

3. Repair the Visual Studio Installer if the MSI is no longer the reported failure

If the old VC package was removed but Visual Studio setup still fails:

1. Open Settings → Apps → Installed apps.
2. Locate Visual Studio Installer.
3. Select … → Modify → Repair.
4. Restart the installer and select Desktop development with C++ again.^1^

For damaged installer metadata, Microsoft also documents closing the installer, deleting:

C:\Program Files (x86)\Microsoft Visual Studio\Installer

and then rerunning VisualStudioSetup.exe. Have a fresh copy of VisualStudioSetup.exe available before deleting that folder.^3^

Last resort: remove broken Visual Studio installation state

Use InstallCleanup.exe only if Visual Studio itself cannot be repaired or uninstalled. It can affect other Visual Studio installations and shared features.

1. Close Visual Studio Installer.
2. Open Command Prompt as administrator.
3. Run the tool with -i because Visual Studio will be reinstalled:

"C:\Program Files (x86)\Microsoft Visual Studio\Installer\InstallCleanup.exe" -i

4. Restart Windows.
5. Run the Visual Studio Community bootstrapper again and select Desktop development with C++.

Microsoft reserves this tool for failed repair or uninstallation scenarios.^4^

If it still fails, collect setup logs with Microsoft’s Visual Studio and .NET log collection tool, then use Visual Studio Installer → Report a problem. The resulting archive is normally written to %TEMP%\vslogs.zip.^3^

References

1. Troubleshoot Visual C++ Redistributable installation problems
2. Fix problems that block programs from being installed or removed
3. Troubleshoot Installation and Upgrade Issues - Visual Studio
4. Uninstall or remove Visual Studio