can someone tell me how to fix this

Question

can someone tell me how to fix this

Ryan Wilson 0

User's image

0 comments

2 answers

Your answer

Answer 1

Marcin Policht 101.2K MVP Volunteer Moderator

Try downloading and installing the supported Microsoft Visual C++ Redistributable for Visual Studio 2015–2022 package. Microsoft combines the Visual C++ 2015, 2017, 2019, and 2022 runtimes into the same redistributable package, so installing the current version should replace or repair older 14.x runtime files, including 14.51.36247.

Download the official x86 installer from Microsoft:

https://aka.ms/vs/17/release/vc_redist.x86.exe

After downloading, right-click vc_redist.x86.exe and select Run as administrator. If the runtime is already installed, the installer will show a Repair option. Choose Repair to restore missing or corrupted files. If Repair is not offered, uninstall the existing Microsoft Visual C++ 2015-2022 Redistributable (x86) from Settings → Apps → Installed apps (or Control Panel → Programs and Features) and then run the installer again.

After installation completes, restart Windows. You can verify the installation by checking Apps → Installed apps for an entry similar to Microsoft Visual C++ 2015-2022 Redistributable (x86).

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Ryan Wilson 0 Reputation points

2026-07-26T17:02:32.2733333+00:00

i tried what you said to do but now this pops up
Marcin Policht 101.2K Reputation points MVP Volunteer Moderator

2026-07-26T22:30:52.4833333+00:00
Open PowerShell as Administrator. List all Visual C++ installer registrations:

Get-ChildItem HKLM:\SOFTWARE\Classes\Installer\Products | Get-ItemProperty | Where-Object { $_.ProductName -like "Visual C++" } | Select-Object ProductName, PSChildName

Locate the entry for Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.44.35211. Note its PSChildName value.

Display all properties for that installer registration by replacing <PSChildName> with the value from Step 2:

Get-ItemProperty "HKLM:\SOFTWARE\Classes\Installer\Products<PSChildName>" | Format-List *

If the output contains a property named ProductCode (or ProductID) with a value like:

{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}

that is the GUID required by Windows Installer.

Use the GUID to force the uninstall:

msiexec /x {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Answer 2

Hi, good day!

Please try the following steps:

First, uninstall all existing Microsoft Visual C++ Redistributable versions. Go to Settings > Apps > Installed apps (or Control Panel > Programs and Features) and remove every entry for Microsoft Visual C++ Redistributable.

Before making any changes to the registry, it's a good idea to create a backup. In Registry Editor, select File > Export, choose a location to save the backup, and make sure All is selected under Export range.

Once the backup is complete, press Windows + R, type regedit, and press Enter.

Navigate to:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products

Review each subkey under Products. In the right pane, check the ProductName value. If it begins with Microsoft Visual C++ 20XX, right-click that subkey and select Delete.

After you've finished, restart your computer to apply the changes, then try the installation again.

I look forward to receiving your update and I'm willing to collaborate with you till we resolve the issue. Do keep me informed by clicking "Add comment" below.

John DeV 168.1K Reputation points Independent Advisor

2026-07-27T08:10:56.2533333+00:00

I'm just checking in to see if you've had a chance to try the solution I suggested.

If you have, could you let me know the outcome? Did it resolve the issue, or are you still experiencing the same problem?

I look forward to your update.