Difference between revisions of "Choco installation"
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
</pre> | </pre> | ||
| + | |||
| + | == Related == | ||
| + | * [[Non-Administrative install]] | ||
== See also == | == See also == | ||
Revision as of 14:51, 8 August 2023
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1')) .../... 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
cocho
cocho : The term 'cocho' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ cocho
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (cocho:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Related
See also
Advertising:
