My first introduction to winget as a sysadmin was horrible. Why Microsoft, in their infinite wisdom, decided to make winget reliant on the user environment still baffles me. Why on earth would they require admin rights for some commands if you need to have logged into the system once?! Even the user created for LAPS does not have that requirement!
Even getting it to run through a service on system level requires you to find the nondescript directory of the executable (which may or may not he the same on other devices!) To get basic functionality going. But even with the --ignore-unknown flag (because it is not able to determine the version of packages when run through a service) winget will refuse to update without a user environment.
Winget is a step in the right direction… but man it is SO SLOW. If PowerBI Desktop has an update, it is actually taking me 20+ minutes to update a handful of apps.
Winget update --all
But yes, this updates any packages distributed by Ms store and winget repos. As an IT professional, I love winget.
My first introduction to winget as a sysadmin was horrible. Why Microsoft, in their infinite wisdom, decided to make winget reliant on the user environment still baffles me. Why on earth would they require admin rights for some commands if you need to have logged into the system once?! Even the user created for LAPS does not have that requirement!
Even getting it to run through a service on system level requires you to find the nondescript directory of the executable (which may or may not he the same on other devices!) To get basic functionality going. But even with the --ignore-unknown flag (because it is not able to determine the version of packages when run through a service) winget will refuse to update without a user environment.
Winget is a step in the right direction… but man it is SO SLOW. If PowerBI Desktop has an update, it is actually taking me 20+ minutes to update a handful of apps.
I just like that it can be scripted and run during off hours.