microsoft / microsoft/winget-cli
Add a timeout for broken IPv6 connections to Microsoft's cloud
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Relevant command(s)
No response
Brief description of your issue
As noted here: https://github.com/microsoft/winget-cli/issues/5549#issuecomment-3561582839
When Microsoft has an issue with IPv6 connections to its cloud servers, Winget will simply hang. The spinner goes forever (I've left it overnight, at least 14 hours). The issue is corrected by disabling IPv6, changing IPv6 address, or otherwise working around whatever problem exists on Microsoft's end.
Steps to reproduce
- Get an IPv6 address that Microsoft has trouble connecting to. VPNs seem to be particularly badly affected.
- Try any Winget command that accesses cloud services, e.g.
winget upgrade.
Expected behavior
Winget works as normal, or if a connection cannot be established in some reasonable timeframe (say 30 seconds), it either tries IPv4 or issues an error message.
Actual behavior
The spinner goes round forever.
Environment
Windows Package Manager v1.12.350
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.26200.6899
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.27.350.0
Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
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
Configuration Modules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules
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
ProxyCommandLineOptions Disabled
DefaultProxy 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
Start with the network path used by cloud-accessing WinGet CLI commands, reproducing the hang with winget upgrade over a problematic IPv6 connection. Determine where the connection waits indefinitely and define completion as a bounded timeout that falls back to IPv4 or reports an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100