PRB: Error 1706 "No Valid Source Could Be Found" When Installing MSI File from Removable Media
This article has been archived. It is offered "as is" and will no longer be updated.
When you install a Windows Installer (MSI) package from removable media, such as a CD-ROM or DVD, and the MSI file doesn't reside on the root folder of the media, the following error message may appear:
Error 1706, "No valid source could be found…"This occurs if the Installer needs to query the source. Browsing to the MSI package does not resolve this error.
The MEDIAPACKAGEPATH property wasn't properly set. MEDIAPACKAGEPATH is a public property that enables you to define where on the removable media the MSI file is located. This can happen if the media that is currently being used and the media that was originally used to install the program have the MSI file at different relative paths.
For example, this error can occur if the original media had the MSI file in a folder called App1, and the current media has the MSI at the root of the media. This error will not occur if the same media is used for the original installation and the current install operation.
Setting the MEDIAPACKAGEPATH property to the correct relative path to the MSI package resolves the issue. The MEDIAPACKAGEPATH property can be set on the command line or in the registry.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
The registry location for setting this property is dependant on the type of installation that was preformed.
Per-user unmanaged installations:
HKCU\Software\Microsoft\Installer\Products\<Compressed ProductCode>\SourceList\MediaPer-user managed installations:
HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Managed\<User SID>\Installer\Products\<Compressed ProductCode>\SourceList\MediaPer-machine installations:
HKLM\Software\Classes\Installer\Products\<Compressed ProductCode>\SourceList\MediaFor all cases, the value is a string named MediaPackage.The data value is the relative path to your application on the media that you want to use for future install operations. For example, if the path to the MSI package on the media is E:\MyPath\My.msi, then use \MyPath\ as the data value.
For setting the property on the command line you would use:
MEDIAPACKAGEPATH="\MyPath\"The path should begin and end with a backslash character (\) and should NOT contain the package name or drive letter.
In version 2.0 of the Windows Installer, the media from which you installed will always work. But if you did not use the original product media for that installation but then later use that product media instead of the media from which you installed, you may receive the error if the MSI file is in different locations on the different media. The resolutions described in this article will resolve this problem as well.
Administrative images moved to removable media can also exhibit this problem if the location of the root of the installation has changed on the new media. The MEDIAPACKAGEPATH property must be set to the new path of the installation location on the media.
This behavior is by design.
For more information on MEDIAPACKAGEPATH see the following MSDN Web page:
Article ID: 299803 - Last Review: 12/06/2015 02:53:49 - Revision: 4.0
Microsoft Windows Installer 2.0
- kbnosurvey kbarchive kbprb KB299803