[Solution Found] Failure to install Microsoft.VisualCpp.Redist14 with Error 0x80070643 despite removal of previous VC++ distributes.

Cypher Cern 0 Reputation points
2026-09-17T20:22:27.76+00:00

Here's a summarized version of my solution:
User's image

Issue: Microsoft.VisualCpp.Redist.14 Installation Failing with Error 0x80070643

Symptom: The Microsoft.VisualCpp.Redist.14 installer fails during setup, exiting with Error 0x80070643: Failed to execute MSI package or Failed to configure per-machine MSI package.

  • Root Cause: Corrupted registry keys associated with Microsoft.VisualCpp.Redist.14 and its legacy package GUIDs (such as {CF4C347D-954E-4543-88D2-EC17F07F466F}). During the detection phase, Windows Installer hits a permission block or broken path for those existing 14.x keys, causing the installation to abort and roll back.

Solution: Manual Registry Nuke of Broken 14 Keys and GUIDs

When standard uninstallation fails, manually removing the corrupted Microsoft.VisualCpp.Redist.14 keys clears the upgrade loop:

  1. Open Registry Editor: Press Win + R, type regedit, and press Enter.
  2. Navigate to Uninstall & Product Keys:
  3. Now, run the Microsoft.VisualCpp.Redist.14 as administrator
    Problem solved.
Developer technologies | Visual Studio | Setup
0 comments

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Damien Pham (WICLOUD CORPORATION) 2,215 Reputation points Microsoft External Staff Moderator
    2026-09-18T02:33:02.9233333+00:00

    Hello @Cypher Cern

    Thank you for sharing the solution.

    We appreciate you taking the time to investigate the issue, test the behavior, and document what worked. Your findings may also help others experiencing a similar installation problem.

    To add some context, the issue was related to an old or corrupted Microsoft Visual C++ Redistributable registration. Removing the specific Microsoft.VisualCpp.Redist.14 entry and legacy GUID referenced in the error cleared the conflict and allowed the installation to complete.

    Since registry changes should be treated with caution, users experiencing similar issues can also refer to Troubleshoot Visual C++ Redistributable installation problems for additional troubleshooting guidance.

    We hope you will continue sharing your questions and findings with the Microsoft Q&A community. Whether or not you already have a solution, sharing your experience can be helpful to others.

    I'm glad that the issue is now resolved. If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback. 

    Thank you again for your contribution.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-09-17T20:22:50.79+00:00

    The supported guidance for this scenario is:

    1. Collect the VC Redist failure logs first.
      • Download the Microsoft Visual Studio and .NET Log Collection Tool.
      • Run Collect.exe.
      • Extract %TEMP%/vscollect.zip.
      • Review log files named like dd_vcredist_<arch>_yyyyMMddHHmmss and search for Error, Failed, or System Error.
    2. Try the standard VC Redist recovery steps.
      • Temporarily disable antivirus or endpoint protection, then retry the installation.
      • Right-click the VC Redist installer and select Run as Administrator.
      • Install all pending Windows updates, reboot, and retry.
    3. If uninstall or upgrade is blocked by broken installer state, use the official Program Install and Uninstall troubleshooter.
      • Download the troubleshooter.
      • Run it and follow the prompts.
      • It can fix problems that prevent programs from being installed, uninstalled, or updated, including corrupt registry keys and cases where a program can’t be removed through Programs and Features.
    4. If the installer package itself is corrupt, use only Microsoft-signed installers downloaded from Microsoft sites.
      • For current versions, install the latest supported Visual C++ Redistributable.
      • For older versions, use the documented Microsoft download sources for legacy VC Redist packages.
    5. Avoid manual registry deletion unless there is a verified backup and a clear recovery plan.
      • Registry changes are high risk and can cause additional install or uninstall failures.
      • The supported material provided here recommends the troubleshooter for corrupt registry-key scenarios rather than manual registry removal.

    The image and description match a broken cached MSI or corrupted installer registration state. The supported path is to use the troubleshooter, review the VC Redist logs, then reinstall from a Microsoft source with admin rights after basic checks such as antivirus and Windows Update.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.