# Install-Module: The term Install-Module is not recognized as the name of cmdlet, function, script file or operable program

If Install-Module is not recognized at all, the usual cause is that the machine is missing the PowerShellGet tooling that newer Windows PowerShell environments include.

blog

25 Jul 2018 en

![Install-Module: The term Install-Module is not recognized as the name of cmdlet, function, script file or operable program](/wp-content/uploads/2018/07/img_5b582a3465b57.png)

[View images (2)](#pf-content-image-1-0)

I was preparing another environment for **PSWinReporting** and started installing the usual dependent modules when PowerShell stopped immediately with a more basic problem: `Install-Module` itself did not exist on that system.

> Install-Module: The term Install-Module is not recognized as the name of cmdlet, function, script file or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

### 💡 Short description of problem

```powershell
Install-Module PSTeams
Install-Module PSEventViewer
Install-Module PSWinReporting
Install-Module PSWriteColor
Install-Module ImportExcel
Install-Module PSSlack
```

[!\[Install-Module Errors\](/wp-content/uploads/2018/07/img_5b582a3465b57.png)](/wp-content/uploads/2018/07/img_5b582a3465b57.png)

Install-Module Errors It turned out the machine was still on **Windows PowerShell 4.0**. That is the key detail, because `Install-Module` comes from **PowerShellGet**, which is part of the newer management stack most people now take for granted.

## Fix

The cleanest fix on an older Windows PowerShell box is to install **Windows Management Framework 5.1**, reboot, and then try again.

[!\[Windows Management Framework 5.1\](/wp-content/uploads/2018/07/img_5b5829d5a3796.png)](/wp-content/uploads/2018/07/img_5b5829d5a3796.png)

Windows Management Framework 5.1 After reboot, `Install-Module` was available again and the module installs worked as expected.

```powershell
PS C:\Windows\system32> Install-Module PSTeams
PS C:\Windows\system32> Install-Module PSEventViewer
PS C:\Windows\system32> Install-Module PSWinReporting
PS C:\Windows\system32> Install-Module PSWriteColor
PS C:\Windows\system32> Install-Module ImportExcel
PS C:\Windows\system32> Install-Module PSSlack
```

## Why this is better than manual copying

Yes, you can copy modules around manually, but that becomes painful very quickly when you need updates, dependencies, or a reproducible setup on multiple machines.

## Current note

For older **Windows PowerShell** systems, this is still the right mental model: if `Install-Module` is missing entirely, first check the PowerShell version and whether the machine has the newer management framework installed.

For newer environments, the broader direction has shifted toward **PowerShell 7** and the newer package tooling, but on legacy Windows administration boxes **WMF 5.1** is still the common baseline that makes `Install-Module` available.

## Related Projects

Projects that align with this post's tags, categories, and content.

[All projects](/projects/)

Matching projects...

[Back to Blog](/blog)

## Related posts

- [Active Directory – How to track down why and where the user account was locked out](/blog/active-directory-how-to-track-down-why-and-where-the-user-account-was-locked-out/)
- [Mentioning users in notifications using PSTeams PowerShell Module](/blog/mentioning-users-in-notifications-using-psteams-powershell-module/)
- [Submitting blogs to web.archive.org using PowerShell](/blog/submitting-blogs-to-web-archive-org-using-powershell/)

<!-- PowerForge markdown artifact sha256:2B4E5C0A617D677F0CDE52CA593BDDD0AAAD7317D15ECAE7C98ABD25BD478935 -->
