winget install SDODS.SDODS says no package found — is the ID wrong?

Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.

The docs table lists it, so I ran it:

powershell

winget install SDODS.SDODS

text

No package found matching input criteria.

winget search sdods finds nothing either. Have I got the identifier wrong, or is my winget source stale?

install windows

asked by Tanvi Bhatt

2 answers

The identifier is right and your source is fine. The manifest is not merged yet — it sits in Microsoft's review queue, and only their reviewers can merge it.
There is friction in that queue for us specifically: the installers are unsigned, and that is something their validation flags. So this is not a matter of waiting a fixed number of days.
Notice that the install page does not offer winget while the docs table does. That is deliberate — the page lists a channel only once its registry actually answers, and a tab whose command fails is worse than a missing tab. The docs table is the full set including what is not live yet.
Until it merges, Scoop installs the same desktop app:
powershell
```
scoop bucket add sdods https://sdods.com/scoop
scoop install sdods
```
answered by Daniel OyelaranSDODS team
Or take the installer straight from the download page if you only need it on one machine. You lose the update channel, which is the only thing winget was going to give you here.
answered by Sam Orbison

Have a different question? Ask it.

winget install SDODS.SDODS says no package found — is the ID wrong?

2 answers

Related