Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#66,755 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
62/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell, yaml
Área
build-system, documentation

Línea de trabajo

Empieza en BUILDING.md, en la sección 'Option 2: Automated install with WinGet', que indica a los usuarios de Windows que ejecuten los archivos .configurations desde PowerShell sin decir si se necesitan derechos de administrador. Reproduce los dos modos de fallo descritos en el issue ejecutando winget configure sobre uno de esos archivos YAML, con y sin una shell elevada. Se considera terminado cuando la sección indica que el comando debe ejecutarse en un PowerShell elevado y se enlaza el issue upstream de winget-cli para el error restante.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
JavaScript
Estrellas
122k
Forks
39.9k
Merge medio
4 d 1 h
PR fusionados (30 d)
234

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nodejs/node

Todos los issues de nodejs/node

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.