Microsoft executives are painting a future where Windows understands your intent, responds to voice commands, and becomes an ambient, multimodal AI assistant. But while the company dreams big, a chorus of users and a detailed analysis from The Register reveal a more mundane reality: Windows still lacks basic productivity features that knowledge workers need every day.

Pavan Davuluri, the head of Windows, recently told Windows Central that the OS will become “more ambient, more pervasive” and “multi-modal,” with voice and screen context becoming primary input methods. It’s a vision that places AI at the heart of computing, capable of semantically understanding user intent and acting on it. Yet for many users, the immediate need isn’t a semantic assistant—it’s a second clock on the taskbar.

The Register’s recent column, which sparked this discussion, listed ten concrete, practical features missing from Windows. From multiple clipboards to a movable taskbar, these requests aren’t flights of fancy; they’re friction points that slow down real work. The discontent highlights a growing rift between Microsoft’s strategic push toward agentic AI and the everyday grind of productivity.

Here’s a detailed look at the features Windows still gets wrong, why they matter, and how existing tools—like Microsoft’s own PowerToys—already prove they’re feasible.

Multiple Clipboards: Beyond Simple History

The ask: Windows should support multiple named clipboards (primary, secondary, tertiary) with dedicated copy/paste shortcuts. This lets users reserve slots for a code snippet, a citation, and an image simultaneously, cutting switching friction.

Why it matters: Copy/paste is the most repeated micro-interaction for knowledge workers. Clipboard history (Win+V) helps, but it’s linear and transient. Dedicated, persistent clipboards would let power users build flowing workflows without shuffling through a history pane.

What exists today: Clipboard history, enabled via Win+V, allows up to 25 entries and supports pinning and cloud sync. But it lacks the ability to assign hotkeys to specific slots. Third-party clipboard managers like Ditto fill the gap, and AutoHotkey scripts simulate similar behavior, but there’s no system-level, first-party implementation.

Microsoft could surface two or three named slots in Settings, provide default key bindings (e.g., Ctrl+Win+1 to copy to slot 1, Ctrl+Win+Shift+1 to paste slot 1), and integrate with clipboard history for a unified experience. Privacy controls would be essential, especially if syncing across devices.

Glanceable Multi-Clock Taskbar

The ask: Show extra clocks directly on the taskbar—UTC, local, another timezone—without requiring a hover or click. Remote teams and publication workflows need constant, glanceable time references.

Why it matters: Clicking the system tray to check a secondary clock steals focus. A persistent second (or third) clock label would be a trivial tweak with outsized benefit for journalists, sysadmins, and dev teams working across timezones.

Current state: Windows supports additional clocks in Settings → Time & Language, but those clocks only appear in a tooltip or flyout—not on the taskbar itself. The mechanism exists; exposing a configurable second clock in the tray area is a low-risk, high-impact enhancement.

A Fourth Modifier Key

The ask: Introduce a dedicated “MOD” key—beyond Ctrl, Alt, Win—reserved exclusively for user-assigned shortcuts. This would let power users create mnemonics without colliding with system or app hotkeys.

Why it matters: Hotkey collisions are real. Emacs, Vim, and custom workflows suffer when the OS hogges key combinations. A reserved modifier could open hundreds of new, consistent shortcut layers.

Feasibility: Hardware changes require OEM cooperation, but Microsoft added the Windows key, then the Copilot key. In software, PowerToys Keyboard Manager can already remap keys and create complex chords, proving the concept. A logical modifier could be emulated via an unused scancode and promoted through PC manufacturers over time.

System-Wide Shortcut Remapping

The ask: Let users remap every OS and common-app shortcut globally. Muscle memory differs; migrations are painful when shortcuts are hardwired.

Current state: PowerToys Keyboard Manager supports remapping keys and shortcuts, including app-specific mappings, but system-reserved combos like Ctrl+Alt+Del can’t be changed. The official docs make these limitations clear.

What’s missing: An official, polished keyboard mapping panel in Settings (Accessibility or Input) that uses PowerToys tech as a backend, explains reserved combos, and offers per-app scoping and a safe mode to revert bad configs. This would make Windows feel modern and customizable out of the box.

Movable, Resizable Taskbar

The ask: Restore the ability to move the taskbar to the top or sides and resize it, as Windows 10 allowed. Multimonitor and unconventional workflows often demand non‑default placements.

Context: Windows 11 locked the taskbar to the bottom-center, removing a long‑standing flexibility. Microsoft has iterated taskbar behaviors in Insider builds and even rolled back some changes based on feedback, showing they’re listening—but the core binding remains.

The code paths exist; reintroducing optional movement and resizing would be low‑engineering and high‑goodwill.

Audio Firewall: Permission Model for App Sound

The ask: Each app should request permission to play audio on first launch, with allow/deny lists and defaults, similar to UAC for admin privileges. Background tabs and apps suddenly blaring sound disrupt meetings and focus.

Current workarounds: Browsers offer site‑level autoplay controls, but they act late. Windows allows per‑app audio output selection via App volume and device preferences, but there’s no system‑wide “require audio permission” prompt. Third‑party tools like EarTrumpet help manage output quickly but don’t add a permission dialog.

