Difference between revisions of "Choco Non-Administrative install"

From wikieduonline
Jump to navigation Jump to search
(Created page with " == Related == * Non-Administrative == See also == * {{Choco}} Category:Choco")
 
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
* https://docs.chocolatey.org/en-us/choco/setup#non-administrative-install
  
 +
<pre>
 +
Set directory for installation - Chocolatey does not lock
 +
>> # down the directory if not the default
 +
>> $InstallDir='C:\ProgramData\chocoportable'
 +
>> $env:ChocolateyInstall="$InstallDir"
 +
>>
 +
>> # If your PowerShell Execution policy is restrictive, you may
 +
>> # not be able to get around that. Try setting your session to
 +
>> # Bypass.
 +
>> Set-ExecutionPolicy Bypass -Scope Process -Force;
 +
>>
 +
>> # All install options - offline, proxy, etc at
 +
>> # https://chocolatey.org/install
 +
>> iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
 +
Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
 +
Getting latest version of the Chocolatey package for download.
 +
Not using proxy.
 +
Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/2.2.2.
 +
Downloading https://community.chocolatey.org/api/v2/package/chocolatey/2.2.2 to C:\Users\USER\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip
 +
Not using proxy.
 +
Extracting C:\Users\USER\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\USER\AppData\Local\Temp\chocolatey\chocoInstall
 +
Installing Chocolatey on the local machine
 +
WARNING: Installation folder is not the default. Not changing permissions. Please ensure your installation is secure.
 +
We are setting up the Chocolatey package repository.
 +
The packages themselves go to 'C:\ProgramData\chocoportable\lib'
 +
  (i.e. C:\ProgramData\chocoportable\lib\yourPackageName).
 +
A shim file for the command line goes to 'C:\ProgramData\chocoportable\bin'
 +
  and points to an executable in 'C:\ProgramData\chocoportable\lib\yourPackageName'.
  
 +
Creating Chocolatey folders if they do not already exist.
 +
 +
chocolatey.nupkg file not installed in lib.
 +
Attempting to locate it from bootstrapper.
 +
WARNING: Setting ChocolateyInstall Path on USER PATH and not SYSTEM Path.
 +
  This is due to either non-administrator install OR the process you are running is not being run as an Administrator.
 +
PATH environment variable does not have C:\ProgramData\chocoportable\bin in it. Adding...
 +
WARNING: Not setting tab completion: Profile file does not exist at 'C:\Users\USER\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'.
 +
WARNING: Unable to run Chocolatey at this time.  It is likely that .Net Framework installation requires a system reboot
 +
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.
 +
You may need to shut down and restart powershell and/or consoles
 +
first prior to using choco.
 +
Ensuring Chocolatey commands are on the path
 +
Ensuring chocolatey.nupkg is in the lib folder
 +
</pre>
 +
 +
 +
Start a new shell and run:
 +
choco
 +
Chocolatey v2.2.2
 +
Please run 'choco -?' or 'choco <command> -?' for help menu.
  
 
== Related ==
 
== Related ==

Latest revision as of 13:15, 4 December 2023

 Set directory for installation - Chocolatey does not lock
>> # down the directory if not the default
>> $InstallDir='C:\ProgramData\chocoportable'
>> $env:ChocolateyInstall="$InstallDir"
>>
>> # If your PowerShell Execution policy is restrictive, you may
>> # not be able to get around that. Try setting your session to
>> # Bypass.
>> Set-ExecutionPolicy Bypass -Scope Process -Force;
>>
>> # All install options - offline, proxy, etc at
>> # https://chocolatey.org/install
>> iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
Getting latest version of the Chocolatey package for download.
Not using proxy.
Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/2.2.2.
Downloading https://community.chocolatey.org/api/v2/package/chocolatey/2.2.2 to C:\Users\USER\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip
Not using proxy.
Extracting C:\Users\USER\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\USER\AppData\Local\Temp\chocolatey\chocoInstall
Installing Chocolatey on the local machine
WARNING: Installation folder is not the default. Not changing permissions. Please ensure your installation is secure.
We are setting up the Chocolatey package repository.
The packages themselves go to 'C:\ProgramData\chocoportable\lib'
  (i.e. C:\ProgramData\chocoportable\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocoportable\bin'
  and points to an executable in 'C:\ProgramData\chocoportable\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

chocolatey.nupkg file not installed in lib.
 Attempting to locate it from bootstrapper.
WARNING: Setting ChocolateyInstall Path on USER PATH and not SYSTEM Path.
  This is due to either non-administrator install OR the process you are running is not being run as an Administrator.
PATH environment variable does not have C:\ProgramData\chocoportable\bin in it. Adding...
WARNING: Not setting tab completion: Profile file does not exist at 'C:\Users\USER\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'.
WARNING: Unable to run Chocolatey at this time.  It is likely that .Net Framework installation requires a system reboot
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.
You may need to shut down and restart powershell and/or consoles
 first prior to using choco.
Ensuring Chocolatey commands are on the path
Ensuring chocolatey.nupkg is in the lib folder


Start a new shell and run:

choco
Chocolatey v2.2.2
Please run 'choco -?' or 'choco <command> -?' for help menu.

Related[edit]

See also[edit]

Advertising: