winget-cli: 0x801901f4 : Internal server error (500) when I try to execute winget list and winget install (Source is down)
Brief description of your issue
When I try to execute winget list or winget install command I get an 0x801901f4 : Internal error in server (500) error.
Steps to reproduce
Execute winget list, winget install.
[winget list]
Ocorreu um erro inesperado ao executar o comando:
0x801901f4 : Erro interno de servidor (500).
[winget install Mozilla.Firefox]
Ocorreu um erro inesperado ao executar o comando:
0x801901f4 : Erro interno de servidor (500).
Expected behavior
List installed apps (with winget list) or install a new app (with winget install)
Actual behavior
Throw an internal server error
Environment
[winget --info]
Windows Package Manager v1.0.11694
Copyright (c) Microsoft Corporation. Todos os direitos reservados.
Windows: Windows.Desktop v10.0.22000.176
Pacote: Microsoft.DesktopAppInstaller v1.15.11694.0
Registros: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 21
- Comments: 48 (15 by maintainers)
The newstore source is down, which breaks the client entirely unless you add
--source winget
to all of your commands. I made a bug about this a few weeks ago: https://github.com/microsoft/winget-cli/issues/1349.BTW, for anyone at MS troubleshooting, it’s the manifestSearch endpoint throwing 500s:
@adrianghc you can
winget source remove newstore
. It still gets a “tombstone” so it shouldn’t show back up unless you disable/reenable the experimental store and then do awinget source reset --force
from an elevated prompt.I have same issue + I can’t download apps from microsoft store too
With
--source winget
it works perfectly, many thanks.I just turned on my machine and also got this error…
Yeah, no problem.
You can also run
winget source reset
to have the client attempt resolving source related issues and add “default” sources back.Here you go:
Thanks for the data points! It looks like we may have another release coming for the experimental store source in the next day or two. It was not built with the reference implementation, so we’re working through some design decisions and legacy systems.
For a bit more transparency, the engineering team working on the store source is working through some technical limitations on how some of the search criteria works. The current implementation is tightly coupled with the search UI in the Microsoft Store. This is likely to have a very long lead time (many months) to get where we want it to be for command-line scenarios supporting the Windows Package Manager.
@denelon Can you reopen this? It’s the only issue noting that the source is down.
Edit: I just remembered that it’s Labor Day, so the team is probably off. Uh, @Fukubi, can you do it?
Also works for me. Thanks!
Can confirm that it worked. But imho, it’s surprising that this was necessary. ‘winget source list’ doesn’t mention “Type” anywhere. So it’s far from obvious that this flag needs to be added. Especially since the error code didn’t mention it either.
I think you need to add
-t Microsoft.Rest
.winget source add -t Microsoft.Rest -n newstore https://storeedgefd.dsx.mp.microsoft.com/v9.0
worked for me.+1 this started working for me this morning as well. Thanks to whoever brought it back to life! Having to remember --source winget was a drag 😃
Fiddler shows the following
@denelon I don’t have any updates in the MS Store, maybe it’s because I’m using the preview version?
Here’s the version details that you asked
And about the internal server error, I still have it
I’m currently also having the issue. My Microsoft Store version is 22109.1401.3.0 (there aren’t any updates available).
Also:
I am facing same issue, as mentioned above for now --source winget seems to work
I have the same issue as well, frustrating.