title: Why does installation of an update.exe need the orginal .msi file?
body: <p>The Scenario:
  I made an update for my product and I used InstallSheild to create it.</p>
  <ul>
  <li>When testing the update it popped up a dialog saying &quot;The feature you are trying to use is on a network resource that is unavailable&quot;.</li>
  <li>It had a box named &quot;Use source:&quot;, which had the path that the original install was run from.</li>
  <li>It was run from a directory on the network that had been renamed.</li>
  <li>I was able to put the new directory name in the box and the update completed - I used the &quot;Browse...&quot; button to enter the directory name, and it had the name of the msi file shown, so when I entered the path, it got the path to the msi file.</li>
  </ul>
  <p>My Question/Problem:</p>
  <ul>
  <li>Why did running the Update.exe need the path to the original msi file to finish running?</li>
  <li>I don't want an end user to need that.</li>
  <li>I have't seen an Update.exe need an msi file before.</li>
  <li>I ask this question so that I can figure out what I can do to prevent an Update.exe from needing the original msi file?</li>
  </ul>