Microsoft’s Windows Package Manager, better known as Winget, now lets you update virtually any compatible application on your PC with a single command. The feature, spotlighted by Neowin on July 15, 2026, isn’t new—Winget has been part of App Installer on Windows 10, 11, and Windows Server 2025 for years—but for many users, the simplicity of typing winget upgrade --all remains a well-kept secret. In an era where keeping software current is a cornerstone of security and performance, this built-in tool eliminates the drudgery of chasing down updaters across a dozen different vendors.
What actually changed: One command to rule them all
Winget itself is a command-line utility that Microsoft ships with modern Windows versions. It works like apt on Linux or Homebrew on macOS, letting you install, list, and upgrade software from a centralized repository of package manifests. The repository, maintained by Microsoft with community contributions, includes thousands of popular desktop applications—browsers, media players, development tools, utilities—and even integrates with the Microsoft Store as a source.
The star command is disarmingly simple:
winget upgrade --all
When you run this from PowerShell or Command Prompt, Winget scans every application it can see on your system, checks all configured sources (the default community repository and the Store), and, where a newer version exists, downloads and installs it—silently, in sequence, without a single Next button. You’ll see a terminal output that scrolls through package names, version numbers, and progress bars, much like a Linux distribution upgrade.
For those who prefer to review before committing, winget upgrade without any flags produces a neat table of all available updates. It shows the installed version, the latest version, and the package source. This is the sensible first step, especially on older machines that have accumulated software over the years. You can then update just one app using its package ID: winget upgrade --id Microsoft.PowerToys, for instance. But the real time-saver is the blanket --all.
Winget lists everything it recognizes with winget list. To see only pending updates, add the --upgrade-available switch. This gives you a focused inventory before you pull the trigger.
What it means for you: A practical breakdown by audience
For everyday Windows users
If you’re a home user running Windows 10 or 11, Winget can radically simplify your routine. Instead of opening Steam, Adobe Creative Cloud, your browser’s built-in updater, and a half-dozen system tray icons, you fire up a terminal and run one command. It’s particularly handy for people who don’t have the time or patience to micromanage third-party updaters. And because Winget uses authentic installers from the original publishers (it pulls from the official download URLs), you’re not trusting a random update service.
Still, not every app is covered. Microsoft’s repository holds thousands of packages, but some niche tools, older abandonware, or software that uses a proprietary update mechanism may not appear. The key takeaway: Winget handles the heavy lifting for the majority of mainstream apps, letting you focus manual efforts on the few outliers.
For power users and enthusiasts
Power users who regularly tinker with scripts and terminal commands can fold Winget into their maintenance routines. Create a simple batch file or PowerShell script that runs winget upgrade --all and call it from a shortcut. Schedule it as a daily task. But here’s the catch: to run unattended, you must add flags to accept source and package agreements silently:
winget upgrade --all --accept-source-agreements --accept-package-agreements
These flags bypass the prompts that ask you to agree to terms from third-party sources. That’s convenient, but it also means you’re accepting legal terms without review. For personal devices, many users consider that an acceptable trade-off. However, be mindful that some installers still require a reboot, user interaction (like closing a running application), or are installed in the user context. Simply scheduling the command to run as administrator doesn’t guarantee a fully hands-off experience. You may still find the odd app that demands a manual click. Testing on your specific mix of software is essential.
For IT professionals and admins
Winget is not an enterprise endpoint management tool, but it can be a useful complement. For small businesses without a formal deployment solution, it fills the gap. For larger environments managed by Microsoft Intune, Configuration Manager, or a third-party platform, Winget’s local command might conflict with centralized policies. Admins should test it on a representative set of devices before encouraging its use, especially because proxy settings, network restrictions, and security software can interfere.
One powerful use case: quickly patching a fleet of development or test machines that aren’t tightly locked down. A script pushed through Remote PowerShell could update all common developer tools (VS Code, Git, Python, Node.js, etc.) in one pass. Just remember that Winget runs in the user’s context; you’ll need to ensure the right user session is active, networking is available, and the App Installer component is up to date. Microsoft documents Winget as part of the App Installer package, so on some systems you may need to update that from the Store first.
How we got here: Winget’s journey from afterthought to everyday essential
Winget debuted in May 2020 as a command-line tool for installing applications on Windows. At the time, Windows was the odd one out without a native package manager, and the community had long relied on third-party solutions like Chocolatey or Ninite. Microsoft’s entry was initially basic, but it evolved quickly. By 2021, Winget 1.0 shipped with support for installing, searching, and listing packages. The upgrade command followed shortly after, and the --all flag became the natural climax of that evolution.
Under the hood, Winget uses YAML-based manifest files stored in a public GitHub repository, microsoft/winget-pkgs. Anyone can contribute a manifest for an application, and Microsoft curates the submissions to maintain quality. When an application publisher releases a new version, a community member typically submits the updated manifest within days. Winget then reads these manifests, downloads the installer directly from the publisher’s server, verifies the hash, and runs the installation with the standard silent switches.
This architecture means Winget is not a traditional auto-updater; it doesn’t monitor for updates in the background. It is an on-demand tool, like running apt upgrade manually. But that design choice also gives users full control over when and how updates happen—a plus for those who dread forced restarts and surprise version jumps.
Microsoft has steadily expanded Winget’s reach. Although it’s a command-line tool, the company also started integrating it with the Microsoft Store, allowing Store apps to be managed through Winget and vice versa. On Windows 11, you might even see Winget in action behind the scenes when the Store updates certain apps.
The recent Neowin coverage doesn’t announce a new feature, but it underscores a growing recognition: everyday Windows users are increasingly comfortable with terminals, and Winget’s simplicity deserves attention beyond developer circles.
What to do now: A step-by-step guide to start using Winget upgrades
First, verify Winget is on your system. Open PowerShell or Command Prompt and type:
winget --version
If you get an error, you need to install or update the App Installer from the Microsoft Store (search for “App Installer” and hit update). On Windows 10, you might need to ensure you’re on a recent build; version 1809 or later should work.
Next, see what Winget can find:
winget list
This prints every application Winget knows about, including those installed outside Winget. Don’t be surprised if the list is long—it often detects hundreds of entries from the registry.
Now check for upgrades:
winget upgrade
This shows the pending updates in a table. Review the list. Are there any apps you want to skip? If so, run the --all command and exclude them by not using the all flag, or update them individually later.
To apply all updates:
winget upgrade --all
You’ll be prompted to accept any source agreements. If you’re comfortable, use the flags to accept automatically. For a completely silent one-liner:
winget upgrade --all --accept-source-agreements --accept-package-agreements
Remember, this still may pop up a few windows for installers that don’t have a true silent mode. Also, some apps have “unknown” versions—these are skipped unless you add --include-unknown. Microsoft advises caution: enabling that flag may result in unnecessary or unstable upgrades.
If you use a machine for critical work, schedule this before a break or at the end of the day in case a reboot is needed. It’s also prudent to close any running applications that might lock files during installation.
Winget works across Windows 10 and 11, including Home and Pro editions, and Windows Server 2025. For older servers, you might need to manually install App Installer.
Outlook: The quiet evolution of Windows package management
Microsoft continues to invest in Winget, adding new commands and refinement with each Windows feature update. Recently, the team introduced support for portable apps, enterprise policies via Group Policy, and better integration with Windows Update for Business. While Winget may never entirely replace dedicated update mechanisms for specialized software, its growing repository and seamless handling of common applications make it an increasingly indispensable part of the Windows toolbox.
The broader shift is clear: as Windows embraces more open-source and developer-oriented tooling, the line between Linux-style package management and consumer-friendly auto-updaters is blurring. For users willing to spend two minutes learning a command, the payoff is a cleaner, safer, and more up-to-date system—without the noise of advertisement-laden updater wizards.
So, open a terminal and run winget upgrade. You might be surprised by how many updates have been waiting for you.