<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Execution Policy and Vista</title><link>http://blogs.msdn.com/powershell/archive/2007/02/15/execution-policy-and-vista.aspx</link><description>Some 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&amp;gt; Set-ExecutionPolicy unrestricted Set-ExecutionPolicy : Access to the registry key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell'</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Execution Policy and Vista</title><link>http://blogs.msdn.com/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#1685969</link><pubDate>Fri, 16 Feb 2007 01:26:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1685969</guid><dc:creator>Heath Stewart</dc:creator><description>&lt;p&gt;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.&lt;/p&gt;</description></item><item><title>&amp;#8220;Captain Literal&amp;#8221;.NET &amp;raquo; PowerShell Basics ??? Running Scripts</title><link>http://blogs.msdn.com/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#1686113</link><pubDate>Fri, 16 Feb 2007 02:36:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1686113</guid><dc:creator>“Captain Literal”.NET » PowerShell Basics ??? Running Scripts</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.captainliteral.net/2007/01/29/powershell-basics-%e2%80%93-running-scripts/"&gt;http://www.captainliteral.net/2007/01/29/powershell-basics-%e2%80%93-running-scripts/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Interesting Finds: February 18, 2007</title><link>http://blogs.msdn.com/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#1705367</link><pubDate>Sun, 18 Feb 2007 18:33:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1705367</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>re: Execution Policy and Vista</title><link>http://blogs.msdn.com/powershell/archive/2007/02/15/execution-policy-and-vista.aspx#9923027</link><pubDate>Mon, 16 Nov 2009 17:14:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9923027</guid><dc:creator>Frustated Newbe</dc:creator><description>&lt;p&gt;I keep getting powershell error after error after error. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;From a FRESH new install of Vista64 (with no security changes yet), how do I write a simple runmyscript.cmd that will run a&lt;/p&gt;
&lt;p&gt;D:\Users\first lastname\Documents\myscript.ps1 &lt;/p&gt;
&lt;p&gt;powerscript file bypassing all vista 64 bit securities, and powershell securities and .net signing security, and all other securities? &lt;/p&gt;</description></item></channel></rss>