Change the PowerShell MachinePolicy Execution Policy in Windows Server 2012R2

By Microsoft MVP and MCT · Pluralsight Author

Published March 18, 2014 · Updated January 15, 2026 · PowerShell

Background

Last week I wanted to try the new SharePoint 2013 SP1 and, as I never install SharePoint without using PowerShell scripts, I tried using the awesome AutoSPInstaller to install my SharePoint. When Windows Server 201 R2 came out, the twitter sphere said that nothing changed except the Execution Policy was “RemoteSigned”. AutoSPInstaller has a Launch.bat file that makes sure the Main.ps1 launches in “ByPass” mode.

AutoSPInstaller Launch.bat command line starting powershell.exe as administrator with -ExecutionPolicy Bypass

However, the way AutoSPInstaller works is that it includes two other PowerShell files where the functions are stored. When those get included, the ByPass mode is not in effect anymore, and PowerShell goes back to the Machine Policy, which by default is Remote Signed. It’s a good security measure, but we need to get this fixed!

AutoSPInstaller console error saying AutoSPInstallerFunctions.ps1 cannot be loaded because it is not digitally signed

Also for the sake of Google indexing the error for other people, here is the error text:

_File cannot be loaded. The file is not digitally signed. You cannot run this script on the current system.
_

So, I tried to change the execution policy from Powershell with the following command:

 Set-ExecutionPolicy -Scope MachinePolicy -ExecutionPolicy Bypass    

However I got the following error:

PowerShell MachinePolicy Execution Policy

Set-ExecutionPolicy : Cannot set execution policy. Execution policies at the MachinePolicy or UserPolicy scopes mustbe set through Group Policy.

The Fix

You can actually change the MachinePolcy Execution Policy without going through GPO! You need to go in the registry and edit the following key HKLM:\Software\Policies\Microsoft\Windows\PowerShell and change the ExecutionPolicy value to ByPass.

Or you can simply run this PowerShell command:

 Set-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\PowerShell -Name ExecutionPolicy -Value ByPass

Registry Editor showing the ExecutionPolicy value set to Bypass under HKLM Software Policies Microsoft Windows PowerShell

However… the PowerShell command might give you an error that will look something like this:

Cannot find path ‘HKLM:\Software\Policies\Microsoft\Windows\PowerShell’ because it does not exist.

PowerShell error from Set-ItemProperty: cannot find path HKLM:\Software\Policies\Microsoft\Windows\PowerShell because it does not exist

This is because your local group policy to allow scripts to run on the system is probably “not configured” . To configure it, run “gpedit.msc” in the metro start bar.

Windows Server 2012 R2 Start screen search for gpedit.msc showing the gpedit result

Then Navigate to: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell. Change the “Turn on Script Execution” to look something like this:

Turn on Script Execution setting in the Local Group Policy Editor set to Enabled with the Allow all scripts execution policy

Afterwards, the PowerShell command should work and you should be able to change your Execution Policy without any problems!

PowerShell window where Set-ItemProperty succeeds and Get-ExecutionPolicy MachinePolicy returns Bypass

Hope his helps!