Removing powershell module using version number

Question

Is there an easy way to pass the version as a parameter to get-module ? I have two versions of Azure Powershell installed:

 C:\WINDOWS\system32> get-module -name azure -listavailable Directory: C:\Program Files\WindowsPowerShell\Modules\... ModuleType Version Name ---------- ------- ---- Manifest 1.0.4 Azure Directory: C:\Program Files (x86)\Microsoft SDKs\Azure\... ModuleType Version Name ---------- ------- ---- Manifest 1.0.2 Azure 

and I want to remove one of them using the command:

 get-module -name azure -version 1.0.2 | remove-module 

Answer 1

Please see: get-help Remove-Module -full

 -FullyQualifiedName [<String[]>] Removes modules with names that are specified in the form of ModuleSpecification objects (described by the Remarks section of Module Specification Constructor (Hashtable) on MSDN). For example, the FullyQualifiedName parameter accepts a module name that is specified in the format @{ModuleName = "modulename"; ModuleVersion = "version_number"} or @{ModuleName = "modulename"; ModuleVersion = "version_number"; Guid = "GUID"}. ModuleName and ModuleVersion are required, but Guid is optional. You cannot specify the FullyQualifiedName parameter in the same command as a Name parameter; the two parameters are mutually exclusive. 

Note:

The FullyQualifiedName parameter accepts the module name specified in the format @ {ModuleName = "modulename"; ModuleVersion = "version_number"}

Based on this, the following follows:

 Remove-Module -FullyQualifiedName @{ModuleName = "Azure"; ModuleVersion = "1.0.2"} 

Improved answer (edit)

More research has been done on this, and there are some quirks when uninstalling with ModuleVersion (which may be string or [version] ).

If you specify ModuleVersion , Remove-Module will remove all relevant modules with this version and more.

To get an explicit match, you must also pass guid .

 Get-Module 'Azure' | where {([string]($_.Version)).StartsWith('1.0.2')} | Remove-Module 

Since this is a lot, I suggest adding a function to my profile to make it easier.

 function Remove-ModuleWithVersion { param ( [Parameter(Mandatory=$true)] [string] $Module, [Parameter(Mandatory=$true)] [string] $VersionToMatch ) Get-Module $Module | where {([string]($_.Version)).StartsWith($VersionToMatch)} | Remove-Module -Verbose } 

and call:

 Remove-ModuleWithVersion 'Azure' '1.0.2' 

Testing and analysis

I could also tell how I tested this to come to my conclusion. I will leave some details to the reader for self-examination ...

Create two modules and export a function from each using different function names to facilitate testing.

D: \ test \ modtest \ v1 \ ModTest.psd1 with version 1.1.0.1
D: \ Test \ modtest \ v1 \ ModTest.psm1

 function Show-Hello1 { "Hello v1.1" } Export-ModuleMember -Function Show-Hello1 

D: \ test \ modtest \ v2 \ ModTest.psd1 with version 1.2.0.2
D: \ Test \ modtest \ v2 \ ModTest.psm1

 function Show-Hello2 { "Hello v1.2" } Export-ModuleMember -Function Show-Hello2 

Create a function to load modules, call the exported functions, show the modules before, delete the module using the specified parameters, show the modules after.

 function Invoke-LoadAndRemove($minor, $useString, $guid = $null) { "`n------`n$($minor), $($useString), '$($guid)'" "`nimport modules..." ipmo D:\test\modtest\v1\ModTest.psd1 -Force #-Verbose ipmo D:\test\modtest\v2\ModTest.psd1 -Force #-Verbose "call exported functions..." Show-Hello1 Show-Hello2 "modules before..." Get-Module *mod* if ($useString) { $ver = "1.$minor.0.$minor" } else { $ver = [version]::new(1, $minor, 0, $minor) } "`nremoving version: $ver, -> $($ver.GetType()), useGuid=$($useGuid)" if ($useGuid) { Remove-Module -FullyQualifiedName @{ModuleName = "ModTest"; ModuleVersion = $ver} -Verbose } else { Remove-Module -FullyQualifiedName @{ModuleName = "ModTest"; ModuleVersion = $ver; Guid = $guid} -Verbose } "modules after..." Get-Module *mod* "done." } 

cause various ways to demonstrate the operation of the Remove-Module ...

 Invoke-LoadAndRemove 2 $true Invoke-LoadAndRemove 1 $true Invoke-LoadAndRemove 2 $false Invoke-LoadAndRemove 1 $false Invoke-LoadAndRemove 1 $false 'b213dea3-4ae3-4fde-a9c6-0ac4a8d1890c' Invoke-LoadAndRemove 2 $true '02fdc44a-2c32-4f7b-8573-b1317b03269a' 

This is the part where I leave it to the reader to further analyze the results in order to verify the conclusions of this article.

However, this was what I noticed that made me explore further:

 modules before... Script 1.2.0.2 ModTest Show-Hello2 Script 1.1.0.1 ModTest Show-Hello1 removing version: 1.2.0.2, -> string, useGuid= VERBOSE: Performing the operation "Remove-Module" on target "ModTest (Path: 'D:\test\modtest\v2\ModTest.psm1')". VERBOSE: Removing the imported "Show-Hello2" function. modules after... Script 1.1.0.1 ModTest Show-Hello1 done. ------ modules before... Script 1.2.0.2 ModTest Show-Hello2 Script 1.1.0.1 ModTest Show-Hello1 removing version: 1.1.0.1, -> string, useGuid= VERBOSE: Performing the operation "Remove-Module" on target "ModTest (Path: 'D:\test\modtest\v2\ModTest.psm1')". VERBOSE: Performing the operation "Remove-Module" on target "ModTest (Path: 'D:\test\modtest\v1\ModTest.psm1')". VERBOSE: Removing the imported "Show-Hello2" function. VERBOSE: Removing the imported "Show-Hello1" function. modules after... done. 

Please note that when removing 1.2.0.2, it works as expected. When you delete 1.1.0.1, both 1.1.0.1 and 1.2.0.2 are deleted!