Closed JMacIV closed 6 months ago
I like the idea of warning users of issues with WinGet. It's not really within the scope of Win11Debloat to update it.
The current warning won't work though, I made a suggestion on how to improve it 😄
Suggestion looks good. I have not tested your changes, but it looks good ha.
I figured you would not want to update it within debloat script. If you did decide to, you could always make it an optional opt-in prompt with a warning that it will either download from MS Store, or GitHub. I will prob maintain this code in my fork since I will want it to automatically install the winget upgrade for my purposes :)
I figured you would not want to update it within debloat script. If you did decide to, you could always make it an optional opt-in prompt with a warning that it will either download from MS Store, or GitHub. I will prob maintain this code in my fork since I will want it to automatically install the winget upgrade for my purposes :)
I appreciate that for your purposes it's nice to have it install automatically, but I think the warning is enough. I don't really want the script to be responsible for updating stuff like this.
I suspect the next Windows image provided by MS will come with a more up-to-date WinGet version, so we won't run into this problem anymore.
Added testing for version of winget when setting the "wingetInstalled" var. Updated output to reflect that the version of winget could be outdated.
Related to #51