Never go to bed without learning something new.
-
I might need to hit my head against the desk, but I learned today the dos command: winget it will scan your whole system for software that needs update, and then is you decide to do it, it is waaaaaayyyy faster than many options I have seen. Example: winget list You will get all the installed software and the 2.column from the right is the new version available (if filled)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
my head hurts, too, but in a good way. thanx
"A little time, a little trouble, your better day" Badfinger
I was told that the update through winget only becomes possible after Microsoft checking the official site and being allow to scan the installers, so you theoretically have the defenses of Microsoft in the background and a secure connection through https to the official link. That's why not every software are available, but even then, the "list" argument is a cool way to check if something is in a system or not, it looks pretty damm complete.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I might need to hit my head against the desk, but I learned today the dos command: winget it will scan your whole system for software that needs update, and then is you decide to do it, it is waaaaaayyyy faster than many options I have seen. Example: winget list You will get all the installed software and the 2.column from the right is the new version available (if filled)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
I've known about winget for quite a while but never really bothered trying to use it. So I gave it a go. I know I have Paint.NET 5.0.9 installed, and that 5.0.10 is out (I just haven't taken the time yet to download/install it). So, "winget list" indeed shows Paint.NET, but 5.0.9 (the version I have) in the Version column...no mention of 5.0.10. I'm not sure how I'm supposed to know that there *is* a newer version available (other than the fact I did, in this particular case, have prior knowledge). So I tell it go ahead and update that: winget install dotPDNLLC.paintdotnet This is the result:
Found an existing package already installed. Trying to upgrade the installed package...
Found paint.net [dotPDNLLC.paintdotnet] Version 5.0.10
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/paintdotnet/release/releases/download/v5.0.10/paint.net.5.0.10.install.x64.zip
██████████████████████████████ 62.4 MB / 62.4 MB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Nested installer file does not exist. Ensure the specified relative path of the nested installer matches: C:\Users\[ProfileName]\AppData\Local\Temp\WinGet\dotPDNLLC.paintdotnet.5.0.10\extracted\paint.net.5.0.10.winmsi.x64.msiSure enough, the file it extracted under Temp is an .exe, not an .msi. Paint.NET isn't exactly an obscure thing at this point, nor are they constantly changing their installer - it's been the exact same upgrade process for years. Why isn't this working out-of-the-box? You know what they say about first impressions... I mean, this is definitely a step in the right direction - if only it worked.
-
I've known about winget for quite a while but never really bothered trying to use it. So I gave it a go. I know I have Paint.NET 5.0.9 installed, and that 5.0.10 is out (I just haven't taken the time yet to download/install it). So, "winget list" indeed shows Paint.NET, but 5.0.9 (the version I have) in the Version column...no mention of 5.0.10. I'm not sure how I'm supposed to know that there *is* a newer version available (other than the fact I did, in this particular case, have prior knowledge). So I tell it go ahead and update that: winget install dotPDNLLC.paintdotnet This is the result:
Found an existing package already installed. Trying to upgrade the installed package...
Found paint.net [dotPDNLLC.paintdotnet] Version 5.0.10
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/paintdotnet/release/releases/download/v5.0.10/paint.net.5.0.10.install.x64.zip
██████████████████████████████ 62.4 MB / 62.4 MB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Nested installer file does not exist. Ensure the specified relative path of the nested installer matches: C:\Users\[ProfileName]\AppData\Local\Temp\WinGet\dotPDNLLC.paintdotnet.5.0.10\extracted\paint.net.5.0.10.winmsi.x64.msiSure enough, the file it extracted under Temp is an .exe, not an .msi. Paint.NET isn't exactly an obscure thing at this point, nor are they constantly changing their installer - it's been the exact same upgrade process for years. Why isn't this working out-of-the-box? You know what they say about first impressions... I mean, this is definitely a step in the right direction - if only it worked.
For me the list has these columns:
Quote:
Name - ID - Version - Available - Source
Version is the installed and available the one that will get downloaded and installed Although I don't want to defend them, I am not sure if the problem here is from winget or from the repo in github. If the Meta-Data needed for the automatism says it should be a MSI... I suppose they are not writing that on its own.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I've known about winget for quite a while but never really bothered trying to use it. So I gave it a go. I know I have Paint.NET 5.0.9 installed, and that 5.0.10 is out (I just haven't taken the time yet to download/install it). So, "winget list" indeed shows Paint.NET, but 5.0.9 (the version I have) in the Version column...no mention of 5.0.10. I'm not sure how I'm supposed to know that there *is* a newer version available (other than the fact I did, in this particular case, have prior knowledge). So I tell it go ahead and update that: winget install dotPDNLLC.paintdotnet This is the result:
Found an existing package already installed. Trying to upgrade the installed package...
Found paint.net [dotPDNLLC.paintdotnet] Version 5.0.10
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/paintdotnet/release/releases/download/v5.0.10/paint.net.5.0.10.install.x64.zip
██████████████████████████████ 62.4 MB / 62.4 MB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Nested installer file does not exist. Ensure the specified relative path of the nested installer matches: C:\Users\[ProfileName]\AppData\Local\Temp\WinGet\dotPDNLLC.paintdotnet.5.0.10\extracted\paint.net.5.0.10.winmsi.x64.msiSure enough, the file it extracted under Temp is an .exe, not an .msi. Paint.NET isn't exactly an obscure thing at this point, nor are they constantly changing their installer - it's been the exact same upgrade process for years. Why isn't this working out-of-the-box? You know what they say about first impressions... I mean, this is definitely a step in the right direction - if only it worked.
I use an "older" version of Paint.NET; 5.0.10 (or was it "9"?) represents a change in "policy" from my older version (the details of which I can't remember) which caused me not to bother with the upgrade. Maybe it's related (It's not the "same software").
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
I might need to hit my head against the desk, but I learned today the dos command: winget it will scan your whole system for software that needs update, and then is you decide to do it, it is waaaaaayyyy faster than many options I have seen. Example: winget list You will get all the installed software and the 2.column from the right is the new version available (if filled)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
I tested and it says 7Zip and CMake need to get updated. Really fantastic!
Behzad
-
For me the list has these columns:
Quote:
Name - ID - Version - Available - Source
Version is the installed and available the one that will get downloaded and installed Although I don't want to defend them, I am not sure if the problem here is from winget or from the repo in github. If the Meta-Data needed for the automatism says it should be a MSI... I suppose they are not writing that on its own.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
The 4 columns I have are Name, Id, Version and Source (which values that are either blank, or say 'winget') I'm on Windows 10 22H2.
I am on Win10 Pro 22H2 too... weird.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I am on Win10 Pro 22H2 too... weird.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
I don't recall installing winget separately, so whatever I have, was probably bundled with a monthly cumulative update. winget -? shows I'm on v1.6.2721
Quote:
C:\>winget -? Windows-Paket-Manager v1.6.2721 Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.
No idea why it is different for you than for me. Here I have checked my personal Win10, Work Laptop Win10... everywhere the same
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.