About this documentation on PowerShell module PackageUpdateInfo

Overview

Mon, 01 Jan 0001 00:00:00 +0000

PackageUpdateInfo helps you keep installed PowerShell modules up to date. It compares local module versions with versions from configured online repositories (for example PSGallery) and reports when newer versions are available.

What does PackageUpdateInfo do?

The module can:

Query locally installed modules.
Discover current online versions.
Compare versions with configurable sensitivity (major, minor, build, revision).
Show rich output including repository, release notes, author, and project links.
Export results for later import and fast startup workflows.

Why use PackageUpdateInfo?

Convenience

Quickly identify outdated modules without manually checking each one.
Export and import update information for offline or delayed review.
Run update checks in background jobs.
Use optional toast notifications on Windows.

Automation

Schedule update checks using your profile, scheduled tasks, or startup routines.
Enforce an update-check interval to reduce unnecessary repository queries.
Keep custom rules per module pattern for update sensitivity.
Reuse previously exported data for low-latency shell startup.

Flexibility

Include or exclude module name patterns.
Define rule scope and precedence with default and custom rules.
Works on Windows, Linux, and macOS.
Supports Windows PowerShell 5.1 and PowerShell 7+.

Prerequisites

Windows PowerShell 5.1 or PowerShell 7+.
PowerShellGet access to your target repository (for example PSGallery).
Optional: BurntToast module for toast notifications on Windows.

Installation

Install for all users (requires administrative rights):

Operational best practices

Mon, 01 Jan 0001 00:00:00 +0000

This page describes recommended operating patterns for PackageUpdateInfo in interactive shells, profiles, and automation.

Start with default behavior

Reset settings before introducing custom tuning, especially on shared systems:

Set-PackageUpdateSetting -Reset

Inspect current configuration and rules:

Get-PackageUpdateSetting
Get-PackageUpdateRule -IncludeDefaultRule

Use update intervals to reduce noise

Get-PackageUpdateInfo respects UpdateCheckInterval. If the last effective check is still within the configured interval, the cmdlet returns early.

Set an interval that matches your environment:

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Use this guide when PackageUpdateInfo does not return expected results, skips checks, or fails to import and export data.

Get actionable diagnostics first

Run with verbose output:

Get-PackageUpdateInfo -Verbose

Validate settings and rules:

Get-PackageUpdateSetting
Get-PackageUpdateRule -IncludeDefaultRule

Check is skipped unexpectedly

Symptom:

You see a warning that update checks are skipped because the check interval is not expired.

Cause:

UpdateCheckInterval and recent LastCheck or LastSuccessfulCheck are preventing a new online check.

Resolution: