Why VC++ and .NET Runtime Are Installed but Not Showing in Installed Apps (How to Fix)

If you’ve installed Microsoft Visual C++ Redistributable or .NET Desktop Runtime, but they don’t appear in Settings- Installed apps, you’re not alone. This can happen even when the runtimes are correctly installed and working.

This guide explains how to confirm the runtimes are actually installed, and what you can do to fix or avoid the issue, especially when apps are installed using WiX bundles.

What Causes VC++ and .NET to Disappear from Installed Apps?

This issue commonly occurs when:

• An app is installed using a WiX Burn bundle
• The bundle includes:
  • A main MSI application
  • Visual C++ Redistributable
  • .NET Desktop Runtime
• The main app is later uninstalled
• The runtimes are removed
• The same bundle is installed again

After reinstalling, the runtimes install successfully, but do not reappear in the Installed Apps list. This behavior is reproducible and documented using a WiX bundle that chains:

• .NET 8 Desktop Runtime
• VC++ 2015–2022 Redistributable
• A main MSI installer

Important Thing to Know (Before Fixing Anything)

The runtimes are usually installed correctly. They’re just not registered for display in Windows Settings.

This happens because:

• WiX Burn uses DetectCondition checks
• If the runtime already exists at or above the required version:
  • Installation is skipped
  • Windows does not re-register it in Installed Apps
• Permanent="yes" prevents proper re-listing after uninstall/reinstall cycles

How to Confirm VC++ Runtime Is Installed (Even If It’s Hidden)

Method 1: Check Installed Programs via Command Line

1. Press Win + R
2. Type cmd, press Enter
3. Run:

wmic product where "name like 'Microsoft Visual C++%'" get name,version

If VC++ is installed, it will appear here even if it’s missing from Settings.

How to Confirm .NET Desktop Runtime Is Installed

Method 2: Use the .NET CLI

1. Open Command Prompt
2. Run:

dotnet --list-runtimes

Look for output similar to:

Microsoft.WindowsDesktop.App 8.0.x [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

This confirms the runtime is installed and usable.

Why This Happens Specifically with WiX Bundles

Some Windows applications are installed using a special type of installer called a WiX bundle.

WiX (Windows Installer XML) is a tool developers use to package:

• The main application
• Microsoft Visual C++ Redistributable
• .NET Desktop Runtime
  into a single installer

Because everything is bundled together, WiX controls how and when these runtimes are installed, detected, or skipped.

How to Fix or Avoid This Issue (Best Options)

Option 1: Manually Reinstall the Runtimes (Safest for Users)

If visibility matters:

1. Download official installers:
   • Microsoft Visual C++ Redistributable (x64)
   • .NET Desktop Runtime (matching version)
2. Run the installer
3. Choose Repair or Install

This forces Windows to re-register the runtime in Installed Apps.

Option 2: Don’t Rely on Installed Apps as Proof

For support teams or developers:

• Use:
  • dotnet --list-runtimes
  • Registry checks
• Treat Installed Apps as visual-only, not authoritative

Option 3: Developer Fix (WiX Bundle Improvement)

If you control the installer:

• Avoid aggressive DetectCondition logic
• Re-evaluate Permanent="yes"
• Ensure runtime EXE installers handle re-registration

This prevents confusion during reinstall scenarios.

Is This a Windows Bug?

No. This is expected behavior based on:

• WiX Burn detection logic
• Runtime version checks
• Permanent package handling

Windows is not failing to install the runtime—it’s just not showing it again.

FAQs

Why is VC++ and .NET runtime not showing in Installed Apps?

VC++ and .NET runtime may not appear in Installed Apps if the installer detects an existing version and skips re-registering it. The runtime is usually installed and working normally.

Is it safe if VC++ or .NET runtime is missing from Installed Apps?

Yes. If your applications run correctly and command-line checks confirm the runtime is present, it is safe. This is a display issue, not a system error.

How can I check if .NET runtime is actually installed?

Open Command Prompt and run dotnet --list-runtimes. If the runtime appears in the list, it is installed and functioning properly.

How do I verify Visual C++ Redistributable installation?

You can check Visual C++ installation using Command Prompt with system queries or by reinstalling the official redistributable to confirm its presence.

Should I reinstall VC++ and .NET runtime if they are not showing?

Reinstall only if an application fails to launch or if you want the runtime to appear in Installed Apps. Otherwise, no action is required.

Can missing VC++ runtime cause app crashes?

Only if the runtime is truly missing. If it is installed but hidden, applications will continue to work normally.

Why does this happen after reinstalling an application?

This often happens when apps use bundled installers that detect existing runtimes and skip reinstallation, which prevents them from showing again in Installed Apps.

Is this issue caused by Windows Update?

No. This behavior is related to installer detection logic, not Windows Update or system corruption.

Does this problem affect Windows performance or security?

No. Hidden runtimes do not affect system performance, stability, or security updates.

How do I make VC++ and .NET runtime visible again?

Download the official Microsoft installers and choose Repair or Install. This forces Windows to re-register the runtime in Installed Apps.

Do I need third-party tools to fix this issue?

No. Microsoft’s official installers and built-in Windows tools are sufficient.