IT Error Decoder
Windows Admin

How to Fix The term is not recognized as the name of a cmdlet

Last reviewed

Error message

The term '<n>' is not recognized as the name of a cmdlet, function, script file, or operable program.

Almost every 'not recognized' error has the same fix: install or import the module that provides the cmdlet.

What this error means

PowerShell can't find anything callable with that name. The cmdlet doesn't exist, the module that provides it isn't loaded, or it's not on PATH (for external programs).

Why this happens

Module not installed, module not auto-imported, command name typo, or you're on a Windows PowerShell session that doesn't have the cmdlet (lots of cmdlets are PowerShell 7-only or Core-only).

Quick fix (for end users)

  • Check the spelling.
  • Try installing the relevant module.

Admin / engineer fix

  • Search for the command across installed modules.

    command
    Get-Command *<partial-name>* -ErrorAction SilentlyContinue

  • Find the module that provides a cmdlet (online).

    command
    Find-Command <name> -ErrorAction SilentlyContinue

  • Install and import the module.

    command
    Install-Module <module-name> -Scope CurrentUser
Import-Module <module-name>

  • If running in Windows PowerShell 5.1 but the cmdlet is PowerShell 7+, switch shells.

Step-by-step fix

  1. Verify the spelling matches Microsoft's documentation.

  2. Use Find-Command or Find-Module to locate the right module.

  3. Install and import it.

Affected products

Windows PowerShell 5.1 · PowerShell 7

Common variations of this error

People also see these phrasings of the same problem:

  • CommandNotFoundException
  • is not recognized as a cmdlet, function, or operable program

Still broken? Try these

  • Open a fresh PowerShell window after install — current session may not pick up the module.
  • Some modules require admin to install machine-wide; use -Scope CurrentUser to install for yourself.
  • If the module exists but the cmdlet doesn't appear, you may have a version that's too old.

Related errors

Related searches

  • powershell command not found
  • find-module powershell

Frequently asked questions

How do I know which module a cmdlet belongs to?

Run `Find-Command <name>` for a published cmdlet, or check the 'Module' column of `Get-Command <name>` once installed.

Browse more errors in Windows Admin: Fix Windows administration errors. Access denied, RPC server unavailable, trust relationship failures, Group Policy errors, and network path issues. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.