14

I'm trying to use oneget w/chocolaty and it doesn't seem to be working at all. The package says it's installed, no warning or notification. It installs the package in the choco directory, but doesn't run the install script and therefore the application is not actually installed. Note this is Windows 10 (Powershell 5).

Get-PackageProvider –Name Chocolatey -ForceBootstrap
Set-PackageSource -Name chocolatey -Trusted 
Install-package filezilla -Verbose -Force -ProviderName chocolatey

yields

powershell result from command

windows directory

ase
  • 13,231
  • 4
  • 34
  • 46
Ashtonian
  • 4,371
  • 2
  • 18
  • 25
  • 6
    I don't know why, but if you don't previously set `Set-ExecutionPolicy RemoteSigned`, it won't work. –  Aug 01 '15 at 08:44
  • @yzT I had my execution policy set at Unrestricted, so that shouldn't matter? normally restrictions outright fail the install. – Ashtonian Aug 03 '15 at 17:06
  • According to this https://technet.microsoft.com/en-us/library/ee176961.aspx, it should work. Also I have noticed that some packages (e.g. Audacious) do not have a installer, but you can find the executable at `C:\Chocolatey\lib\package_name\bin\` –  Aug 03 '15 at 17:44
  • I fixed my issue by running `Set-ExecutionPolicy Unrestricted` in PowerShell while running as an admin. Then `Uninstall-Package` followed by `Install-Package.` – codeConcussion Nov 11 '15 at 02:21

2 Answers2

2

The answer - I wouldn't use the OneGet Chocolatey provider until you hear an official announcement that it is up to date and no longer using the early CTP preview that came out in April 2014 (not a typo).

Until then you should continue to use the official choco client.

ferventcoder
  • 11,952
  • 3
  • 57
  • 90
0

As mentioned in comments, I also tried to fix the problem by running Set-ExecutionPolicy Unrestricted in PowerShell, but I was still having problems with forbidden TLS/SSL security protocols.

And then (as mentioned) I tried through CMD-> %SystemRoot%\System32\WindowsPowerShell\v1.0\PowerShell.exe

and then in PowerShell :

> Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePoin tManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net. WebClient).DownloadString('https://chocolatey.org/install.ps1'))

No more problems with TLS/SSL SecurityProtocol.

Yash Gupta
  • 1,807
  • 15
  • 21
JeeyCi
  • 354
  • 2
  • 9