Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Windows WinGet configuration failures (Failed to create instance: -2147023174)

Fechada Para iniciantes
  • Algo errado?
#66,755 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
62/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
shell, yaml
Domínio
build-system, documentation

Direção de pesquisa

Comece em BUILDING.md, na seção 'Option 2: Automated install with WinGet', que orienta usuários Windows a executar os arquivos .configurations pelo PowerShell sem dizer se são necessários direitos de administrador. Reproduza os dois modos de falha descritos na issue executando winget configure em um desses arquivos YAML, com e sem um shell elevado. Está concluído quando a seção afirma que o comando deve ser executado em um PowerShell elevado e a issue upstream do winget-cli é vinculada ao erro restante.

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

Descrição

doc install windows

Situation

The BUILDING > Windows Prerequisites documentation section 2: Automated install with WinGet describes using the .configurations files to install prerequisites on Microsoft Windows required for building Node.js.

The instructions say to use a PowerShell terminal, and do not specify if elevated (Admin) privileges are necessary.

If the configuration is run without Admin privileges, it fails to install Visual Studio:

VSComponents [vsComponents]
Loading the module for the configuration unit failed because it requires administrator privileges to run.

If the configuration is run with Admin privileges, it fails to determine the current state:

The configuration unit failed while attempting to test the current system state.
Failed to create instance: -2147023174

This error condition is also noted in issue https://github.com/microsoft/winget-cli/issues/6560

Steps to reproduce

On Windows 11 26H2:

From Windows Settings > Apps > Installed Apps delete any of:

  • Git
  • Microsoft Visual Studio Installer
  • Python
  • Python Installer
  • Python Launcher
  • Rust

Delete:

  • C:\Python* if found
  • C:\Program Files\NASM

Restart system

In a PowerShell 7 terminal window, execute:

git clone https://github.com/nodejs/node
cd node
winget configure .\.configurations\configuration.vsBuildTools.dsc.yaml

Logs

Microsoft Windows NT 10.0.26300.0 x64
Windows 11 26H2 (OS Build 26300.9711)
PowerShell 7.6.7
winget v1.29.380

PowerShell non-Admin
WinGetPackage [pythonPackage]
  Unit successfully applied.
WinGetPackage [vsPackage]
  Unit successfully applied.
VSComponents [vsComponents]
  Loading the module for the configuration unit failed because it requires administrator privileges to run.
WinGetPackage [rustPackage]
  Unit successfully applied.
WinGetPackage [gitPackage]
  Unit successfully applied.
WinGetPackage [nasmPackage]
  Unit successfully applied.
Some of the configuration was not applied successfully.
PowerShell Administrator
WinGetPackage [pythonPackage]
  The configuration unit failed while attempting to test the current system state.
Failed to create instance: -2147023174
<See the log file for additional details>
WinGetPackage [vsPackage]
  The configuration unit failed while attempting to test the current system state.
Failed to create instance: -2147023174
<See the log file for additional details>
WinGetPackage [rustPackage]
  The configuration unit failed while attempting to test the current system state.
Failed to create instance: -2147023174
<See the log file for additional details>
WinGetPackage [gitPackage]
  The configuration unit failed while attempting to test the current system state.
Failed to create instance: -2147023174
<See the log file for additional details>
WinGetPackage [nasmPackage]
  The configuration unit failed while attempting to test the current system state.
Failed to create instance: -2147023174
<See the log file for additional details>
VSComponents [vsComponents]
  This configuration unit was not run because a dependency failed or was not run.
Some of the configuration was not applied successfully.

Suggestion

Linguagem predominante
JavaScript
Estrelas
122k
Forks
39.9k
Merge médio
3d 22h
PRs com merge (30d)
233

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 nodejs/node

Todas as issues de nodejs/node

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

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