Summary
After updating GitHub Copilot CLI to v1.0.48-0 on Windows ARM64, all prompt execution fails immediately with:
Execution failed: Error: Native addon "runtime" not found for win32-arm64.
Environment
- OS: Windows on ARM64
- Copilot CLI package:
GitHub.Copilot (WinGet)
- Broken CLI runtime version:
1.0.48-0
- Last working version observed:
1.0.47
Repro
copilot update
copilot --version
copilot -p "say hello"
Observed:
GitHub Copilot CLI 1.0.48-0.
Execution failed: Error: Native addon "runtime" not found for win32-arm64.
Findings
The 1.0.48-0 cached package under %USERPROFILE%\.copilot\pkg\universal\1.0.48-0\prebuilds\win32-arm64\ is missing multiple native addons that are present for win32-x64 (and for darwin/linux arm64).
Compared with prebuilds\win32-x64\, the win32-arm64 folder is missing:
runtime.node
pty.node
win32-native.node
Present in win32-arm64: computer.node, conpty.node, conpty_console_list.node, keytar.node, conpty\conpty.dll, conpty\OpenConsole.exe.
For reference, both prebuilds\darwin-arm64\ and prebuilds\linux-arm64\ correctly include runtime.node and pty.node, so this looks like a win32-arm64-specific packaging miss in 1.0.48-0.
Workaround
Removing the 1.0.48-0 cached package from %USERPROFILE%\.copilot\pkg\universal allows Copilot CLI to fall back to 1.0.47, after which prompt execution works again.
Note: simply renaming the broken package inside universal is not sufficient, because Copilot scans package metadata in that folder and will still select the renamed 1.0.48-0 package if its package.json remains.
Auto-update can recreate the broken 1.0.48-0 package on launch. Disable auto-update before reinstalling/pinning:
[Environment]::SetEnvironmentVariable("COPILOT_AUTO_UPDATE", "false", "User")
$env:COPILOT_AUTO_UPDATE = "false"
Remove-Item "$env:USERPROFILE\.copilot\pkg\universal\1.0.48-0" -Recurse -Force
winget uninstall --id GitHub.Copilot --force
winget install --id GitHub.Copilot --version v1.0.46 --source winget --force
Expected
v1.0.48-0 should include the required Windows ARM64 native addons (runtime.node, pty.node, win32-native.node), or the updater should not offer this version to Windows ARM64 users.
Actual
v1.0.48-0 installs/updates successfully but fails on every prompt execution with the missing native addon error.
Summary
After updating GitHub Copilot CLI to
v1.0.48-0on Windows ARM64, all prompt execution fails immediately with:Environment
GitHub.Copilot(WinGet)1.0.48-01.0.47Repro
Observed:
Findings
The
1.0.48-0cached package under%USERPROFILE%\.copilot\pkg\universal\1.0.48-0\prebuilds\win32-arm64\is missing multiple native addons that are present forwin32-x64(and for darwin/linux arm64).Compared with
prebuilds\win32-x64\, thewin32-arm64folder is missing:runtime.nodepty.nodewin32-native.nodePresent in
win32-arm64:computer.node,conpty.node,conpty_console_list.node,keytar.node,conpty\conpty.dll,conpty\OpenConsole.exe.For reference, both
prebuilds\darwin-arm64\andprebuilds\linux-arm64\correctly includeruntime.nodeandpty.node, so this looks like awin32-arm64-specific packaging miss in1.0.48-0.Workaround
Removing the
1.0.48-0cached package from%USERPROFILE%\.copilot\pkg\universalallows Copilot CLI to fall back to1.0.47, after which prompt execution works again.Note: simply renaming the broken package inside
universalis not sufficient, because Copilot scans package metadata in that folder and will still select the renamed1.0.48-0package if itspackage.jsonremains.Auto-update can recreate the broken
1.0.48-0package on launch. Disable auto-update before reinstalling/pinning:Expected
v1.0.48-0should include the required Windows ARM64 native addons (runtime.node,pty.node,win32-native.node), or the updater should not offer this version to Windows ARM64 users.Actual
v1.0.48-0installs/updates successfully but fails on every prompt execution with the missing native addon error.