`atlas upgrade` stops with "Upgrade failed" and then "Please run the terminal as Administrator and try again" because the install method is choco and choco only allows install and upgrade in elevated terminals. Reopen the terminal as Administrator and re-run `atlas upgrade`. Atlas prints the elevation hint instead of the raw stderr only in this specific case, when it catches UpgradeFailedError and the stderr contains "not running from an elevated command shell".
Why does atlas upgrade ask me to run as Administrator
`atlas upgrade` asks you to run as Administrator because your Atlas install method is choco, and choco only allows install and upgrade in elevated terminals. Atlas catches UpgradeFailedError, sees stderr containing "not running from an elevated command shell", and prints that 1 elevation hint instead of the raw stderr.
The hint is a translation, not a guess. Atlas inspects the failure it caught: the install method has to be choco, and choco's own stderr has to contain the phrase "not running from an elevated command shell". When both conditions hold, Atlas replaces the raw stderr with the plain-English line "Please run the terminal as Administrator and try again", because that is the only action that resolves it. The elevation requirement comes from choco itself, so no Atlas flag or configuration key can bypass it. An unelevated terminal simply cannot complete a choco upgrade.
How to fix the Atlas upgrade elevation error
Fix the Atlas upgrade elevation error in 2 steps: reopen the terminal as Administrator, then re-run `atlas upgrade`. Because choco only allows install and upgrade in elevated terminals, elevating the shell is the entire fix, and no Atlas configuration change is involved.
Reopen the terminal itself with Administrator rights rather than trying to elevate mid-session, because the privilege level of a running shell cannot be changed after the fact. Once the elevated terminal is open, re-run `atlas upgrade` in it. If the same "Please run the terminal as Administrator and try again" line appears in a shell you believe is elevated, the shell is not actually elevated, or `atlas upgrade` is being dispatched to a different, unelevated process. Verify the terminal's privilege level before assuming the message is wrong.
What atlas upgrade prints for other install methods
For install methods other than choco, `atlas upgrade` prints the raw stderr from UpgradeFailedError, so read it directly. The elevation hint is choco-specific, which means a non-choco Atlas install that fails to upgrade in 2026 will never show "Please run the terminal as Administrator and try again".
The distinction is practical. If you are on a non-choco install and the upgrade fails, do not go hunting for a privileges problem. Atlas hands you the installer's own stderr unmodified, and that text is the actual diagnosis. Read it before changing anything. The special-cased elevation hint exists only because choco's stderr on this condition is opaque enough that Atlas rewrites it into an actionable instruction. Every other failure keeps its original wording precisely so you can act on the real cause instead of a generic message.
What Atlas update check failed means
Atlas prints "Atlas update check failed: <reason>" when the version check itself fails, which is a different problem from the elevation error. In 2026 that message means `atlas upgrade` never reached the install step, so choco's requirement to run from an elevated terminal is not what stopped it.
Read the reason in the angle brackets, because it is where the information lives. A failed version check is not an UpgradeFailedError, so Atlas does not print the elevation hint and it does not print installer stderr. Running the terminal as Administrator will not help here, and re-running the upgrade in an elevated shell will just reproduce the same check failure. Treat "Atlas update check failed" as its own class of problem, and diagnose it from the reason Atlas gives you rather than from the upgrade path's remedies.
Why atlas upgrade skips when already on the target version
`atlas upgrade` skips with a warning when Atlas is already on the target version, because there are 0 changes left to apply. Use --force to reinstall if you want the upgrade to run anyway, for example after a partial install left the binary in a state you no longer trust.
The skip is not an error, and it is easy to misread as one when you were expecting an upgrade to happen. Atlas warns instead of failing, because reinstalling an identical version is normally wasted work. Reach for --force when you have a reason to believe the existing installation is damaged rather than merely current. Note the ordering caveat: on a choco install, a forced reinstall still goes through choco, so it still requires an elevated terminal, and running it unelevated will produce the same "Please run the terminal as Administrator and try again" line.
How to verify the atlas upgrade fix worked
Verify the Atlas upgrade fix by re-running `atlas upgrade` inside the Administrator terminal. Success means both messages are gone, "Upgrade failed" and "Please run the terminal as Administrator and try again", and choco completes the upgrade in 2026 without raising UpgradeFailedError.
If Atlas instead warns that it is already on the target version, the upgrade already succeeded on a previous run and there is nothing left to do; use --force only if you specifically want a reinstall. If "Please run the terminal as Administrator and try again" appears again, the terminal is not actually elevated. And if a different message appears entirely, such as "Atlas update check failed", you have moved past the elevation problem into a separate failure, so read the new reason and diagnose that instead.
How to fix it
- 01Reopen the terminal as Administrator and re-run `atlas upgrade`.
- 02For other install methods, the raw stderr from UpgradeFailedError is printed; read it directly.
- 03If the version check itself fails, the message is: Atlas update check failed: <reason>.
- 04If Atlas is already on the target version, upgrade is skipped with a warning; use --force to reinstall.
Frequently asked questions
- How do I fix "Please run the terminal as Administrator and try again" in Atlas?
- Reopen the terminal as Administrator and re-run `atlas upgrade`. The message appears because the install method is choco, and choco only allows install and upgrade in elevated terminals.
- Why does atlas upgrade need an elevated shell?
- Choco only allows install and upgrade in elevated command shells. Atlas catches UpgradeFailedError, detects stderr containing "not running from an elevated command shell", and prints the elevation hint instead.
- Can I bypass the Atlas upgrade elevation requirement?
- No. The elevation requirement comes from choco itself, not from Atlas, so no Atlas flag or config key avoids it. Reopen the terminal as Administrator and re-run `atlas upgrade`.
- What does atlas upgrade print if I did not install with choco?
- For other install methods, the raw stderr from UpgradeFailedError is printed, so read it directly. The Administrator hint is choco-specific and will not appear on a non-choco install.
- What does "Atlas update check failed" mean?
- "Atlas update check failed: <reason>" means the version check itself failed, before any upgrade was attempted. Read the reason; elevating the terminal will not help with this one.
- Why did atlas upgrade skip the upgrade?
- If Atlas is already on the target version, the upgrade is skipped with a warning. Use --force to reinstall if you want the install to run anyway.
- Does atlas upgrade --force still need Administrator on choco?
- Yes. A forced reinstall on a choco install still runs through choco, which only allows install and upgrade in elevated terminals, so run it from an Administrator terminal.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas with OpenAI o1-pro (2026): The $600 Per Mtok Question
OpenAI o1-pro is the most expensive model in the OpenAI registry at $150 per Mtok input and $600 per Mtok output. Here is what it does in Atlas and why o3 usually wins.
Atlas for Godot: Terminal-Native AI Coding for GDScript and the Node Tree in 2026
Atlas is a terminal-native AI coding agent for Godot in 2026, working across GDScript, the node tree, and signals, where scene structure is half the program.
Atlas with NVIDIA Nemotron Nano 9B v2 in 2026
Nemotron Nano 9B v2 in Atlas, 2026: a dense 9B reasoning model at $0.06/$0.23 per Mtok on Vercel AI Gateway and Amazon Bedrock, free on the NVIDIA NIM tier.
Atlas vs Fine.dev: Terminal AI Coding Agents in 2026
Compare Atlas and Fine.dev for terminal AI coding in 2026. Atlas offers a free core TUI with permission-gated tools, while Fine.dev provides asynchronous cloud agents and prebuilt libraries.
Atlas with Claude Haiku 4.5: The Cheap Slot in 2026
Claude Haiku 4.5 runs Atlas's small_model slot at $1 / $5 per Mtok with a 200K window. Titles, commit summaries, and cheap subagent fan-out, priced honestly for 2026.
Atlas with Vercel AI Gateway in 2026: 310 Models Behind One AI_GATEWAY_API_KEY
Atlas with Vercel AI Gateway in 2026: roughly 310 models, Grok 4.20 Reasoning at a 2,000,000 token context for $1.25/$2.50 per Mtok, one AI_GATEWAY_API_KEY.
Atlas with Baseten in 2026: 262,000 Tokens In, 262,000 Tokens Out
Atlas with Baseten in 2026: Kimi K2.7 Code at 262,000 tokens in and 262,000 out, GPT OSS 120B at $0.10/$0.50 per Mtok, and the tradeoffs of dedicated hosting.
Atlas with Kimi K2.7 Code HighSpeed: The 2x Throughput Tier in 2026
Kimi K2.7 Code HighSpeed runs Atlas at $1.90 per Mtok input and $8.00 per Mtok output, exactly 2x K2.7 Code, on the same 256K tokens (262,144) context window.