Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 1638

MSI 1638 and 0x80070666: A Newer Version of This Product Is Already Installed

10 min read Updated October 5, 2026 Installers, Runtimes & App Deployment

Fix it now

1638 is ERROR_PRODUCT_VERSION: another version of this product is already installed, so this one cannot continue. That is not a fault – the installer is refusing to put an older build over a newer one. With Visual C++ redistributables the newer build already satisfies the dependency, so a script should usually treat 1638 as success.

Run this in an elevated PowerShell to see what is already installed

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object DisplayName -like "*Visual C++*" | Select-Object DisplayName, DisplayVersion
  1. Compare what is installed against what the package contains. Settings, Apps, Installed apps shows the product name and version, and the redistributable’s own file version is on the Details tab of the downloaded installer’s properties.
  2. If the installed build is the same or newer and the application only needs the runtime present, stop. There is nothing to fix.
  3. In your deployment tool, add 1638 to the return codes treated as success so the step stops reporting a failure it should not.
  4. Better still, add a detection rule so the package is not run at all when a suitable version is already there.
  5. If you genuinely need the older build, uninstall the newer one first from Settings, Apps, Installed apps, then run the older package immediately.

Match the runtime to the application, not to Windows: a 32-bit application needs the x86 redistributable even on 64-bit Windows. On 64-bit Windows those 32-bit products register in the 32-bit registry view, so check both views or use Settings, Apps, Installed apps, which lists all of them.

If the application runs, you are finished – the dependency was already met. If it still will not start, the next section explains how the comparison works and why 1638 is rarely the real problem.

Why it happens

Every MSI carries an UpgradeCode identifying the product family and a ProductVersion identifying the build. During installation the engine looks for other products sharing the UpgradeCode and compares versions. Where it finds a version higher than the one in the package you are running, it stops and returns 1638 rather than downgrading a working installation. Microsoft’s own message text points you at Add/Remove Programs to configure or remove the existing version, which is the honest answer: the machine already has something newer.

One detail of that comparison surprises people regularly. Microsoft documents ProductVersion as major.minor.build and states that the installer uses only the first three fields – if you include a fourth field, it is ignored. So two builds that differ only in a fourth field compare as identical. If you ship in-house software and your upgrades are silently not applying, that is usually why.

Visual C++ redistributables make this visible more often than anything else, because so many applications bundle one. Microsoft’s current position is that Visual Studio 2017 and later share the same redistributable files, that an application built with any v14 build tools can use the latest v14 redistributable, and that the version installed must be the same as or later than the build tools used to create the application. When Visual Studio 2015 support ended, the v14 runtime remained binary compatible with applications built using the 2015 build tools. So the refusal is correct: whatever is already there satisfies the older application.

A newer runtime is already present

You have this one if The failing package is a Visual C++ redistributable and the machine already lists a higher version of the same architecture.

  1. Confirm the installed version in Settings, Apps, Installed apps.
  2. Do nothing further. The dependency is met and the application will run.
  3. In the deployment step, map 1638 to success.
  4. If the application still fails to start, the missing dependency is a different one; inspect its imports rather than forcing the redistributable.

Install the architecture the application needs, not the architecture of Windows. A 32-bit application needs the x86 runtime even on 64-bit Windows, and mixed estates need both installed.

Your upgrade is not being seen as an upgrade

You have this one if You ship an in-house package, the new build refuses to install over the old one, and the two differ only in the fourth field of the version.

  1. Increment one of the first three fields of ProductVersion for every release you intend to be an upgrade; the fourth field is ignored.
  2. Generate a new ProductCode for a major upgrade while keeping the UpgradeCode constant.
  3. Rebuild and test the upgrade path on a machine that already carries the previous build.
  4. Log the install with /l*v and confirm the related-products action now finds and removes the earlier version.

You need the older build deliberately

You have this one if A specific application requires an exact earlier version and the machine has been updated past it.

  1. Uninstall the newer version from Settings, Apps, Installed apps.
  2. Install the required older build immediately afterwards, before anything reinstalls the newer one.
  3. Expect other applications to be affected; a shared runtime downgrade is machine-wide.
  4. Ask the vendor whether the requirement is genuine or simply an untested installer check, because forcing a downgrade is disruptive and often unnecessary.

The older product cannot be removed during the upgrade

You have this one if Message 1714 in the log – the older version of the product cannot be removed – rather than a clean 1638.

  1. Check whether the older product’s cached package still exists. A missing installer cache is a documented cause of 1714.
  2. Restore the cache or repair the older product from its original package with msiexec /fv, which re-caches the local package.
  3. Uninstall the older product on its own, then run the new package as a clean installation.
  4. If the older product will not uninstall at all, try Repair or Reset on its entry in Settings, Apps, Installed apps, which is where Microsoft’s current guidance for blocked removals sends you; the old downloadable troubleshooter is no longer offered.

