Windows Terminal 1.24.10621.0: What’s New, How to Update, and Why the Icon Change Matters
The newest stable release of Windows Terminal brings a handful of refinements that will hit your daily workflow sooner than you might expect. Readers will discover how to install the update from any Insider channel, what practical changes affect their profiles, and why icons once fetched from the internet now disappear.
New Features Worth a Look
The Command Palette has been given a bilingual search capability, meaning that when you hit Ctrl‑Shift‑P it will locate commands in both English and your chosen display language. For users who juggle multiple languages on the same machine this saves a few keystrokes and reduces frustration.
A dedicated Extensions page appears in Settings, grouping all automatic profile detectors and any fragment extensions you’ve added. The UI now shows each extension’s status side‑by‑side with a toggle button, making it easier to disable or update a problematic one without digging through JSON files.
Relative paths for icons, background images, pixel shaders, and sounds have been extended to work in both local settings files and fragment extensions. That means you can point an icon at “../assets/terminal.svg” from a profile folder, and it will resolve correctly regardless of whether the file lives in the same directory or up one level.
Why the Icon Policy Changed
The devs decided to block icons served over HTTP, HTTPS, and certain network shares. The reasoning is simple: those URLs can silently leak data about who’s opening the terminal, or let a malicious host track you via invisible pixels. The old approach made it trivial for an extension author to embed tracking code under the guise of a cute icon.
In practice this means that if you previously set your profile icon to “https://example.com/terminal.png” and then updated to 1.24, the icon will no longer appear. Users who depend on remote icons now need to copy them locally or host them on a secure share that the Terminal can resolve via relative path.
A real‑world scenario: a small business IT team had an icon library stored on a company web server. After upgrading all PCs to 1.24, every terminal instance displayed a blank icon box. The fix was simply moving the images into each user’s profile folder and updating the JSON paths accordingly.
Updating Windows Terminal 1.24
If you’re already in the Dev or Canary Insider channel, the installer will roll out automatically once the build lands on your machine. For Beta users, the release is staged until stability metrics confirm no critical regressions.
To upgrade manually, download the “WindowsTerminal_1.24_…_x64.exe” from the GitHub releases page and run it as administrator. The installer detects any existing Terminal installation and replaces the core binaries while preserving your settings file in %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe.
Because the release ships with a fresh set of distribution files, you’ll see many copies on disk: one for Dev, one for Beta, one for Canary, etc. The official documentation recommends keeping only the channel you actually use to avoid confusion. If you’re unsure which file is active, open Settings → About; the version number shown there matches the installer you ran.
Troubleshooting Common Issues
Profile Icons Disappear: Check that your icon paths are relative and point to a local file. Remote URLs will be ignored by design.
Command Palette Stuck Items: The 1.24 fix for previewed input actions means items no longer linger after closing the palette. If they do, try resetting the palette cache by deleting %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\PaletteCache.json.
Printing Causes Tab Jitter: A regression introduced in 1.23 caused tabs to move when output was printed while a search query remained active. The 1.24 patch removes the jitter; if you still see it, make sure your Terminal is truly up‑to‑date.
Apps Fail to Launch on Fresh Boots: An error code 0xD000003A that prevented some command line tools from starting has been resolved. If you continue to see this, verify that your PATH environment variable still contains the required directories after the update.
That’s the low‑down on Windows Terminal 1.24. Update now if you want smoother palettes, a cleaner extension UI, and a more privacy‑friendly icon handling strategy.
Release Windows Terminal v1.24.10621.0
We kept Windows Terminal 1.24 out of the stable channel for an extra release cycle just to make sure it was up to par, and now it is. Welcome to 1.24. 1.24 brings a handful of new features and a lo...
