Repository navigation
Releases
Releases · markwragg/PowerShell-ModuleManager
v0.5.1
[0.5.1] - 2026-11-20
- [feature] In the terminal UI, the output pane can be used with the mouse: right-click hides it (anywhere in the list, or over the pane in the details view), as does clicking
L hide(orL/Esc hide) in its header, and clicking[or]there scrolls it.
v0.5.0
[0.5.0] - 2026-11-20
- [feature] The terminal UI can be used with the mouse. Click a module to move to it, and double-click it for its details (right-click to go back). Click its
[ ]box to select it, a family's arrow to expand or collapse it, a column header to sort by that column, andview:orsort:in the title bar to cycle them. Click a key in the help bar to press it, and y or N to answer a confirmation. The wheel scrolls the list, the details view and the output pane. On Windows it uses the console's own mouse input; elsewhere it needs a terminal that reports the mouse in xterm's SGR format, as most do. Hold Shift to select text in the terminal while modman has the mouse, or useShow-ModuleManager -NoMouseto leave it to the terminal. - [feature] Update checks are several times faster. The PowerShell Gallery, and other NuGet v2 feeds, are now queried directly over their API, 30 modules per request, instead of with
Find-PSResourceorFind-Modulefor each module: about 230 modules take about 2 s, against about 9 s with PSResourceGet and minutes with PowerShellGet. Other repositories, and feeds that can't be reached or that need credentials, are still queried with the package manager.
v0.4.1
[0.4.1] - 2026-11-20
- [fix] With PowerShellGet (such as Windows PowerShell's built-in PowerShellGet 1.0), most update checks failed at random with "A parameter cannot be found that matches parameter name 'Provider'" (or 'MessageResolver'), as the PackageManagement module it uses breaks when used by several lookups at once. PowerShellGet lookups now run one at a time; installing Microsoft.PowerShell.PSResourceGet keeps them parallel and faster.
v0.4.0
[0.4.0] - 2026-11-20
- [feature] On Windows, the terminal UI no longer needs to be started as administrator to change modules installed for all users. Moving modules (M), and updating, uninstalling or removing old versions of
AllUsersmodules, run as administrator when the session isn't: the confirmation says so, Windows asks for permission, and the action runs in a hidden elevated PowerShell process, with its output and progress in the output pane as usual. Choosing No at the Windows prompt changes nothing. - [feature] The terminal UI says it's scanning installed modules while it starts, instead of showing a blank screen, which could take a few seconds with many modules.
- [fix] Moving a module installed by PowerShellGet left its install record pointing at the old folder, with the warning "Access to the path ... PSGetModuleInfo.xml is denied", as PowerShellGet makes that file hidden and Windows won't overwrite hidden files. Its location is now updated, and the file stays hidden.
v0.3.1
[0.3.1] - 2026-11-19
- [fix] On Windows,
Move-ManagedModule(and M in the terminal UI) keeps each module with its edition's modules. Before, a module inProgram Files\WindowsPowerShell\Modules, which both Windows PowerShell and PowerShell 7 use, moved toCurrentUserfrom PowerShell 7 went toDocuments\PowerShell\Modules, where Windows PowerShell doesn't look. It now goes toDocuments\WindowsPowerShell\Modules, with a warning when the session doesn't look there (PowerShell 7 only does by default when it's started from Windows PowerShell). - [fix] In the terminal UI on another computer (
-ComputerName,-Session) or the other edition (-Edition), stopping the repository check or an operation could leave the connection unable to run anything else, or freeze the UI. This happened when the stop came before the command had started on the other end (for example, pressing R straight after starting), as the stop was lost and the command carried on there. Stops now wait for the command to start, and give up after a time limit; if the connection is still busy afterwards, the terminal UI reconnects, and says so.
v0.3.0
[0.3.0] - 2026-11-19
- [feature]
Move-ManagedModulemoves modules, or specific versions, between theCurrentUserandAllUsersscopes, for exampleMove-ManagedModule Pester -Destination AllUsers. Each version is copied (so it takes the destination folder's permissions) and the original removed only once the copy is complete; the install record is updated so PowerShellGet and PSResourceGet still recognise it. It needs an elevated session, and warns when moving toCurrentUsera version that a module installed for all users depends on. - [feature] In the terminal UI, M moves the selected modules and versions (or the current one) to the other scope.
- [feature] The terminal UI's title bar shows the share of modules on their latest version (for example
32% latest) once the repository check is done, when the window is wide enough.
v0.2.1
[0.2.1] - 2026-11-19
- [feature] Modules whose publisher has unlisted them from the repository (usually because they're deprecated, such as
Az.DeploymentManager) are reported asUnlistedinstead ofNotInRepository, byGet-ModuleUpdateand in the terminal UI.
v0.2.0
[0.2.0] - 2026-11-19
- [feature] The terminal UI can manage the modules on another computer:
modman -ComputerName Server01(with optional-Credentialand-ConfigurationName) ormodman -Session $session(any transport, such as SSH). The UI runs locally and everything else runs remotely; ModuleManager is sent for the session, so it doesn't need to be installed there. - [feature] On Windows, the terminal UI can manage the other PowerShell edition's modules:
modman -Edition Desktopfrom PowerShell 7 manages Windows PowerShell 5.1's modules, andmodman -Edition Corefrom Windows PowerShell manages PowerShell 7's. It uses that edition's module paths and package manager, in a hidden process of that edition, without needing remoting set up. - [feature] When the update check fails because PowerShellGet needs the NuGet package provider, the terminal UI offers to install it for the current user (no administrator rights needed) and checks again.
- [fix] Update checks and updates failed with Windows PowerShell's built-in PowerShellGet 1.0 ("A parameter cannot be found that matches parameter name 'AllowPrerelease'"), as it doesn't have the -AllowPrerelease and -AllowClobber parameters ModuleManager passed.
- [fix] Every update check failed, with no reason given, where only Windows PowerShell's built-in PowerShellGet 1.0 is available and the NuGet provider isn't installed (it asks to install the provider, which nothing can answer). The check now says how to fix it, and the terminal UI shows why lookups failed when the check finishes.
v0.1.2
[0.1.2] - 2026-11-19
- [feature] The terminal UI can uninstall loaded modules: when some of the versions being uninstalled or removed are loaded, the confirmation offers f to unload them from the session first. Modules that use .NET assemblies, ModuleManager itself and the package manager are skipped with the reason, as they can't be unloaded safely.
- [feature] Versions selected in the terminal UI's details view stay selected when you go back to the list, so you can select versions of several modules and uninstall them together with X. The title bar shows how many are selected, and the list marks modules with selected versions
[-]. - [feature] The terminal UI's help bar says when U, X and O will act on the selection ("update selected", "uninstall selected", "remove old from selected").
- [fix] Dependencies were missed when several share the same version range (as in the
Azrollup, where about half were missed). This left manyAz.*modules outside theAzfamily in the terminal UI, and could letUninstall-OldModuleVersionandUninstall-ManagedModuleremove a version that a rollup still pins.