 <p>The correct thing to do is to set an execution policy on your machine (a one-time action), at which point you won't need to bypass it every time, and the Jenkins plugin should "just work". Are you unable to?</p> <p>A reasonable starting setting would be RemoteSigned, which will allow you to execute local scripts fine but would still disallow scripts downloaded from the internet.</p> <p>From an elevated PowerShell prompt, you would run:</p> <pre><code>Set-ExecutionPolicy RemoteSigned </code></pre> <p>See also: <a href="http://technet.microsoft.com/library/hh849812.aspx" rel="nofollow">http://technet.microsoft.com/library/hh849812.aspx</a></p> <p>UPDATE: excerpt from Help on applying policy and how it's supposed to behave:</p> <blockquote> <p>If you set the execution policy for the local computer (the default) or the current user, the change is saved in the registry and remains effective until you change it again.</p> </blockquote> <p>Of course, if your machine is on a Domain, then Group Policy could revert this.</p>