The code is adapted from Simon Timms blog post.
If (!$hasPackageManager -or $hasPackageManager.Version -lt "1.10.0.0")
Winget will be integrated with Windows 11 but it is not yet a reality, so to be sure to have the right version installed I use this: $hasPackageManager = Get-AppPackage -name 'Microsoft.DesktopAppInstaller' To avoid loosing to much time, I use Boxstarter and Chocolatey to automate as much as possible all settings and softwares installations.īut since I use Chocolatey only on that occasion, I wanted to replace it by Winget: is is (almost) native to windows, the v1.0 is out and the number of packages available in the community repository is good enough.īoth are package managers and are invoked from the command line, so the switch was not hard but there was some differences and deficiencies to come by. At this point the end does not justify the means for me with 10.Around every 2-3 years I reinstall my computer with a fresh Windows.
They're not standing against CISA, and that's a bold move to take when your latest and greatest is perceived by many to be a big chunk of spyware. If anything I'm more likely to switch from 7 to 8.1 at this point if I upgrade to anything, but, I am somewhat hoping that maybe eventually MS gets tired of being questioned and brow beaten in the press and does change their tune (a bit). Realistically I don't expect 1 or 3 but I'm on the "borrowed time" group with #2 (DX12).
DX12 is shown to be worthwhile enough and is used by a lot of games (though I don't expect this for another year at least).Microsoft reverses their stance on updating and allows more user choice especially regarding the ability to refuse updates by picking and choosing what updates to accept (Pro and above).I think 1 (or more) of several things will happen (or, needs to happen at least) before I go back to 10 especially for gaming: I thought about switching to LTSB N but went back to 7 instead.
0 kommentar(er)
