SQL Developer 2025 - "--include-unknown" installs another instance
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
Research direction
Start by reproducing the issue with SQL Server 2025 Developer installed, then compare the output of winget update --include-unknown and winget update --all --include-unknown. The report identifies package version detection and repeated installation as the failure, but names no source files or tests, so trace how WinGet identifies installed package versions and find the relevant tests. Done means the installed version is recognized and repeated updates do not create another SQL Server instance.
Written by the indexing model from the issue text.
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
No response
Brief description of your issue
SQL Server 2025 Developer is already installed on the PC.
When doing a "winget update all --include-unknown" switch, it downloads and starts another installation of SQL 2025 Developer, so another instance is created. This happens every time you run the update with the switch.
If you do a "winget update --include-unknown", it shows UNKNOWN for the installed SQL 2025 version.
Steps to reproduce
Install SQL Server 2025 Developer (either downloaded or through Winget)
Run "winget update --include-unknown" and you'll see a number of ODBC and other connection updates. SQL Server 2025 will show "UNKNOWN" for installed version.
Run "winget update --all --include-unknown" and another SQL server instance is installed with all available updates.
Once done, run "winget update --include-unknown" and it shows no updates are available, but SQL server 2005 will show "UNKNOWN" version.
Run "winget update --all --include-unknown" again, and another SQL server instance is installed.
Expected behavior
Not another installation of SQL server and another instance.
Actual behavior
SQL Server Developer 2025 version isn't seen by Winget, so whenever --include-unknown is used, another instance is installed.
Environment
Winget: v1.29.380
Windows: Windows 11 - 10.0.26300 Build 26300
Package: Microsoft.SQLServer.2025.Developer 17.0.1000.7
- Dominant language
- C++
- Stars
- 26.6k
- Forks
- 1.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/winget-cli
-
Issue-Docs Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/winget-cli#6692 ·
Maintainers usually reply within 2 days
-
Issue-Docs Possible-Duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/winget-cli#6493 · 1 comment ·
Maintainers usually reply within 2 days
-
Issue-Feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6427 ·
Maintainers usually reply within 2 days
-
Issue-Docs msstore
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
microsoft/winget-cli#6331 · 1 comment ·
Maintainers usually reply within 2 days
-
Command-Source Issue-Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-cli#6148 ·
Maintainers usually reply within 2 days
All issues in microsoft/winget-cli
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day