microsoft / microsoft/winget-cli
Error Updating `winget` source - No more endpoints available from mapper
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
I was on an enterprise managed PC running Win10, and then upgraded to Win11. On Win10, winget was working without issue. After the upgrade to Win11, the winget source fails to update
I will say that this is likely not a WinGet specific issue, but I wasn't sure where to put it so thought I would start here.
Additionally, clearer messaging around the failure would be appreciated as opposed to just Cancelled
Steps to reproduce
Unknown;
Expected behavior
Sources to update correctly
Actual behavior
PS C:\Users\REDACTED> winget source update --verbose --logs
Updating all sources...
Updating source: msstore...
Done
Updating source: winget...
█████████████████████▎ 71%
Cancelled
Log:
WinGet-2024-08-05-09-40-24.988.log
2024-08-05 09:40:30.961 [CORE] Starting AddPackage operation #1: file:///C:/Users/REDACTED/AppData/Local/Temp/WinGet/Microsoft.Winget.Source_8wekyb3d8bbwe.msix SkipSmartScreen: 1
2024-08-05 09:40:30.963 [CORE] Begin waiting for operation #1
2024-08-05 09:40:30.963 [CORE] Begin blocking for operation #1
2024-08-05 09:40:31.837 [CORE] Deployment operation #1: error 0x800706D9: While processing the request, the system failed to register the windows.firewall extension due to the following error: There are no more endpoints available from the endpoint mapper.
.
2024-08-05 09:40:31.837 [FAIL] C:\__w\1\s\external\pkg\src\AppInstallerCommonCore\Deployment.cpp(54)\WindowsPackageManager.dll!00007FFE371E81E9: (caller: 00007FFE371E4863) Exception(2) tid(576c) 800706D9 There are no more endpoints available from the endpoint mapper.
Msg:[Operation failed: error 0x800706D9: While processing the request, the system failed to register the windows.firewall extension due to the following error: There are no more endpoints available from the endpoint mapper.
.]
Environment
Windows Package Manager v1.8.1911
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22631.2861
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.23.1911.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
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 by reproducing winget source update --verbose --logs in the reported Windows environment and reading the attached WinGet log, especially the 0x800706D9 deployment error. Trace the source update path from the CLI command and determine where the failure becomes Cancelled. Done means the failure is diagnosed and the user receives actionable messaging instead of only Cancelled.
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
- 32/100