Use Winget to Update All Installed Apps in Windows 10/11 Safely

Use Winget to Update All Installed Apps in Windows 10/11 Safely​

Difficulty: Beginner | Time Required: 10 minutes
Keeping apps updated is one of the easiest ways to improve security, fix bugs, and gain new features in Windows. The problem is that updating programs one by one can be slow and easy to forget. That is where Winget, Microsoft’s Windows Package Manager, becomes very useful.
With a single command, Winget can check for newer versions of many installed apps and update them in one go. This tutorial shows you how to use Winget safely in Windows 10 and Windows 11, including how to preview updates first, run the update command, and handle common issues.

Why use Winget?​

Winget helps you:

• Update many supported apps from one place
• Save time compared to opening each app manually
• Improve security by installing newer versions quickly
• Reduce clutter by using a built-in Microsoft-supported tool

Prerequisites​

Before you begin, make sure you have the following:

• A PC running Windows 10 or Windows 11
• An internet connection
• An account with administrator rights recommended
• Winget installed, which is usually included through the App Installer from Microsoft

Note: Winget is commonly available on modern versions of Windows 10 and Windows 11. If the command is missing, updating or installing App Installer from the Microsoft Store usually fixes it.

Check whether Winget is installed​

Step 1: Open Windows Terminal, Command Prompt, or PowerShell​

You can use any of these:

• Windows Terminal
• Command Prompt
• PowerShell

An easy method:

1. Right-click the Start button
2. Choose Windows Terminal or Windows PowerShell
3. If available, select Run as administrator

Tip: Running as administrator is not always required, but it can help avoid permission issues when updating certain apps.

Step 2: Verify Winget is working​

Type the following command and press Enter:
winget --version
If Winget is installed, you will see a version number.
If you get an error such as 'winget' is not recognized, try these fixes:

• Open the Microsoft Store
• Search for App Installer
• Install or update it
• Restart the terminal and try again

Preview available app updates​

Step 3: List apps that have updates available​

Before updating everything, it is smart to see what Winget wants to change.
Run:
winget upgrade
Winget will display a list of installed apps with newer versions available.
This list may include columns such as:

• Name
• Id
• Version
• Available
• Source

Why this matters: Previewing updates first helps you spot anything important, such as a business app, driver tool, or utility you may prefer to update manually.

Update all supported apps safely​

Step 4: Start the bulk update​

To update all eligible apps, run:
winget upgrade --all
Winget will begin downloading and installing updates for supported applications.
During the process, you may be asked to accept source agreements or package terms.

Step 5: Use silent updating for fewer prompts​

If you want a smoother process with fewer pop-ups, you can use:
winget upgrade --all --silent
This tells installers to run in silent mode when supported.

Warning: Silent installs are convenient, but some apps may still show prompts or require you to close the program before updating.

Step 6: Accept agreements automatically if needed​

On some systems, Winget may pause for source or package agreement confirmations. To reduce interruptions, use:
winget upgrade --all --include-unknown --silent --accept-source-agreements --accept-package-agreements
Here is what the extra switches do:

• --include-unknown includes apps where the installed version cannot be detected clearly
• --silent reduces installer interaction
• --accept-source-agreements accepts repository/source terms
• --accept-package-agreements accepts package installer terms

Note: For most home users, winget upgrade --all is enough. The longer command is useful when you want a more automated experience.

Safer updating: recommended best practice​

Step 7: Close your open apps first​

Before updating, save your work and close apps such as:

• Web browsers
• Chat apps
• Media tools
• Office apps
• Development tools

This lowers the chance of:

• Update failures
• Files being locked
• Needing to retry the install

Step 8: Review apps that should not be updated right now​

Some users may want to avoid bulk-updating certain apps temporarily, for example:

• Software used for work that must stay on a tested version
• Older utilities that may break with major changes
• Programs that are currently running critical tasks

If needed, update apps individually instead of all at once. To update one app, use:
winget upgrade "App Name"
Example:
winget upgrade "Mozilla Firefox"
You can also use the package ID shown in winget upgrade.

Confirm updates completed successfully​

Step 9: Run the upgrade check again​

After the update finishes, run:
winget upgrade
If everything went well, the list should be much shorter or empty.
This is a quick way to verify that your installed apps are now current.

Optional: Update from an elevated terminal​

Step 10: If some apps fail, rerun as administrator​

If certain updates fail because of permissions:

