Corrupted Microsoft Visual C ++ 2015-2022 (X64) & (x86)

Question

Every time I get Windows updates my Microsoft C ++ files get corrupted and I have to go in and repair them. Any reason as to why?

Answer 1

Hi ,

I understand according to the error log because there is a corrupted version of visual c++, follow these procedures first uninstall everything and remove the installation registry folder.

Microsoft FIx it application to completely uninstall visual C++ after uninstallation.

https://download.microsoft.com/download/7/E/9/7E9188C0-2511-4B01-8B4E-0A641EC2F600/MicrosoftProgram_Install_and_Uninstall.meta.diagcab

Create point system before

https://support.microsoft.com/en-us/windows/system-protection-e9126e6e-fa64-4f5f-874d-9db90e57645a

Open the on command(admin) prompt and run the commands: sfc /scannow and dism /online /cleanup-image /restorehealth , wait for the process to finish and restart the PC.

Open, as an administrator, the Windows Registry by typing "Regedit" into the Windows Start button.

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products.

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products to remove MSI

Go to "Edit" and look for the missing *.msi file that was called out in the error message.

You have to search in the regedit tab and search according to the location you will find out yours should be 2015-2022 or just 2022 and delete the registry.

Restart on the computer and install Visual C AIO

Reinstall using Visual C++ AIO after download extract the install.bat file right click run as administrator.

https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Thanks

Answer 2

The recurring corruption is typically not caused by Windows Updates themselves, but by how Visual C++ Redistributable packages are installed and updated on the system and by other applications.

Key points from similar scenarios:

1. Older or conflicting VC++ redistributables
   • Many applications (for example, CAD, Adobe, rendering tools) ship and install their own, often older, Visual C++ Redistributable packages.
   • After updates or application installs, these older packages can overwrite or conflict with the newer, supported Visual C++ 2015–2022 runtime, leading to missing or mismatched DLLs (such as vcruntime140.dll, msvcp140.dll, vcruntime140_1.dll, etc.).
   • This appears as “corruption” and is temporarily fixed when the redistributable is repaired or reinstalled.
2. Multiple versions and upgrade behavior
   • Visual C++ 2015–2022 uses a single major version (14.x) and is binary compatible across 2015, 2017, 2019, and 2022.
   • Each Redistributable installer checks for a newer version and will not install if a newer one is already present. However, if an application installs an older bundle or drops its own DLLs, it can effectively downgrade or break the runtime used by other apps.
   • The installed version is tracked in the registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\{x86|x64|arm64}
   • Inconsistent versions between x86 and x64, or between what apps expect and what is installed, can cause repeated failures until repaired.
3. Installer and cache issues
   • If the Windows Installer cache or VC++ package cache is damaged, updates or app installs that touch the redistributables can fail or leave them in a broken state. This can show up as generic installer errors (1603) or “older version can’t be removed” (1714) in VC++ logs.
   • Corrupted cache or partial installs mean that each time Windows or an app tries to update or use the runtime, it may fail until the redistributable is repaired.
4. How to make the situation more stable
   • Standardize on the latest supported Visual C++ 2015–2022 Redistributable (both x86 and x64) across devices and remove older conflicting versions where possible.
   • After patching or application deployment, verify that the correct redistributable version is still present (via registry or a scripted check) instead of repeatedly repairing only after failures.
   • Review application installers in the environment and, where possible, update or block those that deploy outdated VC++ redistributables that conflict with the standardized version.

This kind of control reduces the chance that Windows Updates or app updates will reintroduce older runtimes or break the shared VC++ components, so the redistributables no longer appear to “corrupt” after each update.

---

References:

• Redistributing Visual C++ Files
• Troubleshoot Visual C++ Redistributable installation issues
• MVC140.DLL Error after Windows OS Updates - Microsoft Q&A