How to Install and Start Using Scoop on Windows

Updated

Scoop is a command-line installer for Windows that installs programs into your user folder, so you can set it up without administrator rights in most cases. To get started, open PowerShell, allow local script execution for the current user, run the official install script, then use scoop install to add packages. The steps below assume a standard Windows 10 or 11 machine with PowerShell available and an internet connection.

Before you run the installer

  • PowerShell: Use Windows PowerShell (or PowerShell 7). Scoop is driven entirely from the command line.
  • User-level install: Scoop installs into your user profile by default, which is why admin rights are usually not required. Some packages may still need elevation or extra setup.
  • Script execution policy: PowerShell blocks downloaded scripts by default. You need to relax this for your own user account before running the installer.
  • Network access: The install script and packages are downloaded from the internet.

Install Scoop step by step

1. Open PowerShell

Launch Windows PowerShell from the Start menu. A normal (non-elevated) window is the usual choice for a user-level install.

2. Allow local scripts for your user

Run:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

This permits locally created and signed scripts to run for your account only. Confirm the prompt if one appears.

3. Run the official install script

irm get.scoop.sh | iex

irm downloads the install script and iex runs it. Expected result: Scoop is installed under your user profile and the scoop command becomes available in a new PowerShell session.

If the script refuses to run because the execution policy is still restricted, revisit step 2 and confirm the scope is CurrentUser.

4. Verify the installation

Close and reopen PowerShell, then run:

scoop --version

A version number confirms Scoop is on your PATH. If the command is not recognized, open a fresh terminal window before troubleshooting further.

Common commands once Scoop is running

Task Command What happens
Search for a package scoop search <name> Lists matching packages from known buckets
Install a package scoop install <name> Downloads and installs the app into your user folder
List installed packages scoop list Shows what you have installed
Update Scoop itself scoop update Refreshes Scoop and its bucket metadata
Update installed apps scoop update * Updates all installed packages
Uninstall a package scoop uninstall <name> Removes the app
Check for problems scoop checkup Reports common configuration issues

A typical first session looks like this:

scoop search git
scoop install git
scoop list

Initialization notes and common snags

  • Buckets: Scoop organizes packages into "buckets." The main bucket is set up by the installer; additional buckets are added with scoop bucket add <name>. If a search returns nothing, the package may live in a bucket you have not added yet.
  • PATH changes: Newly installed command-line tools may not appear in a terminal that was already open. Start a new PowerShell window after installing.
  • Execution policy errors: If you see a message about scripts being disabled, re-run the Set-ExecutionPolicy command from step 2 and check that the scope is CurrentUser, not LocalMachine.
  • Admin-required packages: Some apps still need elevation or a system-wide install. Scoop will tell you when a package cannot be installed at user level.
  • Corporate or restricted machines: Group policy can override your execution policy setting. In that case, ask your administrator before changing anything.

Once scoop --version works and you can install a package such as git, your setup is complete and you can manage most command-line tools from PowerShell without leaving the terminal.