Replies: 2 comments
-
|
Try using: If you still have issues specifically with WinGet, I recommend posting over at that repository. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks. I tried that originally and then googled the issue. Found a couple of posts showing how to find the apps and using id or name to update
Working Virtually for the Kingdom.,
Lawrence
…
On 05/24/2026 at 03:08, Sam Erde ***@***.***> wrote:
Try using: winget upgrade --id 'Microsoft.Office' --silent --accept-package-agreements --accept-source-agreements.
If you still have issues specifically with WinGet, I recommend posting over at that repository.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have 28 Laptops that need to be update at night. I set up a PowerShell script that runs several different updates. The 365 update is not working. Here is 365 listed:
Name Id Version Source
Microsoft 365 Apps for business - en-us ARP\Machine\X64\O365BusinessRetail - en-us 16.0.19929.20172
I tried by Name an here is the result:
PS C:\Temp> winget upgrade --name "Microsoft 365 Apps for business - en-us"
No available upgrade found.
No newer package versions are available from the configured sources.
PS C:\Temp>
I tried by Id:
PS C:\Temp> winget upgrade --id "ARP\Machine\X64\O365BusinessRetail - en-us"
Failed when searching source: msstore
An unexpected error occurred while executing the command:
0x8a150044 : The rest API endpoint is not found.
PS C:\Temp>
When I open Word and run update there it does download and install updates. Why won't it work through the script?
Beta Was this translation helpful? Give feedback.
All reactions