after winget list Powershell only show a blue line

[Mannshoch]

I today freshly installed Winget (App-Installer) from Microsoft store (Version: 1.17.10271.0)
If I run winget list it spins shortly and then the command line turns blue, without any output.

winget source update instead works without problems

[Deleted user (ghost)]

related see : Winget List command takes 10 seconds to complete. #855

Why still bouncing around not fixed ? : Simply Reluctance.

[Mannshoch]

I assume that Winget do a SSL Certificate Pining. After I requestet an exception for Winget in my Company it works.
Sometimes some shady Antivirus software do same. In such cases you have to deactivate it.

[Léo MELKI (leomelki)]

I made it work by updating this thing from the Microsoft Store if anyone get this error.

[Muhammad Danish (mdanish-kh)]

Mannshoch What version of WinGet are you using? You can use winget -v to find out. This is likely related to CDN migration that broke some older versions of WinGet.

• P.S.A. Original CDN will be retired #3652

Please try to upgrade to the latest client either from Microsoft Store, GitHub Releases or this URL https://aka.ms/getwinget.

[Mannshoch]

I could not say If this still is the same state like in April 2022. As I said since I reported the problem to the IT department, my problem was solved.

[dustojnikhummer]

This is still an issue on clean Windows 11 installs. Is there a way to upgrade it through a powershell script, rather than waiting 20 minutes for Windows Store to decide to update it?

[Muhammad Danish (mdanish-kh)]

dustojnikhummer Have you tried using

Add-AppxPackage -Path "https://aka.ms/getwinget"

If some dependencies are missing, you can try using the "Sandbox script"

[Jonas Hilmersson (jonashilmersson)]

Using the Add-AppxPackage method above was the only thing working for me to get winget to work in a clean Windows 11 23H2. I wasn't allowed to update winget using the installation bundle or by updating the App Installer via MS Store.

[Eric Nordebäck (ericnordebaeck)]

Muhammad Danish (@mdanish-kh) 's reply should be the selected answer. Confirmed that this fixed the issue for us as well.