Installing Python on Windows

Why zip Setup Matters

This guide focuses on installing the zip command on Windows through the GnuWin32 project. Windows does not include the zip command by default, so the command must first be downloaded and installed. After installation, Windows must also be told where to find the executable. That second part is handled by the system PATH environment variable.

From Download to Installed Files

The installation process has a simple sequence. Start at the GnuWin32 project page, download the zip package, and install it. The installation should place the command-line files in the GnuWin32 installation directory. The directory used in this guide is C:\Program Files\GnuWin32\bin. The executable that you will later check for is zip.exe.

1. Open the GnuWin32 project page.
2. Download the zip package.
3. Install the package using the GnuWin32 installation process.
4. Use File Explorer to check the directory C:\Program Files\GnuWin32\bin.
5. Confirm that zip.exe is present in that directory.

How PATH Finds zip

The system PATH is a semicolon-separated list of directories. When you type a command, Windows searches those directories to locate an executable. Installing zip.exe in the GnuWin32 bin directory does not by itself tell Windows to search that directory. Adding C:\Program Files\GnuWin32\bin to the system PATH supplies that missing location.

1. Open the Environment Variables dialog.
2. Add C:\Program Files\GnuWin32\bin to the system PATH environment variable.
3. Apply the change.
4. Close the current command prompt window.
5. Open a new command prompt window so the PATH change takes effect.

Checking the Installation

After installing the package, adding the bin directory to PATH, and opening a new command prompt, verify that Windows recognizes the command. Type zip --version. A successful installation produces output showing the zip version number and other information. This confirms that the command is available through the current command prompt.

zip --version

Successful output shows the zip version number and other information. An unsuccessful check shows an error stating that zip is not recognized as an internal or external command.

Troubleshooting a Missing Command

• Checking zip in the same command prompt that was open before PATH was changed.

  The source instructions state that the command prompt must be closed and reopened for PATH changes to take effect.

  Fix: Open a new command prompt window and run zip --version again.

• Adding an incorrect directory to PATH.

  Windows searches the directories listed in PATH. If the correct GnuWin32 bin directory is not listed, it cannot locate zip.exe through PATH.

  Fix: Open the Environment Variables dialog and verify that the entry is exactly C:\Program Files\GnuWin32\bin.

• Assuming installation completed without checking for zip.exe.

  The installation may not have completed successfully or the files may not have been extracted correctly.

  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 a different terminal application might have its own PATH configuration separate from the standard Command Prompt.

  Fix: Check the PATH configuration for the terminal application you are using.

1. Confirm that zip.exe exists in C:\Program Files\GnuWin32\bin.
2. Check the PATH entry for spelling and the correct directory.
3. Make sure you opened a new command prompt after changing PATH.
4. Check whether your terminal application uses a separate PATH configuration.
5. If the problem continues, reinstall GnuWin32 so that the files are extracted again.

Practice the Verification Sequence

Key Takeaways

1. Windows does not include the zip command by default, so install it from the GnuWin32 project page.
2. The installed executable should be checked in C:\Program Files\GnuWin32\bin.
3. Add C:\Program Files\GnuWin32\bin to the system PATH through the Environment Variables dialog.
4. Close and reopen the command prompt after changing PATH.
5. Run zip --version and look for version information to verify that the command is recognized.

The broader lesson is that operating systems locate command-line tools through configured paths. This same PATH concept is useful when working with Python, Node.js, Git, and other developer tools.