microsoft / microsoft/winget-cli
"Failed in attempting to update the source: winget" when using ssh
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
Using ssh connection return "Failed in attempting to update the source: winget" when installing or upgrading.
For this instance i use arch-linux > windows
Administrator in π B-Station in ~
PS > winget install usbipd-win
Failed in attempting to update the source: winget
Found usbipd-win [dorssel.usbipd-win] Version 4.1.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/dorssel/usbipd-win/releases/download/v4.1.0/usbipd-win_4.1.0.msi
ββββββββββββββββββββββββββββββ 4.57 MB / 4.57 MB
Successfully verified installer hash
Starting package install...
Successfully installed
PS > winget upgrade --include-unknown --silent --all
Failed in attempting to update the source: winget
Name Id Version Available Source
--------------------------------------------------------
OBS Studio OBSProject.OBSStudio 30.0.2 30.1.0 winget
1 upgrades available.
Installing dependencies:
This package requires the following dependencies:
- Packages
Microsoft.VCRedist.2015+.x64
(1/1) Found OBS Studio [OBSProject.OBSStudio] Version 30.1.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://github.com/obsproject/obs-studio/releases/download/30.1.0/OBS-Studio-30.1-Full-Installer-x64.exe
ββββββββββββββββββββββββββββββ 126 MB / 126 MB
Successfully verified installer hash
Starting package install...
Successfully installed
Running winget source reset --force does not resolve the ssh client issue.
The apps are seaminly installed propperly and the message do not occure on the device it sefl and i have not yet noticed any ill effects yet when updateing and installing while seeing this message.
Steps to reproduce
- Use ssh to access a system
- Run
winget install apporwinget upgrade
Expected behavior
Not to see the message
Actual behavior
See the message
Environment
S > winget --info
Windows Package Manager v1.7.10661
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22631.3296
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 Enabled
LocalArchiveMalwareScanOverride Disabled
Contributor 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.
Research direction
Reproduce the issue by connecting over SSH and running winget install app or winget upgrade; begin with the winget source update path and the diagnostic logs under %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir. Confirm the fix by ensuring these commands no longer print the source-update failure over SSH while installation and upgrade still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100