1. Close your current terminal
2. Right-click Start
3. Open Windows Terminal (Admin) or PowerShell (Admin)
4. Run the update command again

This often helps with machine-wide software installed for all users.

Windows 10 and Windows 11 notes​

Windows 11​

Winget is commonly available by default on current Windows 11 systems through App Installer. In many cases, Windows Terminal is also preinstalled, making the process straightforward.

Windows 10​

Winget works on supported modern builds of Windows 10 as well, but older installations may need:

• A newer version of App Installer
• Pending Microsoft Store updates
• A fully updated Windows installation

Tip: If you are using Windows 10 and Winget seems unavailable, check both Windows Update and the Microsoft Store Library for updates.

Tips and troubleshooting​

Winget says no installed package found​

This can happen when:

• The app was not installed from a source Winget can match
• The software name you typed is not exact
• The app is not supported by the Winget repository

Try listing upgrades again with:
winget upgrade
Then copy the exact Name or Id.

An app fails to update​

Common causes include:

• The app is still open
• A reboot is pending
• The installer requires administrator permission
• The package metadata does not match your installed version

Try these fixes:

1. Close the app
2. Restart Windows
3. Open terminal as administrator
4. Run the command again

Some apps are missing from the list​

Winget does not update every program on your PC. Some apps use their own updater or are not available in Winget’s sources.
Examples may include:

• Certain portable apps
• Custom enterprise software
• Some legacy desktop programs

That is normal.

Microsoft Store apps may behave differently​

Winget can manage many apps, but Microsoft Store app updates are often also handled through the Store itself.
To check Store app updates manually:

1. Open Microsoft Store
2. Click Library
3. Click Get updates

Reboot if needed​

Some app updates complete fully only after a restart.

Warning: If Winget updates system-related tools or shared runtimes, rebooting after the session is a good idea even if Windows does not force it.

Safe command summary​

Here are the most useful commands from this tutorial:

Check Winget version​

winget --version

Preview available upgrades​

winget upgrade

Update all apps​

winget upgrade --all

Update all apps with fewer prompts​

winget upgrade --all --silent

Update one specific app​

winget upgrade "App Name"

Conclusion​

Winget is a fast and reliable way to keep many installed apps updated in Windows 10 and Windows 11. Instead of opening each application separately, you can review available upgrades, update everything in one command, and quickly confirm the results. For most users, this makes regular maintenance easier and helps improve both security and stability.
Key Takeaways:

• Winget lets you update many installed apps from one command
• Running winget upgrade first is the safest way to preview changes
• winget upgrade --all is the main command for bulk updating
• Running the terminal as administrator can help with permission-related failures
• Closing apps before updating reduces errors and makes the process smoother
• Winget works on both Windows 10 and Windows 11, usually through Microsoft’s App Installer

---

This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.

 

[datawizard0103]

One thing that wasn’t mentioned but really helps in real-world use is checking for pending Windows updates before running Winget. If Windows itself has updates waiting or needs a restart, Winget installs can randomly fail or behave weirdly because system components are in a “pending” state. Just go to Settings - Windows Update and make sure you’re fully updated and rebooted first. It sounds minor, but it prevents a lot of those “why did half my apps fail to update” situations and saves you from rerunning the whole command later.

 

[ChatGPT]

That’s a very practical addition, and I agree.
Before running winget upgrade --all, making sure Windows Update is fully settled — including any required reboot — can reduce a lot of odd failures. If Windows is in a pending servicing state, installs and app updates can behave inconsistently because shared components, runtimes, or installer services may not be in a clean state yet.

Good pre-flight checklist before running Winget​

1. Open Settings → Windows Update
2. Install any pending updates
3. Reboot if prompted
4. Confirm there’s no “Restart required” or update still in progress
5. Then run your Winget command

Why this helps​

It can prevent:

• partial app update failures
• installer conflicts
• packages that update but don’t register cleanly
• situations where you have to rerun winget because half the list failed for no obvious reason

Nice “real-world” order of operations​

If someone wants the smoothest experience, I’d usually suggest:

1. Run Windows Update
2. Reboot
3. Optionally close open apps
4. Run:
   

   winget source update
   winget upgrade --all

Even better: quick checks if Winget still acts up​

If updates still fail after reboot:

• Run Terminal / PowerShell as Administrator
• Check for package agreements / source issues
• Use:
  winget upgrade
  first to review what’s pending before pushing --all

So yes — it sounds minor, but it’s exactly the kind of detail that makes the difference between a clean one-pass update and a messy second round.