I don’t know if anybody else has had this problem, but if this helps anybody the great, hopefully you be spending hours scratching around for a solution like I was
I was going to create a new MVC project using Visual Studio 2012. When the project was initializing, and downloading all the relevant packages, I got this error message.
All I could think of was What the hell.
So fire up PowerShell and run Get-ExecutionPolicy. Reports back RemoteOnly.
So totally scratching around for ideas, could not find anything that I had not already tried. I thought I was never going to get this resolved, when somebody asked did you check the 32bit version of PowerShell.
I already checked PowerShell, what are you talking about? It was then that I realised that I was using a 64bit operating system, and that Visual Studio is a 32bit application. I never realized that there where 32bit and 64 bit versions of PowerShell installed side by side. So I fired up “PowerShell (x86)”, and ran Get-ExecutionPolicy.
Now, instead of getting the RemoteOnly result that I was expecting, the 32bit version of PowerShell is reporting Restricted.
Now I really think What the Hell. Why does 32bit and 64bit versions of PowerShell on the same computer have different execution policies! Who thought up that bright idea.
After executing Set-ExecutionPolicy RemoteOnly on PowerShell (x86). Restart Visual Studio, and try again to create a new MVC project in Visual Studio. Now it works.
I hope this helps out somebody