Fix it now
1612 is ERROR_INSTALL_SOURCE_ABSENT – the installation source for this product is not available – and 1706 says the same thing as “No valid source could be found for product”. It appears when you repair, modify, patch or uninstall rather than when you install, because those operations need the package the product came from. Supply that exact package, or restore the cached copy; do not delete the registration and hope.
msiexec /fv "D:\src\app.msi" /l*v C:\temp\repair.log
- Find where the product was installed from: locate it under
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstalland read theInstallSourcevalue. - Restore that path where you can – reconnect the share, or copy the original package back into place – then retry from Settings, Apps, Installed apps.
- If you have the package but the local cached copy is gone, use
/fvrather than plain/f. Microsoft documents the default argument list for/fas omus, andv– run from source and re-cache the local package – is not in it. - It has to be the identical build. A newer download will be rejected, and the log will tell you it was.
- If the software no longer exists anywhere, work through Microsoft’s own guidance for programs that will not install or uninstall: the repair and reset options on the entry in Settings, Apps, Installed apps, then removal from there. The downloadable Program Install and Uninstall troubleshooter is no longer offered on that page, so do not plan a rebuild around it.
Do not use /fv for a first installation of an application or feature. Microsoft states that explicitly, and it is the one restriction on the option that matters.
If the repair or uninstall completes without asking for a source, you are done. If it still asks, the next section explains what the installer is looking for and why.
Why it happens
When an MSI is installed, Windows Installer keeps a copy of the package in the installer cache under %windir%\Installer, with a generated name. That copy carries the tables – components, registry entries, the action sequence – but not the file payload. It is what makes an uninstall possible without the original media, because the engine can read the component list and reverse it.
What the cached copy does not contain is the files. So the moment an operation needs to replace a file – which a repair always does and a modify usually does – the engine goes looking for the full source. It finds candidate locations in the product’s source list, recorded at install time and updated whenever you point it somewhere new. If the cached package is missing as well, even a plain uninstall struggles, because there is nothing left describing what to remove.
This is why cleanup utilities that empty the installer cache cause so much trouble, and Microsoft’s own warning is blunt: Windows automatically manages that directory when applications install and update packages, and manual changes in it can cause problems, including the ones people then come looking for help with. The errors a missing cache actually produces are 1635, 1636, 1714, 1648 and 1603 – not this one. If you are seeing 1612 or 1706, the source list is the thing to chase first.
The original network share or media is gone
You have this one if The prompt asks for a specific path – an old server name, a drive letter, someone’s Downloads folder – that no longer exists.
- Read
InstallSourceunder the product’s Uninstall key to see exactly what it wants. - Put an identical copy of the package at that exact path if you can; recreating the share name is often the fastest fix.
- Otherwise, when the browse dialog appears, point it at a folder holding the identical package so the engine records the new location.
- For scripted work, run the operation against the package path directly rather than by product code.
The cached copy of the package is missing
You have this one if Several unrelated products fail the same way at once, and a disk-space tool was run on the machine.
- Obtain the exact version originally installed – not a newer one – from the vendor.
- Re-cache it as part of the repair:
msiexec /fv "C:\src\app.msi". Thevoption runs from source and re-caches the local package; the defaultomusset does not. - Where the exact build cannot be obtained, restore the cache from a system state backup or a machine image rather than removing the registration.
- Only after the cache is back should you attempt an uninstall.
Never empty %windir%\Installer to reclaim space. Microsoft warns that manual changes there cause exactly this class of problem, and once it is gone the products on that machine lose the ability to repair, patch or remove themselves cleanly.
The package you have is a different build
You have this one if You supplied a package, the engine accepted it, and the operation still failed – often with 1706 or a source-file error in the log.
- Compare the installed version in Settings, Apps, Installed apps against the version of the package you have.
- Ask the vendor for the exact build. Many keep an archive of previous releases even when the download page shows only the current one.
- Where the vendor cannot supply it, treat the product as unremovable by normal means and take the orphaned-registration route below.
- Re-run with logging and read which file the engine could not find; 1308 and 1309 in the log name it.
The registration is orphaned
You have this one if The product is listed in installed applications, its files are gone, and 0x80070645 appears when you act on it by product code.
- Try the supported route first: open the entry in Settings, Apps, Installed apps and use Repair, Reset or Uninstall there, which is what Microsoft’s current guidance for blocked installs and removals points at.
- Where that cannot see or shift the product, export the product’s key under
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstallbefore touching anything. - Remove the registration so the entry disappears from the installed applications list.
- Delete any leftover program folder and reinstall the current version cleanly if you still need the software.
The source is a share the install account cannot read
You have this one if The path exists and you can browse to it, and a deployment tool or scheduled task still reports 1612.
- Remember that part of the operation runs as the local system account, which has no rights to most shares.
- Grant read access to the computer accounts, or copy the package locally before running the operation.
- Avoid mapped drive letters in scripts; use the UNC path or a local copy.
- Retry from the deployment tool rather than interactively, since that is the context that failed.
Full reference
The codes, as Microsoft states them
| Code | Constant or type | Message |
|---|---|---|
| 1612 | ERROR_INSTALL_SOURCE_ABSENT | The installation source for this product isn’t available. Verify that the source exists and that you can access it |
| 1706 | Internal message | No valid source could be found for product [2] |
0x8007064C |
HRESULT form of 1612 | Facility 0x8007 with 0x64C, which is 1612 |
0x80070645 |
HRESULT form of 1605 | 1605 is ERROR_UNKNOWN_PRODUCT: this action is only valid for products that are currently installed |
| 1308 | Internal message | Source file not found: [2] |
| 1309 | Internal message | Error attempting to open the source file: [3]. System error code: [2] |
1308 and 1309 are worth separating in your head. 1308 means the engine looked and the file was not there. 1309 means it found the file and could not open it, and it hands you the underlying system error code to explain why – which is usually a permission or a locked file rather than a missing source at all.
The repair options, and the one that re-caches
| Option | What it does |
|---|---|
p |
Reinstalls only if the file is missing |
o |
Reinstalls if the file is missing or an older version is installed |
e |
Reinstalls if the file is missing or an equal or older version is installed |
d |
Reinstalls if the file is missing or a different version is installed |
c |
Reinstalls if the file is missing or the stored checksum does not match |
a |
Forces all files to be reinstalled |
u |
Rewrites all required user-specific registry entries |
m |
Rewrites all required computer-specific registry entries |
s |
Overwrites all existing shortcuts |
v |
Runs from source and re-caches the local package – not part of the default set |
msiexec /f with no letters uses omus, which is the combination most people are unknowingly running. It reinstalls files that are missing or older, rewrites user and machine registry entries, and overwrites shortcuts. It does not touch the cached package. If your problem is a missing cache, /f on its own will report success and leave you exactly where you were, which is why /fv matters here.
Restoring a cache that has been emptied
- Identify which products are affected. Several failing at once is the signature of a cleanup tool rather than a single bad install.
- Obtain the original media or patch package for the exact version installed.
- Re-cache through a repair from source with
/fv, which is the supported route and does not require you to place files by hand. - Where a repair is not possible, Microsoft’s guidance for restoring missing cache files covers extracting the original package and placing it in the cache under the correct name, and points at the FixMissingMSI tool that automates the scan and the re-cache.
- Restore from a system state backup where one exists and the above fails.
Do not attempt an uninstall to “clear out” a product whose cached package is missing. That is precisely the operation the missing cache prevents – Microsoft documents 1714, “The older version of [2] cannot be removed”, among the errors it produces – and a failed removal can leave the product half gone with no supported path back. Restore the cache or repair from source first, and take a system image or a restore point before you start.
Why the machine asks for a CD nobody used
The source list records where the product was installed from, and on a machine built from an image or a task sequence that path may be one no human ever saw. It is not evidence of anything sinister. Point the browse dialog at any folder holding the identical package and the engine records the new location, after which repairs and removals work normally.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1612 |
ERROR_INSTALL_SOURCE_ABSENT: the installation source for this product is not available; verify it exists and you can access it | Microsoft Learn |
1706 |
No valid source could be found for the product – the same complaint as an internal message | Microsoft Learn |
0x8007064C |
The same missing-source result in HRESULT form: facility 0x8007 with 0x64C, which is 1612 | Microsoft Learn |
0x80070645 |
HRESULT form of 1605, ERROR_UNKNOWN_PRODUCT: this action is only valid for products that are currently installed | Microsoft Learn |
1308 |
Source file not found: the engine looked for a file the operation needed and it was not there | Microsoft Learn |
1309 |
Error attempting to open the source file, with the underlying system error code reported alongside it | Microsoft Learn |
Confirm the fix worked
- The repair or uninstall completes without prompting for a source.
- The product has gone from Settings, Apps, Installed apps, or the repair reports success.
- For products you repaired with
/fv, a cached package for them exists again under%windir%\Installer. - A second operation on the same product – a repair straight after an uninstall test on a spare machine – behaves normally.
- Another MSI installs cleanly afterwards, which tells you the installer engine as a whole is healthy.
Questions people ask about this
Is there anything to buy to resolve this?
No. You already own the software; what is missing is the installer file, and the vendor you bought it from should supply the matching build. Nothing about 1612 is a licence state.
Can I delete %windir%\Installer to free space?
No. Microsoft warns that Windows manages that directory automatically and that manual changes in it cause problems. It holds the cached packages and patches every installed product needs for repair, patching and removal.
Why does msiexec /f not restore the cached package?
Because the default argument list for /f is omus, and re-caching is the separate v option, documented as running from source and re-caching the local package. Use /fv – but never for a first installation, which Microsoft rules out explicitly.
What if the vendor no longer exists?
Then the orphaned-registration route is what is left: export the keys, remove the registration, and clean up the program folder by hand. Do it deliberately, take an image first, and write down what you removed.
Several products broke at once. What happened?
Almost certainly a disk cleanup tool emptied the installer cache. Expect 1635, 1636, 1714, 1648 and 1603 alongside 1612 across different products, and work through them by restoring the cache rather than by uninstalling anything.
