Repository navigation
Move ManagedModule
Moves modules, or specific versions of modules, between the CurrentUser and AllUsers scopes.
Move-ManagedModule -ModuleBase <String[]> -Destination <String> [-Force] [-PassThru]
[-ProgressAction <ActionPreference>] [-WhatIf] [-Confirm] [<CommonParameters>]
Move-ManagedModule [-Name] <String[]> [-Version <String[]>] [-Scope <String[]>] -Destination <String> [-Force]
[-PassThru] [-ProgressAction <ActionPreference>] [-WhatIf] [-Confirm] [<CommonParameters>]
Moves installed module versions to the module folder of another scope. Each version keeps its folder layout, and the location in its install record (PSGetModuleInfo.xml) is updated, so PowerShellGet and PSResourceGet still recognise it.
On Windows, a version stays with its edition's modules: one in a WindowsPowerShell\Modules folder moves to the other WindowsPowerShell\Modules folder (Documents or Program Files), and one in a PowerShell\Modules folder to the other PowerShell\Modules folder. This keeps it where the edition it was installed for looks. For example, from PowerShell 7, a module in Program Files\WindowsPowerShell\Modules (which both editions use) moved to CurrentUser goes to Documents\WindowsPowerShell\Modules. PowerShell 7 doesn't look there by default (only when it's started from Windows PowerShell), so a warning says when the session can't see where a version went. Other versions move to the first PSModulePath entry for the scope.
Each version is copied, so it takes the permissions of the destination folder, and the original is removed only once the copy is complete. If the copy fails, the original is left as it was.
Safety checks:
- Modules that ship with PowerShell or Windows are never moved.
- Versions already installed for the destination scope are skipped.
- Versions that already exist at the destination are not overwritten.
- Loaded modules are skipped unless -Force is used, which unloads them first.
- Moving to or from AllUsers requires an elevated session.
- Moving to CurrentUser a version that a module installed for all users depends on warns that other users will no longer have it.
Move-ManagedModule Pester -Destination AllUsers
Moves every version of Pester installed for the current user to the all users module folder.
Get-ModuleLocation -Scope AllUsers | Move-ManagedModule -Destination CurrentUser -WhatIf
Shows which all-users module versions would be moved to the current user's module folder, without moving anything.
Move-ManagedModule Az.* -Version 14.* -Destination AllUsers -PassThru
Moves the Az 14.x versions to the all users module folder and lists where they are now.
The module name(s) to move. Wildcards are supported. All versions are moved unless -Version is given.
Type: String[]
Parameter Sets: ByName
Aliases:
Required: True
Position: 1
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: TrueOnly move these versions (for example '1.2.0' or '2.0.0-beta1'). Wildcards are supported.
Type: String[]
Parameter Sets: ByName
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: TrueOnly move versions installed in these scopes.
Type: String[]
Parameter Sets: ByName
Aliases:
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThe folder of a specific installed version. Bound automatically when you pipe output from Get-ModuleLocation or Get-ModuleInventory -AllVersions.
Type: String[]
Parameter Sets: ByModuleBase
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: FalseThe scope to move to: CurrentUser or AllUsers.
Type: String
Parameter Sets: (All)
Aliases:
Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseMove modules even if they are loaded, unloading them from the session first.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseOutput the moved versions, at their new locations.
Type: SwitchParameter
Parameter Sets: (All)
Aliases:
Required: False
Position: Named
Default value: False
Accept pipeline input: False
Accept wildcard characters: FalseShows what would happen if the cmdlet runs. The cmdlet is not run.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: wi
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalsePrompts you for confirmation before running the cmdlet.
Type: SwitchParameter
Parameter Sets: (All)
Aliases: cf
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False{{Fill ProgressAction Description}}
Type: ActionPreference
Parameter Sets: (All)
Aliases: proga
Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: FalseThis cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).