Skip to content

WINDOWS INSTALLER ERROR · ERROR_INSTALL_SOURCE_ABSENT

Error 1612 and 1706: Installation Source Is Not Available

To remove, repair or update a program, Windows Installer needs the package it kept when the program was installed, or the original installation source. It could not reach a source, so it cannot go on.

WHAT WINDOWS SAYS

The installation source for this product isn't available. Verify that the source exists and that you can access it.

Inside a setup's own window the same condition is message 1706: "No valid source could be found for product [2].", where [2] is the product's name.

Wording from Microsoft's documentation, linked under Sources.

TECHNICAL SUMMARY

Number1612, 1706
Windows nameERROR_INSTALL_SOURCE_ABSENT
Where it appearsExit code of msiexec.exe
In PC Tweaker UninstallerShows the exit code

What causes Error 1612 and 1706

  • Files are missing from the Windows Installer cache. Microsoft explains that the cache, by default in C:\Windows\Installer, stores files that are required for uninstalling and updating applications, that it should not be deleted, and that problems may not show until you uninstall, repair or update a product. It lists 1612 among the messages a missing cache file can trigger.
  • The original source is no longer where it was: the download folder, disc, USB drive or network share the program was installed from. Microsoft's message asks you to verify that the source exists and that you can access it.

How to fix Error 1612 and 1706, safest step first

Microsoft's guidance for a missing cache is short and cautious. In its order, with the step that changes nothing first:

  1. Make the original source reachable again

    Reconnect the drive or network share the program was installed from, or put the same version of its installer back in the folder it was run from, then try the removal or repair again.

    To undo: Nothing to undo: no setting changes.

  2. Run the same version's setup and choose Repair

    Download the installer of the exact version that is installed (the version is shown in Settings > Apps > Installed apps) and run it; if it offers Repair, choose that. Microsoft's msiexec reference documents a repair option, /fv, that runs from source and re-caches the local package.

    To undo: A repair reinstalls the program's files and has no undo button. Make a restore point first if the program matters to you.

  3. Get a current installer from the publisher, or ask its support

    Download the program's current setup from its publisher and run that one. For missing cache files Microsoft says to ask the vendor or support team for the application, and to follow the steps the vendor recommends to restore the files.

    To undo: Nothing to undo until a setup completes; after that, uninstalling the program is the way back.

  4. Do not copy cache files from another PC

    Microsoft states that missing files cannot be copied between computers because the files are unique, that it is not possible to replace only the missing files from an earlier backup, and that a full system state restoration is required to bring them back. It names System Restore points among the options if they were made before the files were deleted.

    To undo: Nothing to undo: this step is a warning, not a change.

  5. On Windows 10, run Microsoft's Program Install and Uninstall troubleshooter

    Microsoft's page offers the download under its Windows 10 tab. Microsoft says it fixes corrupted registry keys on 64-bit systems, corrupted registry keys that control update data, and problems that prevent programs from being installed, completely uninstalled or updated, or that block uninstalling through Add or Remove Programs. On Windows 11 the same page gives the Settings steps instead.

    To undo: The troubleshooter has no undo of its own, which is why a restore point comes before it.

Check it yourself, without changing anything

  1. Check that every cached package still exists (PowerShell)

    It prints only the products whose cached package is missing; no output means every cached package is there (on the Windows 11 build 26300 PC we ran it on, all 168 were). Nothing is changed.

    Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\*\Products\*\InstallProperties' -ErrorAction SilentlyContinue |
  Where-Object LocalPackage |
  Select-Object DisplayName, LocalPackage, @{ n='CachedPackageExists'; e={ Test-Path $_.LocalPackage } } |
  Where-Object { -not $_.CachedPackageExists }
    PowerShell

  2. Read what Windows Installer logged (PowerShell)

    Microsoft documents event 1033 (installation completed with status) and 1034 (removal completed with status): each names the product, its version and the status number, which is 0 on success. Nothing is changed.

    Get-WinEvent -FilterHashtable @{ LogName='Application'; ProviderName='MsiInstaller'; Id=1033,1034 } -MaxEvents 10 |
  Format-List TimeCreated, Id, Message
    PowerShell

What PC Tweaker Uninstaller does with Error 1612 and 1706

Shows the exit code

PC Tweaker Uninstaller removes a Windows Installer program with the command it shows you first in the Removal Brief, msiexec.exe /x {ProductCode} /qn /norestart, after asking Windows for a restore point when the removal needs administrator rights. If Windows Installer cannot find its source, the removal fails and the report shows the exit code msiexec.exe returned. The Uninstaller cannot recreate a missing package and does not force the entry out of the list. Its leftover cleanup never offers anything inside the Windows folder, so it does not touch C:\Windows\Installer.

PC Tweaker Uninstaller: see the exact command before a removal runs

Common questions

Can I delete the C:\Windows\Installer folder to free space?

Microsoft says it should not be deleted: the cache stores files that are required for uninstalling and updating applications, and the damage may not show until you uninstall, repair or update a product.

Are error 1612 and error 1706 the same?

They report the same condition from two places. 1612 is the exit code of msiexec.exe; 1706 is the message a setup shows, "No valid source could be found for product".

Can I copy the missing .msi from another computer?

Microsoft says no: missing files cannot be copied between computers because the files are unique. Use the same version's installer from the publisher instead, or the steps the publisher gives.

Why does this appear only when I uninstall or update?

Because that is when Windows Installer needs the cached package. Microsoft notes that with a compromised cache you may not see problems until you uninstall, repair or update a product.