Nushell profile in Windows Terminal has "nu.exe" command line in Windows on ARM
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 79
Description
Bug report form
- I have done a basic search of the issue tracker to find any existing issues that are similar.
- I have checked that my version is at least the latest stable release available via my installation method.
Describe the bug
I attempted to install and run nushell on Windows on ARM64. Installation completed, but the app doesn't run from Windows Terminal. I get a dialog box with this message:
nu.exe - System Error
The code execution cannot proceed because VCRUNTIME140.dll was not found. Reinstalling the program may fix this problem.
I tried installing the Microsoft Visual C++ v14 Redistributable (ARM64) and ran Nushell again, and it brought up the same error message.
Note that this is only when I run Nushell from Windows Terminal directly, from its new tab menu. If I run nu.exe from PowerShell or Command Prompt, even when running those from Windows Terminal, it runs fine. It also runs directly from File Explorer.
I don't know why a Rust application would need the C++ runtime, but that's probably the closest equivalent to libc on Windows. This might be a bug in Windows Terminal, or in the profile created in Windows Terminal by the Nushell installation.
This problem doesn't occur on Windows on x64.
How to reproduce
winget install nushell --scope machine
Then open Windows Terminal, and attempt to open a new tab with the Nushell profile from the dropdown.
Expected behavior
Just run with no dialog box looking for VCRUNTIME140.dll.
Configuration
| key | value |
|---|---|
| version | 0.110.0 |
| major | 0 |
| minor | 110 |
| patch | 0 |
| branch | |
| commit_hash | d40e191d8efad32a174d85b2a45f7ba4796cff84 |
| build_os | windows-aarch64 |
| build_target | aarch64-pc-windows-msvc |
| rust_version | rustc 1.90.0 (1159e78c4 2025-09-14) |
| rust_channel | 1.90.0-aarch64-pc-windows-msvc |
| cargo_version | cargo 1.90.0 (840b83a10 2025-07-30) |
| build_time | 2026-01-18 02:11:09 +00:00 |
| build_rust_channel | release |
| allocator | standard |
| features | default, mcp, network, plugin, rustls-tls, sqlite, trash-support |
| installed_plugins | |
| experimental_options | example=false, reorder-cell-paths=true, pipefail=false, enforce-runtime-annotations=false |
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
Reproduce the issue with winget install nushell --scope machine, then launch the Nushell entry from the Windows Terminal new-tab profile and compare it with nu.exe from PowerShell or Command Prompt. Determine whether the Windows Terminal profile or Nushell's installation is responsible; done means the ARM64 profile opens without the VCRUNTIME140.dll dialog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100