Repair Missing Visual C++ Runtimes with Apps & Features and winget in Windows 10/11

If an app reports that a Visual C++ runtime DLL is missing, first repair the matching installed Microsoft Visual C++ Redistributable in Settings. If that runtime is absent, install the current supported v14 package with winget. This guide applies to Windows 10 and Windows 11; the winget method requires Windows 10 version 1809 or later, or Windows 11, with App Installer available.

Prerequisites and compatibility​

Visual C++ Redistributables are shared runtime libraries used by many desktop programs, games, IDEs, plug-ins, and utilities. They are not interchangeable with .NET Desktop Runtime, DirectX, Java, or the Microsoft Visual C++ build tools.
Keep these compatibility rules in mind before changing anything:

• Repair an existing runtime first when it appears in Settings. This preserves its installed version and registration.
• On a 64-bit Windows PC, install both:
  • x64 for 64-bit applications.
  • x86 for 32-bit applications. Many older and current programs are still 32-bit.
• On an ARM64 Windows PC, install the current x64 package and the x86 package if you run x86 software. The current x64 v14 redistributable includes the ARM64 runtime binaries on ARM64 systems.
• The modern v14 runtime is shared by applications built with Visual Studio 2017 and later. An entry may still use an older display name such as “Microsoft Visual C++ 2015-2022 Redistributable”; that does not necessarily mean it is obsolete.
• Older runtimes—such as Visual C++ 2013, 2012, 2010, or 2008—install side by side. A newer v14 runtime does not replace every older runtime.

Warning: Do not remove all Visual C++ entries as a general “cleanup” step. Applications can depend on a particular older runtime, and mass removal can break working programs. Repair or install only the architecture and generation relevant to the affected app.

Click to expand...

You need:

• An administrator account, or administrator credentials for the User Account Control prompt.
• An internet connection for winget.
• The affected application closed before beginning.

Primary procedure: repair an installed runtime with Settings​

Use this method when the Visual C++ entry is present but the application still reports a missing DLL, a side-by-side configuration error, or a runtime initialization failure.

1. Close the affected program and related launchers​

1. Save work in the affected application.
2. Exit the app.
3. Close its launcher or client if applicable—for example, a game launcher, development environment, or management console.
4. If the installer previously failed because a file was in use, restart Windows now and continue before reopening the app.

Expected result: The runtime installer can replace or register files without the application holding them open.

2. Open the installed-apps list​

Use the path for your version of Windows.
Windows 11

1. Select Start > Settings.
2. Select Apps.
3. Select Installed apps.

Windows 10

1. Select Start > Settings.
2. Select Apps.
3. Select Apps & features.

3. Find the relevant Microsoft Visual C++ entry​

1. In the app-list search box, enter:
   Microsoft Visual C++
2. Look for entries beginning with Microsoft Visual C++ Redistributable.
3. Start with the current v14 entry matching the affected app:
   • Choose (x64) for a 64-bit application.
   • Choose (x86) for a 32-bit application.
   • On a 64-bit PC, repair both x64 and x86 if you do not know which architecture the failing app uses.

Do not rely solely on the year shown in the name. A current shared v14 runtime may be labelled with a 2015–2022-style name even though it services newer Visual C++ applications.

4. Select Modify, then Repair​

Windows 11

1. Select the three dots beside the redistributable entry.
2. Select Modify.

Windows 10

1. Select the redistributable entry.
2. Select Modify.

If Windows displays a User Account Control prompt, select Yes.
In the Microsoft Visual C++ setup window:

1. Select Repair.
2. Wait for the setup process to finish.
3. Select Close when it reports that setup completed.

Repeat this for the other required architecture. For a typical 64-bit Windows PC, repair both the x64 and x86 current v14 entries.
Expected result: The installer completes without an error and the existing package remains listed in Settings. The installed version normally stays the same; repair reinstalls and re-registers its components rather than intentionally downgrading them.

5. Restart Windows when prompted or when testing still fails​

If the setup window requests a restart, restart immediately.
If it does not request one but the app previously produced a DLL-in-use, side-by-side, or startup error, restart Windows before testing. This releases locked files and ensures programs load the repaired runtime fresh.

