SQL Developer 2025 - "--include-unknown" installs another instance

Open
#6,602 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
43/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
backend, cli

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

Issue-Bug
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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli

All issues in microsoft/winget-cli

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.