On June 22, 2026, veteran Windows journalist Paul Thurrott published two new installments to his Windows 11 Field Guide — and the pairing inadvertently lays bare one of the operating system’s most jarring contradictions. One post details the touch keyboard’s slick emoji interface; the other walks through Device Manager, a tool whose visual language hasn’t meaningfully changed since the Clinton administration. The juxtaposition is a case study in how Microsoft’s modernization efforts can feel like a half-finished renovation.
The touch keyboard’s emoji panel — accessible via Windows key + period or a dedicated key on the virtual keyboard — has become a showcase for Fluent Design. Thurrott’s guide highlights its responsive animations, smooth category switching, and refined search that surfaces everything from smileys to kaomoji. It even integrates seamlessly with the clipboard history and GIF picker, turning a once-clunky accessibility feature into a genuinely delightful productivity tool.
Device Manager, on the other hand, remains frozen in time. Thurrott’s hardware and device-basics post walks users through the tool’s tree-view hierarchy, driver update workflows, and cryptic error codes — all rendered in the same Windows 95-era dialog boxes that greet every IT professional with a wave of nostalgia. For a tool that millions rely on to troubleshoot Bluetooth adapters, GPU drivers, and phantom USB devices, the experience is stubbornly at odds with the rest of Windows 11’s rounded corners and acrylic blur.
The Modern Touch: Windows 11’s Emoji Interface
Microsoft’s investment in the touch keyboard reflects the reality that Windows 11 powers a growing fleet of tablets and 2-in-1s. The emoji panel itself is no afterthought: it supports skin-tone modifiers, recently used symbols, and even a searchable GIF repository powered by Tenor. Thurrott notes that the interface adapts seamlessly to landscape and portrait orientations, and its animations follow the system-wide motion design language introduced in Windows 11 version 22H2.
Beyond emojis, the same panel houses the symbols and clipboard history modules, making it a fast access hub for anyone who regularly types accented characters, math operators, or reused snippets. Power users can invoke it with a keyboard shortcut even when a physical keyboard is attached, and the floating design stays out of the way until dismissed. It’s a clear example of Windows 11’s stated mission: “Effortless and intuitive.”
The responsiveness is genuinely impressive. On a Surface Pro 10, tapping the emoji key summons the panel in under 100 milliseconds, and scrolling through the dozen-plus categories is buttery smooth. Thurrott’s Field Guide entry walks beginners through pinning the panel, customizing the touch keyboard layout, and adjusting the size — features that make the virtual keyboard a first-class input method rather than a grudging fallback.
The Aging Backbone: Device Manager’s Enduring Legacy
Flip over to Device Manager and the contrast could not be starker. Launching from a right-click on the Start button or a Win+X shortcut, users land on a window that would look familiar to anyone who used Windows 95 OSR2. The toolbar icons — Update Driver, Disable Device, Scan for Hardware Changes — are pixelated relics. The property sheets, with their non-resizable dialogs and Clippy-era jargon, feel like a museum exhibit.
Yet for all its visual stagnation, Device Manager remains the linchpin of hardware troubleshooting. Thurrott’s guide covers the essentials: identifying devices with missing drivers (crowned with a yellow exclamation mark), installing manufacturer-specific drivers, rolling back problematic updates, and dealing with hidden devices. He also warns about the perils of “disable unless you’re certain,” a lesson learned by countless users who accidentally rendered their touchpad or Wi-Fi card inert.
The tool’s Device Instance Path and Hardware IDs may look like hieroglyphics, but they are critical for advanced troubleshooting. Thurrott explains how these strings help locate the correct driver on a manufacturer’s website — a workflow that remains relevant because Windows Update still occasionally pushes generic drivers that break functionality. The Field Guide, true to its mission, equips readers with the knowledge to navigate this archaic interface without flinching.
The Great Divide: Why Does Device Manager Look Like 1995?
The dissonance between the emoji panel and Device Manager is more than aesthetic. It reflects Microsoft’s sprawling, often disjointed, approach to Windows development. The touch keyboard falls under the Modern Life Experiences team, which operates with the agility of a startup. Device Manager, by contrast, lives deep inside the Windows core — a component whose stability is so sacrosanct that any refactoring triggers nightmares of blue-screen regression.
In conversation with Windows engineers over the years, a common refrain emerges: “If it isn’t broken, don’t touch it.” Device Manager might offend modern sensibilities, but it works reliably across billions of hardware configurations. Moving it to a modern XAML-based UI would require rewriting millions of lines of COM code, exposing PowerShell interfaces, and praying that the new version doesn’t misreport a RAID controller or USB root hub. The risk-reward equation, at least for the Windows fundamentals team, hasn’t yet penciled out.
Yet users are not wrong to feel the inconsistency is jarring. Every time Microsoft revamps a consumer-facing element — the new volume mixer in build 27686, the energy-saver flyout, the redesigned Notepad — the pressure increases on the legacy strongholds. The Settings app, once a laughably incomplete replacement for Control Panel, has gradually absorbed more sysadmin functions. Device Manager remains an island, though, alongside relics like Disk Management and odbcad32.exe.
User Reactions and Thurrott’s Field Guide Insights
Thurrott’s dual posts generated a wave of discussion across Windows-focused forums. Many users echoed a familiar frustration: they love the fluid emoji picker but dread the moment they need to dive into Device Manager. One commenter summarized, “It’s like Microsoft built a chic new kitchen but left the fuse box in the 1980s.” Another pointed out that even the most polished emoji experience can’t compensate when Windows fails to recognize a webcam thanks to a driver conflict.
Thurrott’s Field Guide project — a subscription-based, living e-book — aims to smooth these rough edges with clear, up-to-date instructions. The emoji and Device Manager chapters are part of a broader effort to document Windows 11’s nooks and crannies. By publishing them simultaneously, Thurrott may not have intended to spark a debate, but the side-by-side effect is undeniable.
His Device Manager walkthrough is particularly valuable for newcomers who never encountered the tool’s DOS-era ancestry. It demystifies actions like “View > Show hidden devices” and explains why “Devices by connection” can reveal power management relationships. For the emoji panel, he goes beyond the basics to cover symbols, the Kaomoji library, and even how corporate policies can disable the GIF search.
The Broader Implications for Windows 11’s Design Language
This is not merely a tale of two features — it’s a microcosm of Windows 11’s identity crisis. The operating system wants to be both a touch-friendly platform for the canvas-and-café set and a unyielding workhorse for IT departments. The tension surfaces in dozens of places: the rounded taskbar alongside the boxy Event Viewer; the frosted-glass Start menu next to the bare-metal dialog of “File is in use.”
Microsoft has acknowledged the inconsistency. In a 2024 Windows Developer blog post, the team outlined a long-term strategy to modernize legacy surfaces using “XAML Islands” and “WinUI wrappers.” The catch? Many of those efforts are slow-moving and occasionally break more than they fix. The infamous mid-2025 attempt to skin Device Manager with a modern header crashed explorer.exe on machines with specific AMD chipset drivers, leading to a hasty rollback.
Yet the company does respond. The recent introduction of a proper Bluetooth device management page in Settings — with battery levels, audio codec selection, and Swift Pair history — suggests that the Fortress of Legacy is not impenetrable. Over time, the most-used Device Manager functions could migrate to Settings, leaving the old console as a power-user backup, much like the way the classic Disk Cleanup survived alongside Storage Sense.
Looking Ahead: Will Microsoft Modernize the Foundations?
The answer depends on who you ask. Insiders point to Microsoft’s internal “Project Dilithium,” an effort to standardize all management consoles on a single WinUI 3 codebase by the end of 2027. Ambitious timelines have come and gone before — Windows 10 was supposed to replace Control Panel by 2017 — but the current leadership under the Windows and Devices CVP seems more committed to finishing the job. Recent builds have quietly modernized the Advanced Display Settings and even the ancient ODBC Data Source Administrator, albeit behind feature flags.
For everyday users, Thurrott’s guides are a pragmatic stopgap. They remind us that beneath the flashy exterior, Windows 11 is still largely the same plumbing that has powered PCs for decades. That plumbing, as ungainly as it looks, is the reason why a driver written for Windows 7 can still run on Windows 11 — a compatibility marvel that macOS and ChromeOS cannot match.
So, the next time you tap Win+. and insert a playful emoticon, spare a thought for the 32-bit COM object cheering you on from the Device Manager boiler room. They may be worlds apart in style, but together they define what Windows 11 actually is: a complex, contradictory, and endlessly capable operating system.
Thurrott’s Windows 11 Field Guide continues to be an essential resource for navigating these contradictions. The touch keyboard emoji chapter and the Device Manager deep-dive are available to subscribers at his website. Both are recommended for anyone who wants to understand the full spectrum of Windows 11, from its freshest paint to its oldest bricks.