These are chat archives for chocolatey/chocolatey-oneget
@doggy8088 - I have seen this as well. Though I was retesting exactly that this morning and got success on both Win 10 and Server 2008 R2 with WMF 5. In the previous testing where I had this happen it was also very clean, newly loaded machines that exhibited the problem - and I saw other posts from people who had the problem. I can't put my finger on why it happens. My only suspicion is that if you answer "y" to prompts when first using the WMF package provider, that it is setup slightly differently than forcing the setup with automation. Here are the commands to force it - would love feedback if a fresh VM reset and running these first, results in a working setup. My test package was ConEMU for both failure and success:
Get-packageprovider –name chocolatey -forcebootstrap
Register-packagesource -name chocolatey -location http://chocolatey.org/api/v2/ -providername Chocolatey -trusted -force
Set-executionpolicy remotesigned -force
Hmmmm - on my success attempts I never let nuget provider get installed - always used "install-package conemu -provider chocolatey" - so it never searches powershellgallery and it's never installed nuget as a provider.