UpdateEverything

1.3.0

Updates a Windows machine through every package manager and update channel it can find, running each as an isolated step so one failure does not stop the rest. Covers winget, the Microsoft Store, Windows Update, Microsoft 365 Apps, Defender, PowerShell modules, npm, pipx, uv, Chocolatey, Scoop, rustup, .NET tools and more. Can register itself as a scheduled task with
Updates a Windows machine through every package manager and update channel it can find, running each as an isolated step so one failure does not stop the rest. Covers winget, the Microsoft Store, Windows Update, Microsoft 365 Apps, Defender, PowerShell modules, npm, pipx, uv, Chocolatey, Scoop, rustup, .NET tools and more. Can register itself as a scheduled task with toast notifications.
Show more

Minimum PowerShell version

5.1

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name UpdateEverything -RequiredVersion 1.3.0

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name UpdateEverything -Version 1.3.0

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

Copyright

(c) 2026 Brian Kronberg. Released under the MIT License.

Package Details

Author(s)

  • Brian Kronberg

Tags

Windows Update Maintenance winget WindowsUpdate Chocolatey Scoop ScheduledTask

Functions

Update-Everything Initialize-UpdateEverything Register-UpdateEverythingTask Unregister-UpdateEverythingTask Get-UpdateEverythingTask Test-PendingReboot

PSEditions

Desktop Core

Dependencies

This module has no dependencies.

Release Notes

# 1.3.0

One fix, and it matters on managed machines: UpdateEverything refused to elevate
on any machine using a privilege-management broker.

## Elevation is attempted rather than refused

Test-ElevationCapability treated "not a member of the local Administrators
group" as proof that Windows would not grant elevation. That is false wherever a
privilege-management broker is in use -- BeyondTrust, CyberArk EPM, Admin By
Request -- because the account is deliberately not in the group and elevates
anyway, often per application.

On such a machine 1.2.0 is unusable: it refuses before raising a prompt, and
tells the user something untrue about their computer.

Group membership is now a caution rather than a refusal, warned about before the
attempt. The two genuine certainties still refuse, because neither depends on
who is asking: UAC switched off, and a packaged PowerShell with no MSI build
beside it.

## A failed elevation says more

Get-ElevationPolicyNote names a running privilege broker. Those grant or deny
elevation per application and leave nothing in the registry, so in 1.2.0 a
refusal on such a machine came with no explanation at all.

## Verified

The self-elevation handoff is tested end to end for the first time, by a harness
in tests/Elevation that runs on a real machine with UAC on and asks for one
click. Development machines and CI runners are already administrators, and
Windows Sandbox ships with UAC off, so nothing before this could reach the code
that once shipped unable to parse.

FileList

Version History

Version Downloads Last updated
1.9.0 7 9/3/2026
1.8.0 8 9/3/2026
1.7.3 7 9/3/2026
1.7.2 6 9/3/2026
1.7.1 7 9/3/2026
1.7.0 14 9/2/2026
1.6.0 5 9/2/2026
1.5.0 8 9/2/2026
1.4.0 8 9/1/2026
1.3.0 (current version) 8 9/1/2026
1.2.0 7 9/1/2026
1.1.0 6 9/1/2026
1.0.0 4 8/31/2026
Show less