6. Test the original failure​

1. Launch the same application in the same way that triggered the error.
2. If it starts normally, the repair is complete.
3. If it names a specific missing DLL or says the runtime is missing, note the exact error text before proceeding to the winget method or troubleshooting section.

Verification of success​

After the repair or installation:

1. Return to Settings > Apps > Installed apps in Windows 11, or Settings > Apps > Apps & features in Windows 10.
2. Search for Microsoft Visual C++.
3. Confirm that the relevant x86 and/or x64 entry is present.
4. Launch the affected program.

You can also verify the installed entries from Terminal, Command Prompt, or PowerShell:
winget list "Microsoft Visual C++"
Expected result: winget displays installed Microsoft Visual C++ Redistributable entries. The exact names and versions vary by software installed on the PC.
A listed runtime alone does not prove that every application problem is solved, so the decisive verification is that the original application launches and performs the task that previously failed.

Alternate method: install or repair with winget​

Use winget when:

• The needed current v14 x86 or x64 runtime is missing from Settings.
• The Settings interface does not offer Modify or Repair.
• You prefer a repeatable command-line method.
• You need to repair an installed runtime after identifying its exact name.

1. Open an elevated terminal​

1. Right-click Start.
2. Select Terminal (Admin), Windows PowerShell (Admin), or Command Prompt (Admin).
3. Select Yes if User Account Control appears.

Check that Windows Package Manager is available:
winget --version
Expected result: A version number is displayed.
If Windows says that winget is not recognized, open the Microsoft Store, search for App Installer, install or update it, then open a new terminal window. On a newly configured PC, signing in once and allowing App Installer to finish registering can also be required.

2. Update the winget source​

Run:
winget source update
Expected result: The winget source updates successfully. This refreshes the package catalog before installation.

3. Install the current v14 runtime when it is missing​

For x64 Windows, install the x64 package:
winget install --id Microsoft.VCRedist.2015+.x64 --exact --source winget --accept-source-agreements --accept-package-agreements
Also install x86, because 32-bit applications on 64-bit Windows need it:
winget install --id Microsoft.VCRedist.2015+.x86 --exact --source winget --accept-source-agreements --accept-package-agreements
For 32-bit Windows, install only x86:
winget install --id Microsoft.VCRedist.2015+.x86 --exact --source winget --accept-source-agreements --accept-package-agreements
For ARM64 Windows, install the x64 package first and install x86 as well if you use x86 applications:
winget install --id Microsoft.VCRedist.2015+.x64 --exact --source winget --accept-source-agreements --accept-package-agreements
winget install --id Microsoft.VCRedist.2015+.x86 --exact --source winget --accept-source-agreements --accept-package-agreements
Accept any User Account Control prompt. Do not close the terminal while the installer is running.
Expected result: winget downloads a Microsoft Visual C++ Redistributable installer and reports successful installation, or indicates that an equal or newer version is already installed.

4. Repair a runtime through winget when it already exists​

First, list the locally installed entries:
winget list "Microsoft Visual C++"
Copy the full Name for the runtime you want to repair, then use it in this format:
winget repair --name "paste the exact Name shown by winget here" --exact
For example, if the list identifies one exact x64 runtime name, use that full name inside the quotation marks. Run the command separately for x86 if needed.
Expected result: winget starts the runtime’s repair experience and reports completion. If it reports more than one match, use the exact name shown by winget list rather than a shortened name.

5. Restart and test​

Restart Windows if prompted. Otherwise, close the terminal, restart if the app had a file-lock or side-by-side error, and test the original application again.

Troubleshooting and rollback/escalation​

The runtime is listed, but there is no Modify or Repair button​

Some entries do not expose a repair action through Settings, or the entry may be managed by an application installer.

1. Run:
   winget list "Microsoft Visual C++"
2. Use winget repair with the exact displayed name.
3. If winget repair is unavailable for that entry, install the current supported v14 x64 and/or x86 package with the commands above.
4. If the affected app specifically requires Visual C++ 2013 or earlier, reinstall the exact legacy runtime identified by the app vendor instead of assuming the v14 runtime is a substitute.

winget says “No package found” for the Visual C++ package​

1. Confirm the package source is available:
   winget source list
2. Refresh it:
   winget source update
3. Search the source:
   winget search "Microsoft Visual C++"
4. If the winget source is missing or damaged, reset sources:
   winget source reset --force
5. Run winget source update again, then retry the installation command.

Warning: winget source reset --force removes custom package sources configured for your user account. Before running it on a work-managed device, check whether your organization uses a private package repository. The recovery path is to re-add the required source using your organization’s documented configuration.

Click to expand...

The installer reports error 5, access denied​

This usually indicates insufficient permissions or security software interference.

1. Confirm that you opened Terminal as administrator, or select Modify and approve the UAC prompt.
2. Close the failing application and related background tools.
3. Restart Windows and retry.

Warning: Do not permanently disable antivirus or endpoint protection to install a runtime. If your organization instructs you to temporarily pause protection for testing, disconnect from unnecessary downloads and browsing, retry immediately, and re-enable protection before returning to normal use.

Click to expand...

If the device is managed by work or school policy, contact the IT administrator rather than bypassing endpoint controls.

The installer returns error 32 or says a file is in use​

1. Save work and restart Windows.
2. Before opening other applications, run the repair or installation again.
3. If it still fails, identify and close the application named in the error or log.

A restart is the safest rollback-free way to release a locked runtime file.

The installer returns error 1603​

Error 1603 is a general Windows Installer failure and needs more detail than the code alone.

1. Restart Windows.
2. Install pending Windows updates:
   • Windows 11: Settings > Windows Update > Check for updates.
   • Windows 10: Settings > Update & Security > Windows Update > Check for updates.
3. Restart again if updates require it.
4. Retry the repair or installation as administrator.
5. If it fails again, collect the Visual C++ installer logs from your temporary-files folder. Look for files named similar to:
   dd_vcredist_x64_yyyymmddhhmmss.log
   or:
   dd_vcredist_x86_yyyymmddhhmmss.log

Keep the exact error code and log file for escalation to the application vendor or IT support.

Error 1714: an older runtime cannot be removed​

This commonly means the cached installer files for an older Visual C++ package are missing or corrupted.
Do not manually delete runtime folders, registry keys, or C:\ProgramData\Package Cache folders.

1. Note the exact runtime version and architecture named in the error or dd_vcredist log.
2. In Settings, try uninstalling only that exact broken version.
3. If Windows offers to repair the installation, allow it.
4. Reinstall the current matching runtime after the old entry is repaired or removed.
5. If removal still fails, escalate with the error text and logs. The repair path may require the installer for the exact older version that Windows is attempting to remove.

The app still says a DLL is missing after both x64 and x86 v14 runtimes are installed​

The DLL may not be from the Visual C++ runtime, or the app may require a legacy runtime.

1. Read the error carefully. Files such as VCRUNTIME140.dll, VCRUNTIME140_1.dll, MSVCP140.dll, and related v14 files commonly point to the current Visual C++ runtime.
2. A file such as MSVCP120.dll normally points to Visual C++ 2013; MSVCP100.dll points to Visual C++ 2010. Install the specific legacy runtime required by that application from a Microsoft-signed installer or follow the app vendor’s instructions.
3. Repair or reinstall the affected application itself. Its installer may supply private files, plug-ins, or components that the shared runtime cannot restore.
4. Do not download individual DLL files from third-party DLL sites. Replacing a single DLL can introduce malware, architecture mismatches, or an incompatible library version.
5. If the program is business-critical or managed software, provide the application vendor or administrator with the exact error text, Windows version, runtime architecture, winget list "Microsoft Visual C++" output, and relevant dd_vcredist log.

---

References​

1. Official source: learn.microsoft.com
   
   

   `uninstall` Command | Microsoft Learn

   Uninstalls the specified application.

   learn.microsoft.com
2. Official source: learn.microsoft.com
   
   

   Use WinGet to install and manage applications | Microsoft Learn

   The WinGet command line tool enables developers to discover, install, upgrade, remove and configure applications on Windows computers.

   learn.microsoft.com
3. Official source: support.microsoft.com
   
   

   Repair an Office application | Microsoft Support

   Repair broken Office app installations.

   support.microsoft.com