8

When I install chocolatey, I get error like this :

enter image description here

...

WARNING: It's very likely you will need to close and reopen your shell
  before you can use choco.
...

WARNING: You can safely ignore errors related to missing log files when
  upgrading from a version of Chocolatey less than 0.9.9.
  'Batch file could not be found' is also safe to ignore.
  'The system cannot find the file specified' - also safe.
WARNING: Not setting tab completion: Profile file does not exist at
'C:\Users\Chelsea
\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'.

...

How can I solve the error?

Success Man
  • 291
  • 2
  • 4
  • 7

2 Answers2

9

Here's the solution for the tab completion warning:

  1. Open a PowerShell session and run: notepad $profile This opens the profile file in Notepad.

  2. Copy and paste the following code into Notepad and save the file:

# Chocolatey profile
$ChocolateyProfile = "$env:ChocolateyInstall\helpers\chocolateyProfile.psm1"
if (Test-Path($ChocolateyProfile)) {
  Import-Module "$ChocolateyProfile"
}
  1. Restart PowerShell

Source: https://docs.chocolatey.org/en-us/troubleshooting#why-does-choco-tab-not-work-for-me

ParkerM
  • 103
  • I think you mean chocolateyProfile.ps1 – mbomb007 Feb 23 '21 at 15:28
  • On what chocolatey version are you seeing chocolateyProfile.ps1? On 0.10.15 it’s .psm1. – Tereza Tomcova Feb 25 '21 at 15:12
  • Never mind. I wasn't familiar with PowerShell modules – mbomb007 Feb 25 '21 at 19:54
  • 1
    After doing the above points (thanks!), I then got "execution of scripts is disabled on this system."

    Fixed by following steps in https://stackoverflow.com/questions/4037939/powershell-says-execution-of-scripts-is-disabled-on-this-system:

    Set-ExecutionPolicy -ExecutionPolicy Unrestricted

    – ro͢binmckenzie Mar 21 '22 at 09:05
3

Just ran into this warning myself. It occurs because there is not an existing PowerShell profile for your Windows user.

To create a profile, open a PowerShell session and enter:

if (!(Test-Path -Path $PROFILE)) {
  New-Item -ItemType File -Path $PROFILE -Force
}

I pulled the above code from Microsoft's documentation. The page covers a lot more about profiles if you are interested.