Sling Academy
Home/DevOps/Git error: ‘git is not recognized as an internal or external command’

Git error: ‘git is not recognized as an internal or external command’

Last updated: January 28, 2024

Understanding the ‘git not recognized’ Error

Encountering the ‘git is not recognized as an internal or external command’ error can be frustrating when trying to execute Git commands on your system. This error typically occurs when the Git executable is not found in your system’s PATH environment variable. The PATH variable is a list of directories where the operating system looks for executable files to run commands and programs. If Git is not in this list, your system will not know where to find the Git commands.

Possible Causes

  • Git is not installed on your system.
  • The Git executable path is not added to the PATH environment variable.
  • An incorrect path is set in the PATH variable for Git, perhaps due to a faulty installation or an update overriding settings.

Let’s Fix It

Solution 1: Install or Reinstall Git

Installation of Git is the primary step in setting up your system for Git commands.

  1. Download Git from the official Git website.
  2. Run the downloaded installer for Git.
  3. During installation, ensure that you choose the option to add Git to your system PATH.
  4. Complete the installation process and restart your computer.

Notes: Selecting the option to add Git to PATH during installation is crucial. This is usually the default option but should be confirmed for a successful installation. This method is easy and provides a fresh start, especially if the existing Git installation is corrupt.

Solution 2: Manually Add Git to PATH

If Git is already installed but not recognized, this usually means that Git’s path is not included in the PATH environment variable.

  1. Locate the Git executable file on your computer. By default, it’s often installed in C:\Program Files\Git\bin on Windows.
  2. Right-click on ‘My Computer’ or ‘This PC’ on your desktop or in File Explorer, and select ‘Properties’.
  3. Click on the ‘Advanced system settings’ link.
  4. In the System Properties window, click on ‘Environment Variables’.
  5. In the Environment Variables window, under the ‘System variables’ section, find and select the ‘Path’ variable and click ‘Edit’.
  6. Click the ‘New’ button and add the path to the Git executable (e.g., C:\Program Files\Git\bin).
  7. Click ‘OK’ to save the changes and close all the dialog boxes.
  8. Open a new command prompt window and type git --version to check if Git is now recognized.

The following output should confirm Git is recognized:

$ git --version $ git version 2.35.1.windows.2

Notes: This solution allows you to correct the PATH variable without needing to reinstall Git. However, it requires precision in finding the correct Git path and updating the PATH variable without introducing errors.

Solution 3: Use System Repair Software

System repair tools can automatically fix errors with environment variables and paths.

  1. Download and install a system repair tool that can fix path and environmental variables. (Be sure to choose software from a reputable source to avoid further complications.)
  2. Run the tool and select the option to scan and fix environment/path errors.
  3. Follow any additional instructions provided by the software to correct the PATH variable.
  4. Once completed, restart your computer, and try running Git commands again.

Notes: While system repair softwares can be effective at fixing various system issues inclusively environment variables, they might also adjust settings you are unaware of, leading to unexpected changes in your system’s configuration.

Next Article: How to Fetch/Pull All Git Branches

Previous Article: How to tweak Git commit timestamps (author and committer dates)

Series: Git & GitHub Tutorials

DevOps

You May Also Like

  • How to reset Ubuntu to factory settings (4 approaches)
  • Making GET requests with cURL: A practical guide (with examples)
  • Git: What is .DS_Store and should you ignore it?
  • NGINX underscores_in_headers: Explained with examples
  • How to use Jenkins CI with private GitHub repositories
  • Terraform: Understanding State and State Files (with Examples)
  • SHA1, SHA256, and SHA512 in Terraform: A Practical Guide
  • CSRF Protection in Jenkins: An In-depth Guide (with examples)
  • Terraform: How to Merge 2 Maps
  • Terraform: How to extract filename/extension from a path
  • JSON encoding/decoding in Terraform: Explained with examples
  • Sorting Lists in Terraform: A Practical Guide
  • Terraform: How to trigger a Lambda function on resource creation
  • How to use Terraform templates
  • Understanding terraform_remote_state data source: Explained with examples
  • Jenkins Authorization: A Practical Guide (with examples)
  • Solving Jenkins Pipeline NotSerializableException: groovy.json.internal.LazyMap
  • Understanding Artifacts in Jenkins: A Practical Guide (with examples)
  • Using Jenkins with AWS EC2 and S3: A Practical Guide