Full reference

The three codes

Code Constant or type Message
1638 ERROR_PRODUCT_VERSION Another version of this product is already installed. Installation of this version can’t continue. To configure or remove the existing version of this product, use Add/Remove Programs in Control Panel
0x80070666 HRESULT form of 1638 Facility 0x8007 with 0x666, which is 1638; a bootstrapper reporting this is reporting 1638
1714 Internal message The older version of [2] cannot be removed. Contact your technical support group. System Error [3]

How version comparison actually works

Field Maximum Used in comparison
Major 255 Yes
Minor 255 Yes
Build or update version 65,535 Yes
A fourth field – No: the installer ignores it

Two consequences follow, and both bite in-house packaging teams. A build pipeline that only ever increments a fourth field produces packages that all look like the same version to the installer, so upgrades quietly do not happen. And a version that was rolled back for testing will refuse to install over the one already there, which is 1638 doing its job rather than a broken package.

Visual C++ redistributables specifically

  • The v14 redistributable serves applications built with the v14 build tools from Visual Studio 2017 onwards, and remains binary compatible with applications built using the Visual Studio 2015 build tools.
  • The version installed must be the same as or later than the build tools used to create the application, which is why a newer runtime satisfying an older application is the normal case rather than an exception.
  • Each architecture installs separately. An estate running both 32-bit and 64-bit applications needs both x86 and x64 present.
  • Older families – 2010, 2012, 2013 – are separate products and coexist with v14. What you cannot do is put an older build over a newer one inside the same family, which is where 1638 comes from.
  • To read the version of a redistributable you have downloaded, open its properties and look at File version on the Details tab.

Making deployment stop reporting a false failure

  1. Add a detection rule to the deployment step so the package runs only when it is needed. This is better than mapping return codes, because the step stops doing unnecessary work.
  2. Where a detection rule is impractical, add 1638 to the list of return codes treated as success. Map 0x80070666 too if a bootstrapper wraps the package.
  3. Log with /l*v on one machine and confirm the engine is comparing the versions you think it is.
  4. Do not chain a forced uninstall of the newer runtime into an automated deployment. It is machine-wide, other applications depend on it, and you will not find out which ones until later.

When 1638 is hiding a real problem

The one case worth taking seriously is 1714 in the log. That is the older product refusing to be removed as part of the upgrade, and the usual reason is a missing installer cache – which means the machine has a broader problem than this package. Restore or re-cache the older product first, using a repair from source with /fv, and then run the upgrade. Forcing the new package on top of a product that cannot be removed leaves two registrations and a machine that neither repairs nor uninstalls cleanly.

Every code this article covers

Code What it points at Source
1638 ERROR_PRODUCT_VERSION: another version of this product is already installed, so this version cannot continue Microsoft Learn
0x80070666 The same result in HRESULT form: facility 0x8007 with 0x666, which is 1638 Microsoft Learn
1714 The older version of the product cannot be removed, reported with the underlying system error alongside it Microsoft Learn

Confirm the fix worked

  1. The required product family and architecture appear in Settings, Apps, Installed apps.
  2. For runtimes, the installed version is at or above what the application requires, and both architectures are present if the estate needs both.
  3. The application that needed the dependency starts.
  4. The deployment step now reports success rather than a failed exit code, either through detection or through the mapped return code.
  5. A second machine of the same build behaves the same way, so you know the rule and not the machine was the problem.

Questions people ask about this

Do I need to buy anything?

No. This is a version comparison, not a licensing check. Visual C++ redistributables are free downloads from Microsoft, and 1638 usually means the dependency is already satisfied.

Should my script treat 1638 as an error?

Generally not. If the goal is that a suitable runtime is present, 1638 tells you it already is. Map it to success and add a detection rule so the installer is skipped when it is unnecessary.

Can I install several Visual C++ runtimes side by side?

Yes, across families – 2010, 2012, 2013 and the v14 runtime coexist, and each architecture installs separately. What you cannot do is put an older build over a newer one within the same family.

How do I know which runtime an application needs?

Check the vendor’s system requirements first. Failing that, inspect the application’s binaries to see which runtime DLLs and which architecture they import – and remember the answer is about the application, not about Windows.

My in-house upgrade will not install over the previous build. Why?

Almost certainly because the two versions differ only in the fourth field, which Microsoft documents the installer as ignoring. Increment one of the first three fields for anything you intend to be an upgrade.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error 0x803F8001: This App Is Not Licensed for Your Account or This Device Free Fix MSI 1402 and 1406: Could Not Open Key or Write Value During Installation Free Fix MSI 1327: Invalid Drive – Fixing Broken Shell Folder and Mapped Drive Paths Free Fix MSI 1612 and 1706: Installation Source Missing When You Repair or Remove Apps
โ† Back to Knowledge Base