Free tools Windows power users keep installed
One-click scans. No signup required.
If Windows says a command is “not recognized,” first check whether your shell can find it. If the command is found but then fails, troubleshoot the program, script policy, or app launch instead. The right next step depends on whether you’re using Command Prompt, Windows PowerShell, or PowerShell 7—and on the exact error.
Start with the exact command and error
Before changing PATH, reinstalling an app, or adjusting a security setting, record the facts that distinguish a lookup problem from a launch failure:
As an Amazon Associate I earn from qualifying purchases.
- The full command, including its extension and arguments.
- Which shell you used: Command Prompt (
cmd.exe), Windows PowerShell 5.1, or PowerShell 7 (pwsh). - The complete error text and the current directory.
- Whether the command worked before, how the app was installed, and whether the PC is managed by work or school.
“Not recognized as an internal or external command, operable program or batch file” is a Command Prompt lookup error; “the term is not recognized as the name of a cmdlet” is PowerShell’s wording. Both commonly indicate a spelling, installation, or command-search issue, but the shell’s search rules differ. If the shell finds the command and reports a different error, move to the relevant policy or app-launch checks below.
Check whether your shell can find the command
In PowerShell
Replace tool with the command name, then inspect what PowerShell resolves:
#1 Best Overall
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
Get-Command tool -All
$Env:PATH -split ';'Get-Command -All can show aliases, functions, cmdlets, and external programs with that name. PowerShell gives aliases, functions, and cmdlets precedence over external executables, so a same-name alias or function may be what runs. If you expect an executable, inspect the results and use its verified path to distinguish a naming conflict from a missing file. Microsoft documents these lookup rules in about_Command_Precedence.
PowerShell does not run a program in the current directory just because you typed its name. To test a local executable, specify its relative path, for example .tool.exe, or use its verified full path. If that works while tool does not, the issue is likely command lookup or PATH rather than the executable itself.
In Command Prompt
Use these commands to inspect the path visible to the current Command Prompt and look for a matching file:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →path
set PATH
where toolwhere tool checks for matching files in locations searched through the command path. Windows searches the current directory before directories in PATH, as Microsoft’s path command reference explains. Confirm that the spelling is correct, the app is installed, and the directory containing the executable is in the effective path. PATH entries are separated by semicolons.
Do not use path ; as a repair: that syntax clears the command path for that Command Prompt session. Also avoid replacing the entire PATH with one folder; other applications and Windows components may rely on existing entries.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Refresh PATH without damaging it
A terminal inherits its environment from the process that started it. If an installer or Windows setting changed PATH after the terminal opened, that existing shell may still have the old value. Close the affected terminal, open a new one, and repeat the lookup there. set PATH in Command Prompt and Get-ChildItem Env:PATH in PowerShell show the value visible in those shells. Microsoft explains this inherited environment behavior in its environment variables documentation.
If the executable is absent from PATH, use the vendor’s installation guidance or Windows Environment Variables settings to add only the actual, trusted application directory. Do not copy an unverified path or delete other entries to make room.
If wt is not recognized
For Windows Terminal, check that its app execution alias is enabled in Windows Settings and that %LOCALAPPDATA%MicrosoftWindowsApps is included in PATH. Microsoft advises against editing C:Program FilesWindowsApps; use the alias and supported app settings instead. See Microsoft’s Windows Terminal troubleshooting guidance.
If PowerShell finds a script but blocks it
A script-policy error is different from a command-not-found error: PowerShell has located the script, but its effective policy or an organizational control may prevent it from running. Check the policy in the same PowerShell host that produced the error:
Get-ExecutionPolicy
Get-ExecutionPolicy -ListExecution policies govern whether scripts and configuration files can be loaded and whether scripts must be signed. A MachinePolicy or UserPolicy set through Group Policy can override local preferences. Windows PowerShell 5.1 and PowerShell 6 or later store and manage execution policy separately, so results from one host do not necessarily describe the other. Microsoft’s Get-ExecutionPolicy documentation describes the scopes and behavior.
Rank #3
- WINDOWS 11 | STABLE PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 system, this laptop delivers stable performance for everyday computing tasks. It supports web browsing, online learning, document editing, email communication, and basic office work with optimized power efficiency, providing a practical and reliable experience for essential daily use for daily use.
- 15.6” FHD IPS DISPLAY: Features a 15.6-inch Full HD IPS display with narrow bezels, offering wider viewing angles and clearer image details compared to standard panels. The improved screen-to-body ratio enhances visual experience for study, reading, document work, and video playback, making it suitable for both productivity and entertainment use.
- 4GB DDR4 + 128GB eMMC STORAGE: Equipped with 4GB DDR4 memory and 128GB eMMC storage for everyday basics such as browsing, documents, email, and online learning platforms. The built-in TF card slot supports storage expansion up to 1TB, giving you more flexibility for files, photos, videos, and daily documents. TF card not included.
- CONNECTIVITY & PORTS: Includes 1× TF card slot, 2× USB 3.2 Gen1 ports, and 2× full-featured Type-C ports (USB 3.2 Gen1). The Type-C ports support data transfer, charging, and video output, enabling flexible connection with external devices such as monitors, storage, and peripherals for daily work and study use.
- LIGHTWEIGHT DESIGN | ONLINE COMMUNICATION: Designed with a slim, portable profile, this laptop is easy to carry for school, commuting, and travel. A built-in 1MP front camera supports online classes, video meetings, remote communication, and everyday conferencing. The 3300mAh battery works with the low-power system design to support practical daily use, while thermal optimization helps maintain quieter operation during extended tasks.
Do not routinely set execution policy to Bypass. Microsoft says execution policy is “defense in depth,” not a security boundary. If Windows marks a downloaded script as blocked, review and verify its contents before considering the documented Unblock-File approach; do not use it to run code you do not trust. On a managed PC, ask the administrator rather than overriding organization policy. See about_Execution_Policies.
If Windows or your organization blocks execution
Some organizations use App Control policies to restrict which scripts or commands can run, or how PowerShell can be launched. The controls and their capabilities depend on policy configuration and Windows or PowerShell version; their existence should not be assumed on every PC. Microsoft documents examples, including restrictions on command-line, pipeline, interactive, or encoded-command execution, in its App Control for PowerShell guidance.
On a managed device, preserve the complete error and note the app path and PowerShell version, then contact your administrator. Do not try to evade a control by changing invocation methods or encoding commands.
If a packaged app is found but will not launch
A Microsoft Store or inbox app can resolve by name and still fail during activation. Possible causes include per-user app registration, an incomplete or damaged package, permissions, or AppLocker policy. These are app-specific launch problems, not evidence that every command-line failure has the same cause.
Microsoft’s Store app troubleshooting guidance is aimed at support agents and IT professionals. It covers checking app registration and package state and consulting relevant event logs. Keep repairs specific to the affected app; avoid broad registry edits or filesystem permission changes unless an administrator has diagnosed the cause.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose the next test from the failure type
| What you observe | Likely area to investigate | Next check |
|---|---|---|
| Command Prompt says the command is not recognized | Spelling, installation, current directory, or PATH lookup | Run where tool, inspect path, and test a verified full path. |
| PowerShell says the term is not recognized | Command lookup in that PowerShell host | Run Get-Command tool -All; check PATH and whether the command is an alias, function, cmdlet, or executable. |
| A local executable runs by full or relative path, but not by name | PATH or command resolution | Check the directory entry, then open a fresh terminal after any PATH change. |
| PowerShell finds a script but reports a policy error | Execution policy or organization control | Check effective policy in the failing host; ask the administrator if policy is managed. |
| A Store or inbox app resolves but fails during launch | Package registration, package condition, permissions, or policy | Follow app-specific support guidance and consult relevant event logs or IT support. |
If these checks do not isolate the cause, give support the shell and version, exact command and full error, current directory, lookup results, app install method, and whether the device is managed. Those details help distinguish a missing file from a conflicting command, stale environment, policy block, or package activation failure.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
