Microsoft’s September Patch Tuesday cumulative update for Windows 11 24H2 (KB5065426) finally delivered Emoji 16.0 font assets to millions of PCs, bringing the system’s emoji count to the full Unicode 16.0 recommendation. But many users who expected to see the new icons in their favorite apps or the built-in emoji picker instead found missing-glyph boxes. The rollout highlights the messy reality of emoji support on Windows: getting the new characters into the OS is only half the battle.
Eight fresh emojis—including a sleepy face with under-eye bags, a fingerprint, a leafless tree, and the flag of Sark—are now technically available. Yet even after installing the latest updates, Windows’ own Emoji Panel (Win + .) does not list them on most systems, and popular applications like Outlook, Instagram, and X still show blank rectangles. The result is a fractured experience where the same character renders perfectly in Microsoft Teams or WhatsApp desktop but fails in the very next app over.
How Windows Handles Emoji: A Three‑Part Puzzle
Emoji support on Windows relies on three interdependent layers: the Unicode code points defined by the Unicode Consortium, the system color-emoji font (Segoe UI Emoji), and the rendering pipeline that each application uses—DirectWrite, legacy GDI, or an app-bundled font. A font update alone does not guarantee that every app or system surface will automatically show the new glyphs. The Emoji Panel further relies on a separate internal database that maps emojis to search keywords and skin-tone sequences, requiring its own update cycle.
Emoji 16.0 was finalized alongside Unicode 16.0 on September 10, 2024. It added only eight recommended-for-interchange (RGI) items—seven new standalone code points plus one flag sequence—a deliberately compact set after years of larger expansions. The full RGI emoji inventory now stands at 3,790, including gender and skin-tone variants.
The Eight New Emojis in Emoji 16.0
The most visible additions are:
- Face with Bags Under Eyes
- Fingerprint
- Splatter (paint or ink splash)
- Root Vegetable (a turnip-like tuber)
- Leafless Tree
- Harp
- Shovel
- Flag: Sark (the first new flag emoji since 2022, added via a rare ISO code exception)
Platform vendors like Microsoft then draw their own Fluent-style artwork and package it into font files, a process that always lags behind the Unicode standard adoption. The August optional preview update (KB5064081) for Windows 11 24H2 seeded the new Segoe UI Emoji assets into the OS, and the September Patch Tuesday (KB5065426, pushing some builds to 26100.6584) made those assets available broadly.
The Rollout: Fonts Arrive, Picker Waits
Microsoft’s strategy splits the font payload from the user interface. The August preview and September updates ship the glyph data, but the Emoji Panel—the shortcut-based picker most Windows users rely on—remains frozen at Emoji 15.1. This staging is intentional: the panel’s search index, keyword mappings in dozens of languages, and skin-tone sequence logic must be updated and validated separately to avoid regressions. Previous update cycles have broken emoji search after rushed picker changes, so Microsoft now decouples the two.
The result is a disjointed rollout. On fully patched 24H2 machines, users who rely on the Win+. picker won’t find the new emojis at all unless they paste them from an external source. Meanwhile, apps that use modern DirectWrite or ship their own emoji sets are already showing the fresh designs.
Where the New Emojis Work—and Where They Don’t
Testing by early adopters and emoji-tracking sites reveals a patchwork:
Apps that render Emoji 16.0 correctly:
- Microsoft Word, PowerPoint, OneNote
- Microsoft Teams
- WhatsApp (desktop/web configurations)
- Other apps using DirectWrite and the updated Segoe UI Emoji font
Apps that still show missing-glyph tofu:
- Outlook (classic and new)
- Instagram web
- X (Twitter) web client
- Microsoft Edge address bar
- Many older Win32 apps relying on GDI rendering
The gap is not a single bug. It stems from the three-way interaction of fonts, rendering pipelines, and application design.
Why Some Apps Work and Others Don’t
DirectWrite vs. GDI: Modern apps built on DirectWrite automatically pick up the updated system font. Legacy GDI applications often use their own fallback lists and may never retrieve the new glyphs unless the app is rewritten or reconfigured.
App-bundled emoji sets: Web apps like WhatsApp or certain clients use their own emoji graphics (e.g., Noto Emoji in Chrome). Those updates happen on the vendor’s schedule, independently of Windows. A chat client might already show the Face with Bags Under Eyes because its developers packaged the new art, while Outlook—still tethered to the system font—falls behind until Microsoft updates its internal rendering paths.
Picker metadata lag: The Win+. interface uses an internal emoji-entry dataset that includes search strings. For Emoji 16.0, that dataset must be localized for every supported language. Microsoft typically enables it through a separate feature flag or a future cumulative update, which explains why the glyphs exist in the font but remain invisible in the picker.
Staged enablement: Microsoft often controls feature exposure via server-side flags or ringed rollouts. Even with the font installed, the picker’s ability to display the new emojis may be locked until the user’s machine receives a signal from Microsoft’s update service—a process that can take days or weeks.
What Users and Admins Can Do Right Now
For impatient users, two practical workarounds exist:
- Install the August optional preview KB5064081 if you accept the risks of preview updates. It delivered the font assets earlier. Be aware optional updates can introduce instability.
- Copy/paste emojis from Emojipedia or Unicode charts into apps that already render the system font. This works as a stopgap for sending visible glyphs to colleagues who use compatible clients.
For IT administrators planning a wider rollout:
- Pilot KB5065426 on test machines, paying special attention to line-of-business apps that rely on GDI rendering.
- Expect larger update packages; recent cumulative updates include on-device AI models for Copilot, inflating download size and deployment time.
- If your organization depends on consistent emoji rendering (e.g., documentation or UI screenshots), consider bundling a color-emoji font in deployed apps until the picker and rendering stack stabilize fleet-wide.
Cross-Platform Context: Windows Lags Behind Mobile
Smartphone platforms and Google’s Noto fonts adopted Emoji 16.0 months earlier. Apple and Android OEMs pushed updated keyboards and system fonts through their own update cycles, often weeks after the Unicode release. Windows’ model—tying font and picker changes to monthly servicing—introduces inherent latency. That gap is a practical trade-off: Windows must support a massive application ecosystem and multiple rendering paths, whereas mobile platforms can enforce a single, tightly controlled text stack.
For Windows users, the delay means a friend on an iPhone might send a splatter emoji that renders perfectly, only for the recipient on a fully updated PC to see a blank box in Outlook. The uneven experience damages the seamlessness that emojis promise.
Analysis: A Necessary Step, but a Fragile Experience
Strengths:
- Aligning with Unicode 16.0 keeps Windows on par with global standards, reducing cross-platform confusion over time.
- Microsoft’s Fluent design language produces polished, consistent artwork across Office and Teams, boosting communication clarity.
- Staggering the font and picker updates reduces the risk of a broken search index—a known pain point from past releases.
Weaknesses:
- Fragmentation erodes user trust. Casual users expect emojis to “just work” after an update; seeing blank boxes in Outlook or no new entries in the picker creates confusion.
- Legacy application compatibility remains a persistent gap. Businesses still on GDI-heavy software may never see the new glyphs without application updates.
- Update complexity is growing. September’s payload bundled non-security AI model updates alongside the emoji assets, complicating bandwidth planning for organizations with metered connections.
The Road Ahead: When Will the Emoji Panel Catch Up?
Microsoft has not published a timeline for updating the Emoji Panel. Historically, the company has enabled picker support weeks to a couple of months after the initial font seeding, often via a follow-up cumulative update or a configurable feature flag. Ring-based testing and telemetry feedback will determine the pace. Until a formal release note confirms the change, any third-party estimate remains provisional.
The eventual enablement must pass rigorous testing across search, skin-tone modifiers, and sequence composition in 100+ languages—a non-trivial task that justifies the cautious staging, even if it tests user patience.
Final Takeaway
The September Patch Tuesday for Windows 11 24H2 is a critical milestone: Emoji 16.0 assets are now on disk, and a growing list of modern apps already render the new icons. But the experience is not seamless. The Emoji Panel, the most visible entry point for casual users, still shows last year’s set, and many popular applications display tofu instead of the intended characters.
Understanding the root cause—the separation of font, rendering pipeline, and picker metadata—helps set realistic expectations. For those who want the new emojis today, workarounds exist; for IT teams, phased testing is mandatory. As Microsoft continues to unfold the feature, the gap will close, but for now, Windows users inhabit a half-upgraded emoji world—a vivid reminder that on Windows, even something as simple as a smiley face comes with hidden complexity.