3 ms·

Did a fresh install of windows 11 yesterday and winget doesn’t work. Seriously. I haven’t even installed any software yet.

krger 3y ago
The output turns blue and nothing happens? Update Terminal and then winget will work.
- sixothree 3y ago
  No I was getting "0x8a15000f : Data required by the source is missing" out of the box. Then after that went away it was another error. It might be related to this not being a "local only" account and not a microsoft account. Ultimately, thinking winget can be used like apt to get a new system up and running is misguided on my part.
kotaKat 3y ago
You have to wait for all the back-end updates to finish. Install all the Windows Updates, then open Microsoft Store and go to the Library and wait for it to update even more shit, then you finally will have Terminal and WinGet. Yeah, I found that one out the annoying way too.
- 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 ago
    My 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.

krger 3y ago

The output turns blue and nothing happens? Update Terminal and then winget will work.

sixothree 3y ago
No I was getting "0x8a15000f : Data required by the source is missing" out of the box. Then after that went away it was another error. It might be related to this not being a "local only" account and not a microsoft account. Ultimately, thinking winget can be used like apt to get a new system up and running is misguided on my part.

kotaKat 3y ago

You have to wait for all the back-end updates to finish. Install all the Windows Updates, then open Microsoft Store and go to the Library and wait for it to update even more shit, then you finally will have Terminal and WinGet. Yeah, I found that one out the annoying way too.

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 ago
  My 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.