4 ms·
Maybe I was experiencing something else on top of that because I was getting exception codes at first. But then once I started getting "source errors" I decided
by sixothree 3y ago
Maybe I was experiencing something else on top of that because I was getting exception codes at first. But then once I started getting "source errors" I decided to check the store and such and that's when things started working more normally.
What's surprising though is that it listed the msstore source as operating normally when I did winget source update. Regardless, kind of crappy this doesn't work out of the box and I have wave dead things not mentioned in any instructions to get this dumb thing working.
- kotaKat 3y agoMy experience (and path that lead to this) was realizing that a fresh install of Windows 11 gave me PowerShell and not Terminal in the Win+X menu. WinGet would... launch, but provide no output. And of course, it was my first time trying to use WinGet in general... A few reboots later suddenly Win+X had Terminal and WinGet started working, and on a subsequent reinstall in a VM I spotted that, yeah, apparently all the extra WinGet, Terminal, etc stuff all has to be pushed from the MS Store instead of Windows Update. Total pain in the ass.