Implementation idea: An opt‑in Audio Permission policy that prompts “Allow [App] to play sound?” on first audio playback attempt, with remember choices. Default off, but configurable by power users and enterprise admins. Whitelists for trusted system apps would prevent over‑prompting.

Per‑App Monitor Affinity (Multi‑Monitor Persistence)

The ask: When an app is launched, force it to a specific monitor—optionally with a saved layout—so it always opens in the right place. Multimonitor power users waste time dragging windows across screens.

What exists: Windows remembers last window positions in many cases. PowerToys FancyZones can create complex layouts and move newly created windows to their last known zone. Third‑party display managers like DisplayFusion add per‑app placement rules. Microsoft is gradually reinstating multi‑monitor conveniences in Insider builds, such as notification center on secondary displays.

A native solution: Add per‑app monitor affinities in Settings → System → Display, plus a simple “Always open on this screen” checkbox on window context menus. Integrate FancyZones‑like zone recall so the OS can restore entire workspace configurations.

Program Groups: One‑Click Workspace Launch

The ask: Create “program group” shortcuts that open a preconfigured set of apps, browser tabs, and window layouts for a specific work mode—web dev, writing, video editing.

Why it matters: Knowledge work is modal; setting up a consistent environment should be one click, not ten. Power users already script multi‑app launches via AutoHotkey, AutoIT, or batch files, but there’s no polished built‑in solution.

A simple “Workspace” preset in Start/Taskbar could let users define a list of apps, browser bookmarks/tabs (via command-line flags), a window layout (using Snap/FancyZones), and optional delays. This is low‑complexity but high‑impact for individuals and enterprises alike.

Fast Audio Device Switching + Per‑Usecase Routing

The ask: Put a compact audio output/input switcher in the taskbar tray with one‑click device selection, and allow persistent per‑usecase profiles (e.g., “Meeting,” “Gaming”). The current Settings flow requires too many clicks when you urgently need to switch.

Current reality: Windows 11’s Quick Settings can change audio devices; Insider builds are testing a shared‑audio feature. Per‑app audio preferences exist but are session‑dependent and have UX limitations. Community feedback shows users still rely on third‑party utilities like EarTrumpet, SoundSwitch, or hardware toggles.

A practical design: A dropdown in the system tray listing inputs/outputs with single‑click switching, per‑app assignments, a “switch all communication apps to…” toggle, and persistent profiles that integrate with Windows’ per‑app device preferences. This would end the “pull the plug” workaround many users adopt.

Cut the Microsoft‑Induced Distractions

The ask: Ship Windows with minimal promotional noise by default—no widgets/news pushes, no second‑chance OOBE upsells, and no runtime push‑notifications for Game Pass or Microsoft 365.

Why it matters: Default‑on marketing interrupts the workday and erodes trust. Users who paid for Windows shouldn’t be coaxed into signups mid‑task. Default to quiet, enable clear toggles during OOBE, and offer an Enterprise/Pro “No Commercial Prompts” policy. Business decisions must balance revenue with user respect.

Microsoft’s AI Ambitions: A Distracting Promise?

Meanwhile, Microsoft’s leadership is preparing a seismic shift. Davuluri described a future where “the computer can actually look at your screen and is context aware,” and where voice becomes a first‑class input method. Windows, he said, will be “increasingly agentic and multi‑modal,” using a combination of local and cloud compute.

This vision has merit. Agentic AI could automate repetitive tasks, and natural language interaction could lower barriers for non‑experts. But it also raises red flags. Windows Recall’s controversial screen‑snapping feature, even after re‑launch, was reportedly still capturing passwords and social security numbers, according to independent testing. Features that record or analyze user content demand conservative defaults, stronger filtering, and transparent controls.

For many, the balance feels off. Microsoft is investing heavily in moonshot AI while overlooking the mundane tweaks that would deliver immediate productivity gains. The Register’s list is a reality check: these aren’t exotic requests; they’re about making the OS behave.

A Pragmatic Roadmap: Small Features, Big Returns

Microsoft has already built pieces of many of these ideas. PowerToys demonstrates remapping and advanced window management. Clipboard history proves the plumbing for named slots exists. Insider builds are restoring multi‑monitor and taskbar conveniences. The company can—and should—mainstream these capabilities.

Here’s a feasible timeline:

Short‑term (quarterly update):
- Taskbar quick‑audio switcher and persistent profiles.
- Option to show a second clock in the taskbar.
- “Workspace” shortcuts for program groups.
- PowerToys Keyboard Manager capabilities surfaced in Settings.

Medium‑term (6–12 months):
- Native named clipboards (2–3 slots) with keyboard bindings and optional cloud sync.
- Per‑app monitor affinity settings and restore‑on‑launch options.
- Opt‑in audio permission model for users and enterprise.

Long‑term (next major release):
- Full keyboard‑layer modifier support.
- Deeply integrated FancyZones‑like layout manager.
- Clear, audited privacy model for Recall‑style features with strict default disablement and local‑only processing.

Each item can be gated behind an “advanced” toggle so novices aren’t overwhelmed while power users get meaningful leverage. The choice for Microsoft is stark: continue prioritizing AI features that may take years to mature, or invest in the small, immediate quality‑of‑life improvements that make Windows truly productive today. The Register’s list is a roadmap of low‑hanging fruit. Implement them, and Windows will regain credibility where it matters most—making people faster, less distracted, and more confident at work.