Fix it now
1642 is ERROR_PATCH_TARGET_NOT_FOUND, and Microsoft’s wording is precise: the installer cannot install the upgrade patch because the program being upgraded may be missing, or the patch updates a different version of the program. It is a statement about matching, not about damage. Confirm what is installed, then confirm what the patch targets.
msiexec /p C:\temp\patch.msp /l*v C:\temp\patch.log REINSTALL=ALL REINSTALLMODE=omus
- Note the exact installed version from Settings, Apps, Installed apps, including the build field.
- Compare it against the prerequisite in the vendor’s release notes. A patch built for one build will not apply to another, newer or older.
- Check the edition, architecture and language of the installed product, not of Windows. A 32-bit application on 64-bit Windows needs the 32-bit patch, and localised products often have separate patch files.
- Read the log for the target product code the patch is looking for and what the engine found instead. That line ends most of these investigations.
- Where several patches exist for one product, apply them in the order the vendor specifies rather than newest first.
If the product is not the version the patch targets, the fix is to obtain the matching patch or to bring the product to the base version the patch expects. There is no switch that makes a patch apply to a product it was not built for.
If the patch applies and the product reports the patched build, you are done. If it still finds no target, the next section covers the three things it is matching on.
Why it happens
A patch package holds transforms – differences to be applied to an installer database – together with metadata describing which product codes and which version ranges it is valid for. When you run it, Windows Installer looks for an installed product that matches that metadata, applies the transforms to a working copy of the product’s database, and performs the resulting installation. 1642 is raised at the first step: nothing installed matched.
Matching is stricter than most people expect, and it is not only about the version number. The patch names target product codes, and a product code differs between editions, between architectures and often between languages. So a machine can be running exactly the version printed in the release notes and still have no target, because it is the localised build or the 32-bit build and the patch is not. Microsoft’s own wording covers both halves of this: the program being upgraded may be missing, or the patch updates a different version of the program.
There is a second, less obvious way to end up here. Patch state for a product is registered under the installer’s own user data, in the Patches subkey beneath the product’s entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products. Where those entries are missing or inconsistent, the engine’s view of what is installed does not match reality and a patch that should apply reports no target. That is a registration problem rather than a version problem, and it is worth checking before you go hunting for a different patch file.
The installed product is a different version from the patch target
You have this one if The product is clearly installed, and its version does not match what the patch’s release notes require.
- Note the exact installed version, including the build field.
- Obtain the patch that matches it, or bring the product to the base version the patch expects by applying the intervening updates first.
- For products distributed as cumulative updates, install the latest full package instead of chaining patches.
- Re-apply and check the log for the target product code being matched.
The patch targets a different edition, architecture or language
You have this one if The version number matches and the patch still finds no target, and the product exists in several editions or languages.
- Confirm the architecture of the installed product rather than of Windows.
- Check which edition and language the patch is built for; localised products commonly have their own patch files.
- Download the patch variant matching the installed product and retry.
- Where the vendor ships one patch for all editions, log the attempt and send them the section showing the target codes.
The product’s patch registration is missing or inconsistent
You have this one if The version, edition and architecture all match, and the engine still reports no target – often on a machine that has been imaged, migrated or heavily cleaned up.
- Look under
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Productsfor the product and its Patches subkey. - Compare against a healthy machine running the same build; missing entries there explain a patch that should apply and does not.
- Repair the product from its original package before patching, so the registration is rebuilt from something known.
- Take an image or a restore point before changing anything under the installer’s user data.
You are trying to remove a patch that cannot be removed
You have this one if 1646, 1647 or 1649 rather than 1642, during the uninstall of an update rather than the install of one.
- Check whether the patch is listed as applied to the product first. 1647 simply means it is not applied, so there is nothing to remove.
- 1646 means the package was not built as a removable patch, which is a decision made by whoever packaged it and not something you can change.
- 1649 means removal was disallowed by policy; look at the Windows Installer machine policies before assuming the patch is at fault.
- Where the patch genuinely cannot be removed, the supported route is to uninstall and reinstall the product at the version you want.
A set of patches cannot be sequenced
You have this one if 1648 when applying a group of patches, or when a repair triggers reapplication of everything already installed.
- Apply the patches one at a time, in the order the vendor lists, logging each one.
- Identify the patch that breaks the sequence and check whether it supersedes another already applied.
- Where the vendor publishes a cumulative package, use that instead of a chain of individual patches.
- Note that 1648 is also one of the errors a missing installer cache produces, so check the cache before blaming the patch set.
Full reference
The six codes, as Microsoft states them
| Code | Constant | Message |
|---|---|---|
| 1642 | ERROR_PATCH_TARGET_NOT_FOUND | The installer can’t install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program |
| 1637 | ERROR_PATCH_PACKAGE_UNSUPPORTED | This patch package can’t be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service |
| 1647 | ERROR_UNKNOWN_PATCH | The patch isn’t applied to this product |
| 1646 | ERROR_PATCH_REMOVAL_UNSUPPORTED | The patch package isn’t a removable patch package |
| 1648 | ERROR_PATCH_NO_SEQUENCE | No valid sequence could be found for the set of patches |
| 1649 | ERROR_PATCH_REMOVAL_DISALLOWED | Patch removal was disallowed by policy |
A missing installer cache is a different error
It is worth being explicit, because the two problems get conflated constantly. When the cached base package for a product is missing, Microsoft’s guidance lists the errors you get as 1635, 1636, 1714, 1648 and 1603 – not 1642. So a machine whose cache has been emptied by a cleanup tool will fail to repair, uninstall and patch, and it will tell you so with those numbers. If what you have is 1642, the cache is not the thing to chase; the patch’s target is.
| Symptom | Which article you are in |
|---|---|
| 1642 on a patch, other products repair and uninstall normally | This one: the patch does not match the installed product |
| 1635 or 1636 on a patch | The patch package itself cannot be opened or is not valid |
| 1714, 1648 or 1603 across several unrelated products | The installer cache is missing; restore it before anything else |
| 1612 or 1706 on a repair or uninstall | The installation source cannot be found |
If the cached base package really is gone
Do not respond to a missing cached package by uninstalling the product. The uninstall is precisely the operation the missing cache prevents – Microsoft documents it failing with 1714, the older version cannot be removed – and a failed removal can leave a product half gone with its registration destroyed and no supported way back. Take a system image or a restore point first, and restore the cache before you attempt anything destructive.
- Repair from the original package for the exact build, using
msiexec /fv "C:\src\app.msi". Thevoption runs from source and re-caches the local package; the defaultomusset does not, so plain/fwill report success and change nothing. - Where you have the original media or the patch itself, Microsoft’s cache-restore guidance covers extracting it and placing the .msi or .msp into
%windir%\Installerunder the correct cached name. - The FixMissingMSI tool that Microsoft’s guidance points at scans for missing cached files and re-caches them from the original media in one step.
- Restore from a system state backup where the above is not possible.
- Do not use
/fvfor a first installation of an application or feature. Microsoft rules that out explicitly.
REINSTALLMODE, and what the letters mean
REINSTALLMODE shares its argument list with the /f repair option, so the letters mean the same things: o reinstalls a file that is missing or older, m and u rewrite machine and user registry entries, s overwrites shortcuts, a forces every file to be reinstalled, and v runs from source and re-caches the local package. omus is the conventional set for patching because it refreshes files and registration without forcing a full file replacement. If you specifically want the cached package refreshed as part of the operation, v is the letter that does it – and it is the one people leave out.
Before you contact the vendor
- Record the installed version, edition, architecture and language, and the same four facts about the patch.
- Run the patch with
/l*vand keep the section naming the target product codes. - Check the same patch on a second machine at the same build. A patch that applies elsewhere points at that machine’s registration; one that fails everywhere points at the patch.
- Confirm the base product repairs cleanly before patching. A product that will not repair will not patch either, and the patch error is then a symptom.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1642 |
ERROR_PATCH_TARGET_NOT_FOUND: no installed product matched the patch’s target – the program may be missing, or the patch updates a different version of it | Microsoft Learn |
1637 |
ERROR_PATCH_PACKAGE_UNSUPPORTED: the installed Windows Installer service cannot process this patch package | Microsoft Learn |
1647 |
ERROR_UNKNOWN_PATCH: the patch is not applied to this product, so there is nothing to remove | Microsoft Learn |
1646 |
ERROR_PATCH_REMOVAL_UNSUPPORTED: the patch package is not a removable patch package | Microsoft Learn |
1648 |
ERROR_PATCH_NO_SEQUENCE: no valid sequence could be found for the set of patches; also one of the errors a missing installer cache produces | Microsoft Learn |
1649 |
ERROR_PATCH_REMOVAL_DISALLOWED: patch removal was disallowed by policy | Microsoft Learn |
Confirm the fix worked
- The patch appears under the product’s installed updates, or the product’s version has moved to the patched build.
- Re-running the patch reports that it is already applied rather than failing.
- The application starts and reports the expected version.
- A repair of the base product still completes cleanly after patching.
- The same patch applies on a second machine at the same build, which tells you the fix was general.
Questions people ask about this
Does fixing this require buying anything?
No. Patches for software you already own come from the vendor as part of the product. What you may need to obtain is the original installer for the exact build you are running, which is a support request rather than a purchase.
Can I extract an MSP and copy the files in by hand?
You can extract the contents, and copying files over an installed product bypasses the component registration and reference counting the installer maintains. The next repair or upgrade will undo or conflict with it. Fix the target instead.
Why does the patch work on one machine and not another?
Because the two machines are not at the same base version, edition, architecture or language, or because one machine’s patch registration under the installer’s user data is inconsistent. Compare all of those before assuming the patch file is faulty.
What does REINSTALLMODE=omus do?
It reuses the same letters as the /f repair option: reinstall a file that is missing or older, rewrite machine and user registry entries, and overwrite shortcuts. It refreshes resources rather than skipping them. Note that it does not re-cache the local package – that is the separate v option.
My installer cache was emptied. Is that why I get 1642?
No. Microsoft lists the errors a missing cache produces as 1635, 1636, 1714, 1648 and 1603. 1642 means the patch found no matching target. If you have both problems, restore the cache first – and do not try to uninstall your way out of it, because that is the operation the missing cache blocks.
