Pricing

Kiro Error Code 21: Why Kiro Crashes on Startup and How to Fix It

Q: How do I fix Kiro crashing on startup?

Launch with kiro --disable-gpu to get in, then move to a current build; a clean 1.2.4 install resolved the crash in #11523.

Kiro crashing with error code 21 after an update? What the crash code means, the fixes users report in Kiro's GitHub issues, and when to wait for a patch.

By Engineer Foodie Desk Nov 2, 2026 ✓ Sources checked Nov 2, 2026

8 min read

Error text, versions and fixes checked Nov 2, 2026 in Kiro’s GitHub issues (#11523, #11554, #8010). Log paths, update steps and release dates checked Nov 2, 2026 in Kiro’s troubleshooting docs and IDE changelog. Every source is listed at the bottom. No affiliate links on this page (how we work).

Short answer: code 21 means Kiro’s window renderer failed to launch, and on Kiro’s GitHub it traced back to the 1.1.14 update on Windows. The workaround users and a Kiro contributor reported is launching with kiro --disable-gpu. The fix that closed the issue was getting off 1.1.14: the reporter’s crash went away on a clean install of 1.2.4. As of Nov 2, 2026, the current Kiro IDE release is 1.4.62, so if you’re stuck on an old build, updating is step one.

The exact error: `The window terminated unexpectedly (reason: 'launch-failed', code: '21')`

This is the dialog text from the original report:

The window terminated unexpectedly (reason: 'launch-failed', code: '21')

And these are the matching lines from Kiro’s main.log:

[warning] [WebviewProcessMonitor] app render-process-gone: reason=launch-failed, exitCode=21
[error] CodeWindow: renderer process gone (reason: launch-failed, code: 21)

Source: kirodotdev/Kiro issue #11523, “1.1.14 Update causes launch failure code 21”, opened Sep 22, 2026 and closed Oct 5, 2026 (verified Nov 2, 2026). A second report, #11554 (“Kiro.exe crashing with error code 21 on startup”), logged the same render-process-gone lines and was closed on Sep 24, 2026 as a duplicate of #11523.

In plain English: the main Kiro process started, but the process that draws the editor window died before it finished launching. The reporter on #11523 said Kiro offered a “Reopen / Don’t restore editors” prompt, but crashed again before either button could be clicked.

Which versions and systems were hit

Here’s what the issues actually say, and nothing more:

Version: both reports name Kiro 1.1.14 as the build that started crashing (#11523, #11554).
OS: both are Windows 11. #11523 was Windows 11 Enterprise 25H2 on a laptop with Intel Arc 140V graphics. The issue carries Kiro’s os: windows label.
macOS and Linux: no code 21 reports in these threads. That doesn’t prove they’re immune. It means nobody filed one that got linked here.
Fix version: not published. Kiro’s changelog doesn’t mention code 21. The closing comment on #11523 says only that a clean 1.2.4 install resolved it. Kiro’s changelog dates 1.2.4 to Sep 30, 2026.

So is it a Windows bug? Every report in the thread is Windows, and a Kiro contributor’s first read was a GPU hardware-acceleration regression with Intel Arc graphics. The closing comment leaves the root cause at “moving off 1.1.14”.

Reported fixes, in the order I’d try them

Each fix below comes from the issue thread named next to it. No account hacks or ToS workarounds here, just launch flags and updates.

1. Launch with GPU acceleration off (reported in #11523)

Close Kiro completely, then start it from a terminal:

kiro --disable-gpu

The reporter on #11523 found this got Kiro open. A Kiro contributor replied on Sep 24, 2026 that it looked like a GPU hardware-acceleration regression with Intel Arc, and that “launching with kiro --disable-gpu is the workaround” (#11523). Treat it as a way back in long enough to update, not a forever setting.

2. Make sure Kiro is really closed first (reported in #11523)

A Kiro maintainer asked the reporter to fully close Kiro and check Task Manager for leftover Kiro processes before relaunching with a flag. A flag does nothing if an old process is still running and grabs the launch.

The same maintainer also suggested testing kiro --disable-skia-graphite. Be careful with that one: the closing comment says the “Skia Graphite theory was ruled out” (#11523).

3. Get off 1.1.14 with a clean install of a current build (reported in #11523)

This is the one that closed the issue. The closing comment, Oct 5, 2026: the crash “did not reproduce on a current build… Moving off 1.1.14 (ending on a clean 1.2.4 install) resolved the launch crash.”

One trap from that same thread: on Oct 2, 2026 the reporter’s updater had rolled them back to 0.9.2, and the maintainer pointed them to the latest stable build at kiro.dev/downloads. So check the version you actually landed on. Kiro’s troubleshooting docs list “Kiro: Check for Updates” in the command palette. They also note that on Windows, a user-scope install set to run as Administrator has updates disabled. The fix there is to untick “Run this program as an administrator”.

4. If it crashes on the second launch, change the launch parameter (reported in #11554)

The #11554 reporter saw a pattern: a launch with a given parameter worked once, then crashed on the next launch with the same one. Their workaround was running Kiro.exe with a different parameter each time, even a made-up one. That’s a user’s stopgap, not something Kiro endorsed, and the thread was closed as a duplicate the next day. It’s useful mainly as a sign you need step 3.

An older renderer crash (#8010, Kiro 0.11.133, “webviewRendererProcessGone”) tried "disable-hardware-acceleration": true in argv.json. It didn’t fix that case, and Kiro closed it on Sep 24, 2026 as an old version, pointing to kiro.dev/downloads. Different code, same lesson: old builds get closed, not patched.

What each fix keeps

Action	Keeps login	Keeps settings
`--disable-gpu` launch	Yes, flag only	Yes, flag only
Kill leftover processes	Yes, restart only	Yes, restart only
Update in place	Not published	Not published
Clean reinstall	Not published	Not published
New launch parameter	Yes, flag only	Yes, flag only

The “Yes” rows are launch-time flags or process restarts that don’t delete files. Kiro doesn’t publish what a reinstall or update keeps. The #11554 log shows Kiro’s state lives in AppData\Roaming\Kiro\User\globalStorage\state.vscdb and .kiro-shared\sharedStorage\state.vscdb, so if you do a clean reinstall, back up those folders first.

Grab your logs before you file anything

Kiro’s troubleshooting docs list the log folders:

Windows: %APPDATA%\Kiro\logs\
macOS: ~/Library/Application Support/Kiro/logs/
Linux: ~/.config/Kiro/logs/

If Kiro opens at all, “Developer: Export Logs…” bundles them. On #11523 the maintainer also asked for %APPDATA%\Kiro\Crashpad. Kiro’s docs warn that logs can contain sensitive information, so read them before attaching them to a public GitHub issue.

An update shipped, and the editor stopped opening on Windows. The reporter couldn’t even reach the “don’t restore editors” button. Then the updater rolled them back to 0.9.2, which is a version so old it’s practically vintage. The thread ends with “did not reproduce on a current build”, and Kiro’s changelog never names the bug. If you pay for a tool, a one-line “fixed: launch crash code 21” in the release notes isn’t asking much.

Source: Kiro #11523 and Kiro IDE changelog, verified Nov 2, 2026

Is it your credits? No.

Code 21 is the editor window crashing at launch. None of the linked reports tie it to credits or plans, and Kiro’s out-of-credits behaviour is a different message, not a crash. If Kiro opens and then refuses prompts, that’s a different problem: see Kiro “Error sending prompt” and Kiro credits. And if you’re weighing whether to keep paying, Is Kiro free? and Kiro vs Cursor cover the money side.

Here’s what I’d do

Close Kiro, kill any leftover Kiro processes, and launch with kiro --disable-gpu.
Once it opens, run “Kiro: Check for Updates” and confirm the version number. If the updater won’t move you, download the current build from kiro.dev/downloads.
Still crashing on a current build? Back up your state.vscdb folders, do a clean install, then export logs and open a new issue that links #11523.
Don’t run Kiro’s user install as Administrator. It disables updates, which is the one thing that fixed this.

If your whole team is stuck, it’s worth a look at the AI coding tools compared page while you wait.

FAQ

What is Kiro error code 21? It’s Kiro’s editor renderer failing to launch, tied to the 1.1.14 update on Windows in Kiro GitHub issue #11523 (verified Nov 2, 2026).

What does “The window terminated unexpectedly (reason: ‘launch-failed’, code: ‘21’)” mean in Kiro? It means the process that draws Kiro’s window died during launch; main.log shows render-process-gone with exitCode=21.

How do I fix Kiro crashing on startup? Launch with kiro —disable-gpu to get in, then move to a current build; a clean 1.2.4 install resolved the crash in #11523.

Is Kiro error code 21 a Windows bug? Every linked report is Windows 11 and the issue carries Kiro’s os: windows label, but Kiro has not published a root cause.

Is Kiro error code 21 caused by running out of credits? None of the linked reports tie it to credits; it’s an editor launch crash, not a billing message.

Which Kiro version fixes error code 21? Not published; the closing comment says a clean 1.2.4 install worked, and the current release as of Nov 2, 2026 is 1.4.62.

Sources

Kiro GitHub issue #11523, “1.1.14 Update causes launch failure code 21” (dialog text, main.log lines, --disable-gpu, --disable-skia-graphite ruled out, 1.2.4 resolution, 0.9.2 rollback): https://github.com/kirodotdev/Kiro/issues/11523 (verified 2026-11-02)
Kiro GitHub issue #11554, “Kiro.exe crashing with error code 21 on startup” (second-launch crash, changing parameters, state.vscdb paths, duplicate of #11523): https://github.com/kirodotdev/Kiro/issues/11554 (verified 2026-11-02)
Kiro GitHub issue #8010 (webviewRendererProcessGone, argv.json hardware acceleration setting): https://github.com/kirodotdev/Kiro/issues/8010 (verified 2026-11-02)
Kiro IDE troubleshooting docs (log paths, Export Logs, Check for Updates, Administrator install note): https://kiro.dev/docs/ide/troubleshooting/ (verified 2026-11-02)
Kiro IDE changelog (1.2.4 on Sep 30, 2026; 1.4.62 on Oct 28, 2026): https://kiro.dev/changelog/ide/ (verified 2026-11-02)
Kiro downloads: https://kiro.dev/downloads (linked from #11523, verified 2026-11-02)