title: What is the difference in the way I launch powershell console?
body: <p>I work with Sharepoint and I need Sharepoint snap-in present in my console host. When I run powershell from my Windows start menu, I run command</p>
  
  <pre><code>Add-PSSnapin Microsoft.Sharepoint.Powershell
  </code></pre>
  
  <p>snap-in is added ok, and everything works well. </p>
  
  <p>Also, everything is ok, when I run cmd.exe, and type <code>powershell.exe</code> to it and press enter. So I think no shortcut parameters are involved in this problem (but I not 100% sure :) ).</p>
  
  <p>But when I launch powershell through some launcher (I've tested <a href="http://www.launchy.net/" rel="nofollow">Launchy</a> and <a href="http://humanized.com/enso/launcher/" rel="nofollow">Enso</a>) and I try to add the same snap-in, it fails with this error message:</p>
  
  <pre><code>Add-PSSnapin : No snap-ins have been registered for Windows PowerShell version 2.
  At somefile.ps1:7 char:14
  +     Add-PSSnapin &lt;&lt;&lt;&lt;  Microsoft.Sharepoint.Powershell
  + CategoryInfo          : InvalidArgument:(Microsoft.Sharepoint.Powershell:String)     
  [Add-PSSnapin], PSArgumentException
  + FullyQualifiedErrorId : 
  AddPSSnapInRead,Microsoft.PowerShell.Commands.AddPSSnapinCommand
  </code></pre>
  
  <p>What is the difference when I launch powershell with launcher?</p>
  
  <p>I think this is not sharepoint related problem but rather powershell one.</p>
  
  <p>(note: I know about Sharepoint management shell and question is not about it)</p>