Before You Start
The examples below use PowerShell. Run Chocolatey installation and machine-wide package changes from an administrator shell. Install Scoop from a normal, non-administrator shell. WinGet may request elevation when an application’s installer requires it.
Use one package manager to maintain each application so that upgrades and uninstall operations remain predictable. The package names below are examples; check the package details before installing.
Chocolatey
Install Chocolatey
Open PowerShell as administrator and check the execution policy:
Get-ExecutionPolicy -List
$PSVersionTable.PSVersion
Run the official installation command. The policy override applies only to the current process.
Set-ExecutionPolicy Bypass -Scope Process -Force
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
Check the installation and update Chocolatey itself:
choco --version
$env:ChocolateyInstall
choco upgrade chocolatey
Manage Packages
Search for a package and inspect its details:
choco search git
choco info git
Install, update, or remove it as needed:
choco install git
choco upgrade git
choco uninstall git
List installed packages and check for updates:
choco list
choco outdated
In Chocolatey CLI 2 and later, choco list lists installed packages. The old -l / --local-only options are no longer needed or supported. Use choco search to query a repository. See the Chocolatey 2 upgrade notes.
Update all Chocolatey-managed packages only after reviewing the outdated list:
choco upgrade all
Open a new terminal after installation if a command is not found. In a shell where Chocolatey’s helper is loaded, refreshenv refreshes environment variables without reopening the terminal.
Configure Features
List features and their current state:
choco feature list
For a specific command, add -y when you intend to accept its confirmation prompts:
choco install git 7zip -y
To enable automatic confirmation for future commands, or restore prompting:
choco feature enable --name=allowGlobalConfirmation
choco feature disable --name=allowGlobalConfirmation
The following features make Chocolatey stop when it detects a pending or requested reboot; they do not disable reboot detection:
choco feature enable --name=usePackageExitCodes
choco feature enable --name=exitOnRebootDetected
See the feature reference and reboot handling options.
Installation Locations
Chocolatey normally stores its own files in C:\ProgramData\chocolatey. Applications can still install into C:\Program Files, C:\Program Files (x86), or the user’s AppData directory, depending on the package and installer.
ChocolateyInstall selects Chocolatey’s own location before installation. Changing it afterward does not move installed files. ChocolateyToolsLocation applies to packages that use that variable; it does not relocate every application’s installation directory.
Non-administrator installation is an advanced option with limited package support. Follow the non-administrative installation instructions instead of assuming every package supports it.
Sources and Proxy
List configured repositories:
choco source list
For a repository you administer, replace the example URL before adding it:
choco source add --name=MyCustomSource --source=https://example.com/packages/
choco source remove --name=MyCustomSource
Use an HTTP proxy for an individual command:
choco outdated --proxy=http://127.0.0.1:7890
Export and Restore Packages
Save the installed package list in a reinstallable configuration file:
choco export --output-file-path=packages.config
Review the file before using it on another machine:
choco install packages.config
See the export reference. The file records packages, not application settings or user data.
Chocolatey GUI
Install the graphical interface from an administrator shell:
choco install chocolateygui
Open Chocolatey GUI from the Start menu. See the GUI documentation.
WinGet
Check Availability
WinGet is distributed with App Installer. If the command is missing, install or update App Installer through the Microsoft Store, then open a new terminal.
winget --version
winget --info
winget --help
Manage Packages
Search first, then use the exact package identifier to avoid ambiguous matches:
winget search git
winget show --id Git.Git --exact --source winget
winget install --id Git.Git --exact --source winget
List installed applications and available updates:
winget list
winget upgrade
Update or remove the selected application:
winget upgrade --id Git.Git --exact --source winget
winget uninstall --id Git.Git --exact
To upgrade all eligible applications after reviewing the list:
winget upgrade --all
Sources and Settings
Display sources and refresh their metadata:
winget source list
winget source update
Open the settings file with the correctly spelled command:
winget settings
For example, this JSON changes the progress-bar style:
{
"$schema": "https://aka.ms/winget-settings.schema.json",
"visual": {
"progressBar": "accent"
}
}
Merge the settings into the existing file if it already contains custom values. Package listing, upgrading, and uninstalling are standard commands and do not need the old experimental switches. See the settings reference.
Export and Restore Packages
Export applications that WinGet can match to its configured sources:
winget export --output winget-packages.json
Review the file, then install its packages on the target machine:
winget import --import-file winget-packages.json
Unmatched applications produce warnings and need separate handling. Export does not back up application settings or user data. See the export and import references.
Scoop
Install Scoop
Open a non-administrator PowerShell window. The normal installation places Scoop in $HOME\scoop.
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Invoke-RestMethod -Uri https://get.scoop.sh -OutFile install-scoop.ps1
Review the downloaded script, then run it:
.\install-scoop.ps1
scoop --version
scoop checkup
The execution policy change persists for the current user. Follow organizational policy if it prevents the change.
Choose Custom Installation Locations
As an alternative to the default installation, pass absolute paths when running the installer:
.\install-scoop.ps1 -ScoopDir 'D:\Applications\Scoop' -ScoopGlobalDir 'F:\GlobalScoopApps'
Choose existing drives appropriate for your machine. These parameters configure the installation; they do not move an existing Scoop setup. Administrator installation requires an explicit -RunAsAdmin option and is separate from the normal per-user installation. See the installer documentation.
Manage Packages
Search, inspect, and install a package:
scoop search git
scoop info git
scoop install git
Update Scoop and its bucket metadata, then check installed applications:
scoop update
scoop list
scoop status
Update one application or all installed applications:
scoop update git
scoop update *
Hold an application to exclude it from updates, or release the hold:
scoop hold git
scoop unhold git
Remove the application when no longer needed:
scoop uninstall git
Use scoop help or scoop help update for command details. See the command reference.
Manage Buckets
Buckets contain package manifests. List known and configured buckets:
scoop bucket known
scoop bucket list
Install Git before adding the extras bucket:
scoop install git
scoop bucket add extras
Removing a bucket does not uninstall its applications:
scoop bucket rm extras
Configure a Proxy
Set an explicit proxy, or restore the default proxy behavior:
scoop config proxy 127.0.0.1:7890
scoop config rm proxy
See the proxy documentation.
Enable Multi-Connection Downloads
Install aria2 and enable its integration:
scoop install aria2
scoop config aria2-enabled true
Keep certificate validation enabled. The original --check-certificate=false setting is unnecessary for normal downloads. See Scoop’s aria2 documentation.