PowerShell: Enable Script Support
Contributed by Rob Rogers 
Tagged: Windows By default, PowerShell has scripting support disabled. If you try and run a PowerShell script, you will be greeted with an error stating that the execution of scripts is disabled on your system. To enable scripting support so that your scripts will run, read on:
1. Open PowerShell (if you are running PowerShell on Windows Vista, right-click your PowerShell icon and select Run as administrator. If you don’t do this, you will not be able to enable script support).
2. Check the current script execution policy by using the Get-ExecutionPolicy cmdlet. To do this, input Get-ExecutionPolicy and press Enter on your keyboard. PowerShell will return a value of Restricted.
3. To change the script execution policy, use the Set-ExecutionPolicy cmdlet. Input Set-ExecutionPolicy unrestricted and press Enter on your keyboard.
4. To ensure that the script execution policy has been changed, use the Get-ExecutionPolicy cmdlet again. PowerShell should return a value of Unrestricted.
You can now run your PowerShell scripts.
You may also like -
How to run your own PowerShell scripts / cmdlets
Windows 7: Enable Execution of Windows PowerShell ScriptsHow to Find and Reference Environment Variables in Windows PowerShellHow to find and use an alias or function for cmdlets and commands in Window PowerShell
Windows Server 2008: Install Windows PowerShell
PowerShell: Get a Cmdlet or Script's Execution Time
PowerShell 1.0: Getting Help with Get-Help
Firefox: Enable AutoFill in URL (Address) Bar
Steve said on December 23, 2008
This doesn’t seem to work on XP — I fired up the new install of CTP3 and got my start-up script denied. Set-Ex ran but told me it was being overriden; running the PoSh executable as the local Admin let Set-Ex complete without any messages, but did not propagate the effect to my normal ID. I ended up searching the registry for the string “AllSigned” and changing my HKCU execution policy key manually.
Guest said on March 17, 2009
Worked like a charm on XP for me.
JWashington said on May 1, 2009
I have a XP system and this worked great thank you
Jim Balcomb said on February 15, 2010
As a discussion point, `Set-ExecutionPolicy RemoteSigned` will let you run your scripts as well but leaves just a bit more security in place.
zwinnetetten said on June 30, 2010
arseholio
Wasim21k said on January 11, 2011
worked for me on Server 2008 R2 Standard
Glincb said on January 22, 2011
Worked GREAT on win7