Update Micorosoft Store and Store Apps with command line?

Question

Update Micorosoft Store and Store Apps with command line?

~OSD~ 2,201

Hi

To update Microsoft Store and Store Apps, I navigate to the Store and select "Get Updates", like above screenshot.

Question: Is there any possibility to achieve the same with Command Line /Power Shell or DISM?

5 answers

Your answer

Answer 1

S.Sengupta 23,091 MVP

Open Command Prompt or, PowerShell as Admin and type this command to list all the apps with updates on Windows 11 and press Enter:

winget upgrade

Ref: upgrade command (winget)

~OSD~ 2,201 Reputation points

2022-09-06T12:26:25.067+00:00
Thanks for reply and suggesting Winget Upgrade.
With Winget, I have two issues (1) not installed by default on Windows 10 (2) needs to send device location to MS in order to perform the upgrade, see below: ... (any other alternative? where device location /privacy is not shared with MS)?

C:\>winget upgrade The `msstore` source requires that you view the following agreements before using. Terms of Transaction: https://aka.ms/microsoft-store-terms-of-transaction The source requires the current machine's 2-letter geographic region to be sent to the backend service to function properly (ex. "US").
Mark McLaughlin 1 Reputation point

2022-11-26T19:01:41.257+00:00

I ran "winget upgrade" in PowerShell ISE version 5.1 and I wasn't able to enter Y / yes for the terms agreement.

When I ran in the Visual Studio Code PowerShell terminal I was able to enter "Y" and proceed
Lowell Williamson 0 Reputation points

2023-02-14T20:49:12.17+00:00

When I run winget upgrade -i --all where do you put the Y?
Christian Føsund 1 Reputation point

2023-06-14T09:52:21.6366667+00:00
@Lowell Williamson
Ref: upgrade command (winget)

winget upgrade -i --all --accept-source-agreements --accept-package-agreements
katsutoshi hayashida 0 Reputation points

2023-06-30T06:32:45.1966667+00:00

Winget is one of app in the store. Winget is not available on a fresh Windows instance. To use winget, we need to update store apps from command line. We don’t want to say “please wait for an hour to get winget before running our setup script” to customers.
BenjaminAdam 0 Reputation points

2023-07-29T12:20:13.1733333+00:00
I had the same problems with my new W10 image.

To make Winget available for the rollout script right after Windows deployment, I added the following Appx packages as AppxProvisionedPackage in my image.
Microsoft.VCLibs.140.00
Microsoft.UI.Xaml.2.7
Microsoft.DesktopAppInstaller

However, for some reason DesktopAppInstaller is still not automatically installed, but this can be easily installed via a rollout script using the following command:

Add-AppxPackage -Register (Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq 'Microsoft.DesktopAppInstaller').InstallLocation -DisableDevelopmentMode

Alternatively, the Appx packages can of course also be provided as an installer in the file system of the image or a network share and installed directly via a rollout script.

Of course, if there is free Internet access in the deployment environment, the packages can be downloaded via Powershell and then installed. Thus, the packages do not need to be provided in the image or network share beforehand.

$Tempfolder = "AppxDownload" Push-Location -Path (New-Item -Path $env:SystemDrive -Name $Tempfolder -ItemType Directory -Force).FullName $Uri = '...msixbundle' # Set the URL to the related msixbundle file on github. $File = Split-Path $Uri -Leaf Invoke-WebRequest -Uri $Uri -Out-File $File Add-AppxPackage -Path $file Pop-Location (Join-Path -Path $env:SystemDrive -ChildPath $Tempfolder) | Remove-Item -Recurse -Force

For me, all the options works so far without any problem, Winget is directly available after Windows 10 deployment.
DGarkie 0 Reputation points

2024-09-25T16:04:56.9166667+00:00

One issue with this method, if the reason you're you're trying to update store apps is because Winget is too out of date, you will likely have to open the store manually to update "app installer" which is what winget is packaged within.
I for example have several machines stuck on winget 1.2, where the latest version at the moment is 1.8. Winget 1.2 cant scan, or add any sources(get a forbidden error when adding or scanning sources).
Not a major issue but it means i'll have to log into hundreds of machines and open the store to update winget.
Any recently imaged machine will require touching them and updating store apps(23H2v2 is packaged with 1.2) before any winget commands will work for installing things like our softphone app from the windows store which recently went store-only.

Answer 2

S.Sengupta 23,091 MVP

There is no way to skip 2 letter geolocation thing using Winget command. If you use Y [Yes] it will move to the next step.

Answer 3

I have been using winget from within Crowdstike and Intune Remediation. Few tips I have learned.

In an automation environment with install/upgrade always add:
1. --id - use this instead of name, it has a higher chance of success
2. --silent - so you don't disburb users with the update
3. --accept-package-agreements - this bypasses the questions about 2 letter geolocation
4. --accept-source-agreements - this bypasses the questions about 2 letter geolocation
5. --exact - this mitigates situation where there may be 2 products with similar names or IDs
6. --source - not always needed but it sometimes will error if the product is in both msstore and winget.
7. --uninstall-previous - This is not always necessary but sometime the old version is left behind or a product won't upgrade. I found using this with the Install resolves the issues.
In an automation environment with install/upgrade product may need to stay at a certain level for compatibility with a solution or may be managed by another app like Office with a channel. In these situation pin the product so the automation script does not hang or error out
1. winget pin add --id IdofProduct - pins product so automatic updates skip it
2. winget pin remove --id IdofProduct - removes pin
3. winget pin -? - to see all commands
4. winget upgrade --include-pinned - use this with the upgrade to specifically upgrade a pined product.
5. Be cautious on security of the app.
If you install/upgrade pick the correct product. Research the best one. Examples:
1. winget search -q Chrome - this may come up with a large list
  1. The Chrome with the ID Google.Chrome installs with the msi installer
  2. The Chrome with the ID Google.Chrome.EXE installs with the exe installer
  3. From research the exe installer is better for automation but either works fine.
If your EDR shows that a product contains vulnerabilities, but you have the latest or it won't upgrade. Check the installed versions:
1. winget list -q Edge
  1. You may see that two versions are install one with the id related to the source and one that starts with msix\path to file.
  2. The one that starts with msix may be the one out of date. Just use winget uninstall --id IdOfAppx
Sometime the sources get corrupt or there may be malware interference
1. winget source reset --force - resets the sources to the default

Hope these tips help anyone with using winget.

Answer 4

Ro Social 0

actually, an more easy way is to use Windows update!

on your pc go to settings > windows updates

check for updates and install them

Vincent Duvernet 11 Reputation points

2024-05-31T14:57:22.4+00:00

Windows Update don't update MS Store.

Answer 5

Johnathan Myers 0

I'm kind of late to the party here, but thought it's worth mentioning the use of Microsoft Power Automate. It allows you to record your mouse actions and save them to a "flow" that can be run.

Share via

Update Micorosoft Store and Store Apps with command line?

5 answers

Your answer