http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspxSome of you may be getting an error when trying to set the execution policy on a new install of Windows PowerShell in Vista: PS C:\Users\leonard&gt; Set-ExecutionPolicy unrestricted Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINEen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#10338805Sun, 12 Aug 2012 06:24:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:10338805Ali<p>This is what I was looking for..keep good work :-)</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10338805" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#10140545Mon, 14 Mar 2011 04:42:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:10140545Kyle<p>If it doesn&#39;t work for you to &quot;Run as Administrator&quot; (mine didn&#39;t), you can add the permission directly via the windows registry.</p> <p>See <a rel="nofollow" target="_new" href="http://kyleclegg.com/powershell/">kyleclegg.com/powershell</a></p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10140545" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#9923027Mon, 16 Nov 2009 17:14:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:9923027Frustated Newbe<p>I keep getting powershell error after error after error. &nbsp;</p> <p>From a FRESH new install of Vista64 (with no security changes yet), how do I write a simple runmyscript.cmd that will run a</p> <p>D:\Users\first lastname\Documents\myscript.ps1 </p> <p>powerscript file bypassing all vista 64 bit securities, and powershell securities and .net signing security, and all other securities? </p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9923027" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#1705367Sun, 18 Feb 2007 18:33:09 GMT91d46819-8472-40ad-a661-2c78acb4018c:1705367Jason Haley<img src="http://blogs.msdn.com/aggbug.aspx?PostID=1705367" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#1686113Fri, 16 Feb 2007 02:36:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:1686113“Captain Literal”.NET » PowerShell Basics ??? Running Scripts<p>PingBack from <a rel="nofollow" target="_new" href="http://www.captainliteral.net/2007/01/29/powershell-basics-%e2%80%93-running-scripts/">http://www.captainliteral.net/2007/01/29/powershell-basics-%e2%80%93-running-scripts/</a></p> <img src="http://blogs.msdn.com/aggbug.aspx?PostID=1686113" width="1" height="1">http://blogs.msdn.com/b/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#1685969Fri, 16 Feb 2007 01:26:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:1685969Heath Stewart<p>This also seems true of installing snap-ins. You must run in an elevated PowerShell host to install snap-ins; rather, the installation process has to be elevated no matter how you do it.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1685969" width="1" height="1">