microsoft / microsoft/winget-cli

SfsClient do not handle Kerberos Authentication for proxy

Open
#5,684 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Command-Download Issue-Bug
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)

winget download

Brief description of your issue

winget download --id 9NBLGGH4QGHW --Source MSStore --accept-package-agreements --accept-source-agreements
results in:
"Fehler beim Abrufen von Microsoft Store Paketdownloadinformationen"

Steps to reproduce

run cmd or powershell
run:
winget.exe download --id 9NBLGGH4QGHW --Source MSStore --accept-package-agreements --accept-source-agreements --proxy="http://proxyxxxxx:" --verbose-logs

winget is asking for the entra id.
answer the question with "No, only this app"
-> error

Expected behavior

downloading the package with dependencies

Actual behavior

download try results in error message:
"Fehler beim Abrufen von Microsoft Store Paketdownloadinformationen"

WinGet-2025-08-25-14-03-54.298.log

Environment
Windows-Paket-Manager v1.11.430
Windows: Windows.Desktop v10.0.22631.5771
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.26.430.0

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

Start with the winget.exe download command and the SfsClient proxy path, using the attached verbose log to trace the failed Microsoft Store request. Reproduce through a Kerberos-authenticated proxy and confirm that package downloads with dependencies complete successfully without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
authentication, cli, networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.