Skip to content

WinGet source update cancels for winget and winget-font with 0x80072EFE / 0x80072EFF while direct CDN access works #6586

Closed

Description

@loenxvi

Relevant area(s)

WinGet CLI

Relevant command(s)

No response

Brief description of your issue

WinGet source refresh is failing system-wide. msstore updates successfully, but both winget and winget-font return Cancelled. The issue persists after source resets, App Installer re-registration, DISM/SFC repairs, an in-place Windows 11 repair install, and testing on a completely fresh local administrator account.

Direct access to the same WinGet CDN endpoints works normally outside WinGet. curl returns HTTP 200 and a direct WinHTTP request to the same URL also returns 200. Verbose WinGet logs instead show connection reset / terminated errors with 0x80072EFF and 0x80072EFE.

Steps to reproduce

Open Command Prompt or Terminal.
Run:
winget source update
Observe:
Updating source: msstore...
Done
Updating source: winget...
Cancelled
Updating source: winget-font...
Cancelled

Run:
winget source reset --force
Then run a normal search command, for example:
winget search powertoys
WinGet fails to open the source.

The same behavior occurs on a completely fresh local administrator account.

Expected behavior

winget source update should successfully refresh the winget and winget-font sources, and normal winget search commands should be able to open and query those sources.

Actual behavior

msstore updates successfully, but winget and winget-font both return Cancelled.

After resetting the sources, WinGet still fails to open them.

Verbose logs show failures while retrieving headers from:

https://cdn.winget.microsoft.com/cache/source2.msix

with errors including:

0x80072EFF
0x80072EFE

indicating that the connection was reset or terminated abnormally.

Direct requests to the same CDN URL succeed outside WinGet, including curl and a direct WinHTTP request returning HTTP 200.

Environment

Windows Package Manager version: v1.29.380
Windows: Windows 11 Pro
Windows version/build: 10.0.26300.9457
Package: Microsoft.DesktopAppInstaller 1.29.380.0

Additional troubleshooting already completed:
- winget source reset --force
- Microsoft.DesktopAppInstaller re-registered
- SFC and DISM repairs
- Windows 11 in-place repair install using ISO
- Tested on a completely fresh local administrator account
- Kaspersky fully disabled during testing
- IPv6 disabled during testing
- WinHTTP proxy shows direct access with no proxy
- Direct curl access to WinGet CDN succeeds
- Direct WinHTTP request to WinGet CDN returns HTTP 200

Installed Microsoft.Winget.Source package:
Version 2026.1009.2124.28
Status: OK

Activity

  1. added
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    Needs-TriageIssue needs to be triaged
    on Oct 10, 2026
  2. loenxvi commented on Oct 11, 2026

    @loenxvi
    Author

    Turns out, I was just using an outdated Kaspersky app. Resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-BugIt either shouldn't be doing this or needs an investigation.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions