-
Notifications
You must be signed in to change notification settings - Fork 18
chocholatey packages not found, PATH not set #2
Comments
I have run into the same issue with the git and chocolatey packages. the install happens just fine, but the PATH modification doesn't occur. |
I faced the same issue in the beginning. Make sure you PowerShell instance has execution policy for executing scripts. If Then I uninstalled git and tried again, it worked fine. Probably this happens because Chocolatey downloads a ps script file and fails to execute it silently. |
Howdy. I just turned on watching for this repo. Apologies that I had not previously seen this. |
What @villasv mentioned here. |
@ferventcoder Thanks for watching. In my VM I've replayed it in a Windows 10 Insider Preview 10565 but even with
|
Is this related to chocolatey/choco#1052? There are also two StackOverflow questions where setting the execution policy to RemoteSigned worked:
But it didn't work for me. I created my own Chocolatey package (a "hello world" .NET Core console app, published as self-contained deployment, copied all published files to the When running The app isn't signed, so I tried with execution policy Unrestricted as well, but to no avail. |
I see you left a comment at #5. I will follow up there. |
I played with the latest Windows 10 Build 10162 and tried the "OOBE" of the built-in package manager. I tried installing a command line tool on a fresh Windows installation.
First the nuget provider will be installed.
After repeating the
Install-Package docker
command it installs the Chocolatey package.But the command line tools could not be started as it is not found in PATH.
Here is the output of my shell:
Even after signing out and signing in again the PATH is still the same and the command line tool could not be found.
The environment variable
ChocolateyPath
is set for the current user, but the PATH is not set:I have found the installed package at the usual place:
Is there a way to set PATH for the user as well?
PS: I used this boxcutter/windows PR#25 to create the Windows 10 Vagrant basebox for the tests.
The text was updated successfully, but these errors were encountered: