WinGet upgrades Windows ADK to unsupported version and fails with 0x80070656

Aberta
#6,687 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
20/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cpp
Domínio
cli

Direção de pesquisa

Start by reproducing the upgrade of Microsoft.WindowsADK and capturing the installer log path WinGet builds for the failing MSI, since the report points at a 260-character log path (Windows Installer error 1622) alongside the 0x80070656 failure. From there, trace how the upgrade sequence uninstalls the old package before installing the replacement, and check how the offered version is selected versus Microsoft's ADK documentation. Done means the long-log-path case no longer aborts the install and the offered upgrade matches a supported ADK version for the target OS.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Command-Upgrade Issue-Bug Needs-Triage
Relevant area(s)

WinGet CLI

Relevant command(s)

winget upgrade

Brief description of your issue

When upgrading Microsoft.WindowsADK from version 10.1.26100.9457 to 10.1.28000.3481 on Windows 11 Pro 26H2 (x64), WinGet successfully uninstalls the existing ADK but fails to install the replacement.

The installation terminates with error 2147944022 (0x80070656), leaving the system without a working ADK installation.

The failure occurs while installing the "Windows Deployment Image Servicing and Management - Headers and Libraries" MSI package.

The expected MSI log file is not created. Its full path is exactly 260 characters long, suggesting a possible MAX_PATH-related logging issue.

Furthermore, WinGet offers ADK 10.1.28000.3481 even though Microsoft's documentation identifies ADK 10.1.26100.9457 as the appropriate version for Windows 11 26H2.

The issue was reproduced twice on November 14, 2026.

Manual installation of ADK 10.1.26100.9457 succeeds. A WinGet blocking pin has been applied as a temporary workaround.

Steps to reproduce
  1. Use Windows 11 Pro 26H2 (Build 26300.9974, x64).
  2. Install Windows ADK 10.1.26100.9457 using Microsoft's official installer.
  3. Open PowerShell and run winget list --id Microsoft.WindowsADK.
  4. Observe that WinGet offers version 10.1.28000.3481 as an upgrade.
  5. Run winget upgrade --id Microsoft.WindowsADK.
  6. WinGet successfully uninstalls version 10.1.26100.9457.
  7. Installation of version 10.1.28000.3481 fails with exit code 2147944022 (0x80070656).
  8. Run winget list --id Microsoft.WindowsADK again and observe that the ADK package is no longer detected.

The issue occurred twice, with the second failure logged at 21:12:37 on November 14, 2026.

Expected behavior

WinGet should offer an ADK version appropriate for the target system and deployment scenario.

For Windows 11 Pro 26H2 (x64), Microsoft's ADK documentation recommends version 10.1.26100.9457.

When upgrading an existing ADK installation, WinGet should ideally avoid removing the currently working version before ensuring that the replacement can be installed successfully.

If the upgrade fails, the previously installed and functional ADK should remain available or be restored automatically.

Additionally, MSI installation logging should work reliably, including when generated log file paths are very long.

Actual behavior

WinGet offers Windows ADK 10.1.28000.3481 as an upgrade from version 10.1.26100.9457 on Windows 11 Pro 26H2 (x64).

Executing the upgrade causes WinGet to successfully uninstall the existing ADK before starting the installation of the replacement version.

The new installation fails with exit code 2147944022 (0x80070656).

The installer log identifies the failing component as:

package_WindowsDeploymentImageServicingandManagementHeadersandLibraries_x86_en_us

The expected MSI log file for this component is missing. Its intended full path is exactly 260 characters long.

The installation is rolled back, leaving the Windows ADK uninstalled.

This behavior was reproduced twice on November 14, 2026.

The working ADK version 10.1.26100.9457 was subsequently restored using Microsoft's standalone installer. Further unwanted upgrades were prevented using:

winget pin add --id Microsoft.WindowsADK --blocking

Environment
WinGet version: 1.29.380  
Windows Package Manager: v1.29.380  
Windows version: Windows 11 Pro 26H2  
OS build: 10.0.26300.9974  
System architecture: x64  
Desktop App Installer: Microsoft.DesktopAppInstaller v1.29.380.0  
PowerShell version: 5.1  

Affected package: Microsoft.WindowsADK  
Previously installed version: 10.1.26100.9457  
Offered upgrade version: 10.1.28000.3481  

Installation error: 2147944022 (0x80070656)  
Windows Installer error: 1622 (ERROR_INSTALL_LOG_FAILURE)  

Reproduction date: November 14, 2026  
Reproduced: Twice  

Additional observations:
- The previously installed ADK was successfully uninstalled.
- The replacement installation failed during the DISM Headers and Libraries MSI package.
- The intended MSI log path was exactly 260 characters long.
- The MSI log file for the failing component was not created.
- The installation log directory was writable, and SYSTEM and Administrators had full access.
- Manual installation of ADK 10.1.26100.9457 succeeded.
- A blocking pin was added to prevent WinGet from repeating the upgrade.
Linguagem predominante
C++
Estrelas
26.6k
Forks
1.8k
Merge médio
3d 10h
PRs com merge (30d)
41

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/winget-cli

Todas as issues de microsoft/winget-cli

Issues semelhantes

Mais issues de C++

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.