All notes


Some important installation logs:

Downloading to C:\Users\me\AppData\Local\Temp\

Creating ChocolateyInstall as an environment variable (targeting 'Machine')
  Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'

Restricting write permissions to Administrators

We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocolatey\lib'
  (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
  and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.

PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...

Chocolatey (choco.exe) is now ready.
You can call choco from anywhere, command line or powershell by typing choco.

Run choco /? for a list of functions.

Ensuring chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder

@powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString(''))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"

choco /?