Error message installing Chocolatey in PowerShell

Question

I'm trying to install Chocolatey to use with PowerShell.

The recommended way to install it is copy and paste the following line.

@powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object net.webclient).DownloadString('http://chocolatey.org/install.ps1'))" && SET PATH=%PATH%;%systemdrive%\chocolatey\bin

But I get the following error:

At line:1 char:13
+ @powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object  ...
+             ~~~~~~~~~~
Unexpected token '-NoProfile' in expression or statement.
At line:1 char:24
+ @powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object  ...
+                        ~~~~~~~~~~~~~~~~
Unexpected token '-ExecutionPolicy' in expression or statement.
At line:1 char:150
+ ... nstall.ps1'))" && SET PATH=%PATH%;%systemdrive%\chocolatey\bin
+                    ~~
The token '&&' is not a valid statement separator in this version.
At line:1 char:1
+ @powershell -NoProfile -ExecutionPolicy unrestricted -Command "iex ((new-object  ...
+ ~~~~~~~~~~~
The splatting operator '@' cannot be used to reference variables in an expression. '@powershell' can be used only as
an argument to a command. To reference variables in an expression use '$powershell'.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

ExecutionPolicy is set as RemoteSigned and I'm running Powershell v3

I tried some apply some bits of the installation code rather than the whole line, but basically, anything after @Powershell is an unexpected token.

Answer 1

In PowerShell v3+ the easiest way is:

1. Open a PowerShell window (run as administrator)

2. Check the version of PowerShell is greater than 3:

    $PSVersionTable.PSVersion
   

3. Enable execution of PowerShell scripts?

   set-executionpolicy remotesigned
   

4. In PowerShell

   iwr https://chocolatey.org/install.ps1 -UseBasicParsing | iex
   

Answer 2

You must start that line from cmd.exe (a "standard" command prompt), not from PowerShell.