title: msi installation failure (Error 1001. InstallUtilLib.dll: Unknown error. DEBUG: Error 2769: )
body: <p>Eariler, We had our solution built with visual studio 2010 and we had .vdproj file for creating the build and it was working fine perfectly.(setup is installed and works as expected).</p>
  
  <p>But recently, we have upgraded our solution to visual 2017. We did the migration successfully but for build or setup .vdproj was not working fine as we were not able to open .vdproj in visual studio 2017. So, I just googled around &amp; found out the following solutions:</p>
  
  <ol>
  <li>Install visual studio installer plugin in 2017</li>
  <li>User InstalledShield Limited editions</li>
  </ol>
  
  <p>We have gone with first option. We just installed that plugin. Post this, We are able to open that existed visual studio 2010 .vdproj in visual studio 2017. It got migrated without any error. We had custom actions(primary output) in the project, we just re-added them. *.vdproject gets complied successfully and generates .msi file</p>
  
  <p>But while installing it by command line or explicit(double click the .msi). We get following error:</p>
  
  <pre><code>Error 1001. Error 1001. InstallUtilLib.dll: Unknown error.
  DEBUG: Error 2769:  Custom Action _71938623_DFF8_4B88_8552_77D8706A0C48.install did not close 1 MSIHANDLEs.
  The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. 
  The arguments are: _71938623_DFF8_4B88_8552_77D8706A0C48.install, 1, 
  CustomAction _71938623_DFF8_4B88_8552_77D8706A0C48.install returned actual error code 1603 
  (note this may not be 100% accurate if translation happened inside sandbox) 
  </code></pre>
  
  <p>After googling a bit about this, We found couple of suggestion such as adding or removing slash in arguments using command line installation. </p>
  
  <p>But even though we are doing explicit installation(by double clicking the setup file) still we get the above mentioned error. </p>
  
  <p>In case, We remove the custom action from project installation, then msi gets installed successfully. So, we don't know what is the problem with those custom actions.  </p>
  
  <p>We tried of debugging custom action by using Debugger.Launch(). But installer doesn't reach that portion. Prior to that we get above mentioned exception.</p>
  
  <p>Don't know what to do.</p>
  
  <p>We are scratching our head. Any suggestion or help would be really appreciated.</p>
  
  <p>Could it be because of .net framework installed. we have installed .NET 4.6.1 too.</p>