microsoft / microsoft/winget-cli

winget upgrade of Microsoft.SQLServerManagementStudio from v19.3 to 20.0 fails

Open
#4,323 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug Side-by-Side
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Brief description of your issue

Wanted to upgrade SQL Server Management Studio v19.3 to 20.0 through winget, executed:

winget list --upgrade-available --source=winget and realized the upgrade to 20.0 was available, so executed:

winget upgrade Microsoft.SQLServerManagementStudio and it looks like it upgraded the package, but when I open SQL Server Management Studio and check the version, it's still v19.3 instead of 20.0, when I run the upgrade command again I get:

No installed package found matching input criteria.

Steps to reproduce

winget list --upgrade-available --source=winget
winget upgrade Microsoft.SQLServerManagementStudio

Expected behavior

SQL Server Management Studio successfully upgraded to 20.0

Actual behavior

SQL Server Management Studio is still v19.3 after upgrading the package through winget

Environment
Windows Package Manager v1.7.10661
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.4170
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10661.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the two listed winget commands on the stated Windows 10 x64 environment, then inspect the diagnostic logs under %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir. Done means identifying why the package upgrade leaves SQL Server Management Studio at v19.3 and verifying the corrected upgrade behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.