# Install-Module : A parameter cannot be found that matches parameter name AllowPrerelease.

If Install-Module does not recognize -AllowPrerelease, the usual cause is an older PowerShellGet version rather than your PowerShell session itself.

blog

22 Aug 2018 en

![Install-Module : A parameter cannot be found that matches parameter name AllowPrerelease.](/wp-content/uploads/2018/08/img_5b7c83c6b9d34.png)

If `Install-Module` tells you that `-AllowPrerelease` does not exist, the problem is usually not your PowerShell prompt itself. In most cases the machine is still using an older **PowerShellGet** module that does not understand prerelease installs.

> Install-Module : A parameter cannot be found that matches parameter name AllowPrerelease.

That is easy to miss on older Windows hosts, because the operating system can ship with a built-in version of **PowerShellGet** that is far behind what is available in **PSGallery**.

## Confirm what version you are actually using

```powershell
$PSVersionTable
Get-Module PowerShellGet -ListAvailable | Sort-Object Version -Descending
Find-module PowershellGet
```

[!\[PowerShell output showing $PSVersionTable, PowerShellGet version 1.0.0.1, and Find-Module reporting PowerShellGet 1.6.7\](/wp-content/uploads/2018/08/img_5b7c83c6b9d34.png)](/wp-content/uploads/2018/08/img_5b7c83c6b9d34.png)

If the version loaded from the box is very old, it may not include the prerelease parameter at all.

## Fix

Install a newer copy of **PowerShellGet** from **PSGallery**:

```powershell
Install-Module PowershellGet -Force
```

If you do not want to install it for all users, add `-Scope CurrentUser`:

```powershell
Install-Module PowershellGet -Force -Scope CurrentUser
```

Then close and reopen the PowerShell session so the newer module version is picked up.

## What if Update-Module fails?

That is also expected on some systems. The inbox version of **PowerShellGet** was not installed with `Install-Module`, so `Update-Module` cannot replace it in place. In that case, install the newer version side-by-side instead. I covered that related error here:

[Update-Module : Module 'PowerShellGet' was not installed by using Install-Module, so it cannot be updated.](/blog/update-module-module-powershellget-was-not-installed-by-using-install-module-so-it-cannot-be-updated/)

## Current note

As of **April 22, 2026**, `Install-Module` is still the familiar **PowerShellGet v2** workflow, but the newer package tooling is **PSResourceGet**. If you are already using that stack, the equivalent prerelease install looks like this:

```powershell
Install-PSResource PSWriteWord -Prerelease
```

## Related Projects

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

[All projects](/projects/)

Matching projects...

[Back to Blog](/blog)

## Related posts

- [Set-PSRepository Installation Policy Trusted – Invalid Class Error](/blog/set-psrepository-installation-policy-trusted-invalid-class-error/)
- [Install-module : The ‘install-module’ command was found in the module ‘PowerShellGet’, but the module could not be loaded.](/blog/install-module-the-install-module-command-was-found-in-the-module-powershellget-but-the-module-could-not-be-loaded/)
- [Update-Module : Module ‘PowershellGet’ was not installed by using Install-Module, so it cannot be updated.](/blog/update-module-module-powershellget-was-not-installed-by-using-install-module-so-it-cannot-be-updated/)

<!-- PowerForge markdown artifact sha256:7F91819C7947FFB16DDD7412077C92EEA2AB022AD189DB7F467B14D072A0438F -->
