Command Line Basics for Windows

Windows does not include the zip command by default; download and install it from the GnuWin32 project page

Programming

The Missing Command

A command prompt can run programs by command name, but Windows does not include the zip command by default. To use zip on Windows, download and install it from the GnuWin32 project page, then configure Windows so it can locate the installed executable.

How does the GnuWin32 project provide the zip executable, and where does that executable fit within the installed bin directory?

The PATH Lookup

The system PATH is a semicolon-separated list of directories. When you type a command, Windows searches those directories to locate an executable. For the GnuWin32 installation, the directory that must be added is C:\Program Files\GnuWin32\bin. Once that directory is in PATH, Windows has a configured location to search for zip when you type its command name.

How does Windows use the PATH entries to find the zip executable when the user types zip in the command line?

PATH does not describe the zip command itself. It identifies directories that Windows searches for executable programs. The important configuration change is adding the GnuWin32 bin directory to the system PATH.

Installation Sequence

Open the GnuWin32 project page and download the zip command for Windows.
Install the downloaded GnuWin32 tool.
Open the Environment Variables dialog.
Add C:\Program Files\GnuWin32\bin to the system PATH environment variable.
Close the existing command prompt window.
Open a new command prompt window so the PATH changes take effect.
Type zip --version to verify that Windows recognizes the command.

What changes from downloading the GnuWin32 zip tool to adding its bin directory to PATH and making the command available?

A complete installation scenario

A Windows learner needs to use zip from a command prompt.

Obtain the tool: The learner downloads and installs zip from the GnuWin32 project page.

Configure the search location: In the Environment Variables dialog, the learner adds C:\Program Files\GnuWin32\bin to the system PATH.

Refresh the command prompt: The learner closes the current command prompt and opens a new one because PATH changes take effect in a reopened command prompt.

Verify the command: The learner types zip --version in the new command prompt. Successful installation produces output showing the zip version number and other information.

The zip command is available to the new command prompt when the installation completed, the correct GnuWin32 bin directory was added to PATH, and the prompt was reopened.

Verification and Diagnosis

Verification should happen in a new command prompt window. Type zip --version. If the installation was successful, the output shows the zip version number and other information. This check tests whether the command prompt can locate the installed tool through the configured PATH.

What is the difference between Windows failing to recognize zip before PATH configuration and successfully locating it afterward?

Testing in the old command prompt after changing PATH.
The source instructions require closing and reopening the command prompt for PATH changes to take effect.
Fix: Open a new command prompt window and run zip --version again.
Adding an incorrect GnuWin32 directory to PATH.
Windows searches the directories listed in PATH, so an incorrect directory does not identify the installed zip executable.
Fix: Open the Environment Variables dialog and verify the entry exactly.
Assuming installation succeeded without checking for zip.exe.
The GnuWin32 installation may not have completed successfully or all files may not have been extracted.
Fix: Use File Explorer to navigate to C:\Program Files\GnuWin32\bin and confirm that zip.exe is present.
Ignoring the terminal application being used.
The source notes that another terminal application might have its own PATH configuration separate from the standard Command Prompt.
Fix: Check the PATH configuration for the terminal application being used.

Command Lookup in Motion

What happens in sequence when a user types a command, Windows searches PATH, and the installed program runs?

The sequence is simple but important. The user types a command in a command prompt. Windows uses the system PATH as its list of directories to search. If the GnuWin32 bin directory is included and the command prompt has the updated PATH, Windows can locate zip.exe and the verification command can produce version information. If the directory is missing or the prompt has not been reopened, the lookup can fail even though the installation files may be present.

Reopening the command prompt is part of the configuration process, not an optional cleanup step. It gives the new command prompt the PATH state needed for verification.

Practice Check

MEDIUM

You installed zip from GnuWin32 and added C:\Program Files\GnuWin32\bin to PATH. In the command prompt that was already open before the PATH change, zip --version still produces the not-recognized error. What should you do next, and what two additional checks should you make if the error remains?

Hints

Think about which command prompt window contains the updated PATH.
Check whether zip.exe is present in C:\Program Files\GnuWin32\bin.
Review the PATH entry for typos and consider whether the terminal application has a separate PATH configuration.

Your attempt (not saved)

The next step is to close the old command prompt and open a new one, then run zip --version again. If the error remains, confirm that zip.exe is present in the GnuWin32 bin directory, verify that the PATH entry is exactly correct, and check whether the terminal application uses a separate PATH configuration.

Key Takeaways

Windows does not include the zip command by default; obtain it from the GnuWin32 project page.
The system PATH is a semicolon-separated list of directories Windows searches for executables.
Add C:\Program Files\GnuWin32\bin to PATH through the Environment Variables dialog.
Close and reopen the command prompt before testing the updated PATH.
Use zip --version to verify the installation, and inspect zip.exe, the PATH entry, and the terminal configuration if recognition fails.