Home
News & Insights
- News & Insights Home
- Innovation
- IT Careers & Skills
- Cloud
- Cyber Security
- Future of Work
- All Categories
- Marketing
- HR
- Finance
Community
- Ask question
- Community Home
- Spiceworks Originals
- Cloud
- Collaboration
- Networking
- Water Cooler
- Windows
- All forums
- How-Tos
- Scripts
- Vendors
- Meetups
Reviews
Online Events
Log in Join
Log in Join
Bill Windham
May 09, 2013 1 Minute Read
Spice
Reply (7)
Subscribe
- Share
Bill Windham
Bill Windham14 years in ITA+, Network+
6
Contributions
1
Helpful Posts
Main Areas of Contribution:
- Spiceworks General Support |
- Firewalls |
- General Windows |
- Windows Server
Register. Track Progress. Earn Credits.
Learning has never been so easy!
Sign UpRead these next...
Educative Answers Team
The “Python is not recognized as an internal or external command” error is encountered in the command prompt of Windows. The error is caused when Python’s executable file is not found in an environment variable as a result of the Python command in the Windows command prompt.
RELATED TAGS
python
error
command
terminal
cmd
Copyright ©2022 Educative, Inc. All rights reserved
Summary
A Script Task from a deployment or build plan may fail with the following error:
PowerShell is not recognized as an internal or external command, operable program or batch file
Environment
Bamboo (or its agents) running on Windows OS.
Diagnosis
If your Bamboo version is 6.10.2 or older, please beware of the following bug:
However, if you're running a more recent version of Bamboo, or you also experience this issue when running the PowerShell command directly from Windows' Command Prompt, please proceed with the below.
Cause
This is caused by the user (or system) PATH environment variable not containing the directory where the PowerShell executable resides. It's usually located at C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe, and although the PATH variable contains the C:\Windows\System32 directory, Windows may have trouble locating the executable within its subfolders.
Solution
The solution consists of adding the directory where the PowerShell executable resides to the PATH environment variable.
- Search for "environment variables" in the Windows search bar and open the respective Control Panel item.
- A System Properties window will appear. Click on "Environment Variables" at the bottom.
- Edit the PATH environment variable and add the path to the folder where PowerShell is
located.
- For the changes to be picked up, the agent needs to be restarted. You may also need to restart the machine so all of the other Windows portions pick up the new variable.