Microsoft’s Windows has become maddeningly loud about what it thinks you should do — sign in with a Microsoft account, buy Game Pass, use Copilot+, install OneDrive — yet when it comes to the small, gritty features that actually speed work, the OS still feels stingy and distracted. The Register’s column that sparked this conversation lays out ten concrete, practical features Windows lacks — multiple clipboards, visible extra clocks, a fourth modifier key, full shortcut remapping, a movable/resizable taskbar, an audio “firewall,” pinning apps to specific monitors, program groups that launch related apps, fast audio-device switching, and fewer Microsoft-driven distractions — and argues Microsoft is prioritizing attention-grabbing AI and upsells over everyday productivity.
Windows has historically been both the workplace’s backbone and its annoyance: powerful, ubiquitous, and full of legacy cruft. In recent years Microsoft has invested heavily in AI-first experiences, Copilot integrations, and tighter ecosystem hooks, while also experimenting with UI changes that have sometimes removed long-favored conveniences. That strategic tilt — toward ambient AI, subscription nudges, and premium hardware features — has produced new capabilities, but it has also prompted a backlash: users ask for tools that help them work faster, not more in-OS marketing and ephemeral flashy features. The tension between marketing-driven product placement and productivity-first design is now visible across the OS. Recent public comments from Microsoft executives show Windows is leaning further into “agentic” and multimodal interfaces, which only sharpens the complaint that Microsoft is evolving input metaphors rather than polishing the basics. (windowscentral.com, techradar.com)
This article summarizes the Register’s ten requests, examines existing Windows capabilities and third-party workarounds, validates technical claims against official documentation and reputable tech coverage, and offers a pragmatic roadmap for what Microsoft could ship that would actually improve productivity for millions of users.
Why it matters: Copy/paste is the single most-repeated micro-interaction for knowledge workers. Clipboard history (Win+V) helps, but it’s still linear and transient. Dedicated clipboards would let users reserve slots for a code snippet, a citation, and an image simultaneously, cutting switching friction.
Current reality and validation: Windows includes a clipboard history that you can enable with Windows+V and sync across devices, with a 25-item limit and pinning features documented by Microsoft. That feature is helpful, but it’s not the same as multiple persistent clipboards with their own hotkeys. (support.microsoft.com)
Workarounds: Power users use clipboard managers (third-party) or AutoHotkey scripts to simulate multiple clipboards; but there’s no first-party, system-level “named clipboards” API. A Microsoft implementation could expose a small set of named slots (Clipboard A/B/C), provide keyboard defaults (e.g., Ctrl+Win+1 copy to slot 1, Ctrl+Win+Shift+1 paste slot 1), and integrate with clipboard history.
Risks & considerations: Syncing named slots across devices raises privacy questions (should those be cloud-synced by default?), and the UI should avoid cluttering Win+V. Default off plus clear privacy settings would mitigate concerns.
Why it matters: Remote teams and publication workflows (UTC deadlines) require constant, glanceable time references. Clicking the tray steals attention.
Current reality: Windows supports Additional clocks in Settings → Time & language, but those clocks only appear in the tooltip or flyout — not persistently on the taskbar itself. Microsoft’s settings pages confirm the additional-clock mechanism but also its hover-only presentation. (support.microsoft.com)
Feasibility: Low risk. Microsoft already tracks multiple timezones; exposing a second clock label in the system tray (configurable) is a quality-of-life tweak that would be trivial compared with larger UI overhauls.
User impact: Immediate day-zero benefit for journalists, sysadmins, dev teams working across timezones.
Why it matters: Hotkey collisions are real; adding a reserved modifier would let users build large, consistent personal shortcut layers (e.g., MOD+C / MOD+V for second clipboard).
Reality & alternatives: Hardware changes require OEM cooperation; but Microsoft has precedent (the Windows key, later the Copilot key). In software-only terms, PowerToys Keyboard Manager already lets you remap keys and create complex chords and “start app” actions; it demonstrates the OS-level value of this approach and how Microsoft could standardize it. PowerToys documentation shows full shortcut remapping exists already, but a native extra modifier would simplify cross-app consistency and hardware-key mapping. (learn.microsoft.com)
Risks: Adding a new physical key across billions of keyboards is a long effort; but Microsoft could emulate a logical modifier (mapping an unused Android/keyboard scancode) and champion it through PC manufacturers.
Why it matters: Muscle memory differs and migrations (e.g., Emacs users, Vim users, or those switching OSes) are painful when shortcuts are hardwired.
Current options: PowerToys Keyboard Manager supports remapping of keys and shortcuts, includes app-specific mappings, and can trigger apps — but it has limitations (reserved system combos like Ctrl+Alt+Del cannot be remapped). The official docs make clear some keys/shortcuts remain reserved. (learn.microsoft.com)
Recommendation: Windows should surface an official keyboard mapping panel (Settings → Accessibility or Input) that uses PowerToys tech as its backend and explains reserved combos. That would give power users a polished, Microsoft-supported way to tune shortcuts and reduce reliance on third-party utilities.
Caveat: Remapping globally can break automation, accessibility gestures, and games. Any high-level remap UI must provide per-app scoping and easy “safe mode” to revert bad configs.
Why it matters: Different workflows and multi-monitor setups often benefit from non-default taskbar placements. Windows 11’s locked, center-aligned taskbar removed long-standing flexibility and annoyed many users.
Context and evidence: Microsoft has iterated taskbar behaviors in preview builds, and some experimental changes have been rolled back based on tester feedback — showing the team is listening but cautious about default changes. Reports of taskbar adjustments and reverts are well-documented in tech coverage. (techradar.com)
Feasibility: High — earlier Windows offered this; the code paths exist. Reintroduce as an optional user preference, not the default.
Why it matters: Background tabs and apps suddenly playing audio disrupt meetings and focus. Users should be able to prevent unsolicited playback at the OS level.
Current state and workarounds: Browsers (Edge/Chrome/Firefox) offer site-level autoplay controls, but these act at the browser layer and often only mute after the sound occurs. Windows allows per-app audio output selection and a volume mixer, but there’s no system-wide “require audio permission” prompt. Third-party utilities like EarTrumpet help manage per-app output and volume quickly, but they don’t implement a permission dialog flow. Articles and community posts repeatedly call for better per-app audio controls and quicker device switching tools. (howtogeek.com, reddit.com)
Implementation idea: Introduce an “Audio Permission” policy that is off by default but can be enabled by power users or enterprise admins. When enabled, any app attempting audio playback initially prompts: “Allow [App] to play sound?” with allow/deny and remember choices. Include whitelists and a “do no ask” for signed/trusted system apps.
Trade-offs: This introduces friction for media apps and games; making it optional and granular (system defaults) will reduce false positives.
Why it matters: Multimonitor power users waste time dragging windows; saving placement preferences speeds task context switching.
What exists today: Windows remembers last known window positions in many cases; PowerToys FancyZones lets you create complex window layouts and can “move newly created windows to their last known zone.” Community knowledge (and the Microsoft community forum) shows users have long used shortcuts, display utilities, or PowerToys to approximate this. Display managers like DisplayFusion add per-app placement rules. Microsoft’s Dev/Beta builds are gradually reinstating multi-monitor conveniences (e.g., notification center on secondary displays). (superuser.com, windowscentral.com)
Recommended path: Native per-app monitor affinities in Settings → System → Display, plus a simple “Always open on this screen” checkbox on window context menus. For advanced users, integrate FancyZones-like zone recall into the OS (opt-in) so the OS can restore complex workspace configurations.
Why it matters: Knowledge work is modal; setting up a consistent environment should be one click, not ten.
Workarounds: AutoHotkey, AutoIT, and even PowerShell scripts are commonly used to script multi-app launches. PowerToys’s “Run” and third-party tools (or a simple batch file) can achieve this, but there’s no polished built-in solution that pairs apps with tabs and workspace layout.
Implementation approach: Add “Workspace” presets in Start/Taskbar/Settings that allow:
Why it matters: Silent video calls or accidental loudspeaker broadcasts are frequent, painful errors. The existing Settings flow requires too many clicks when you urgently need to switch.
Current reality and validation: Windows 11’s Quick Settings can change audio devices; Windows is testing a “shared audio” feature in Insider builds and Quick Settings improvements appear in Dev/Beta channels. There are also native per-app audio preferences (App volume and device preferences) that let you assign outputs to running apps, though they can be session-dependent and have UX limitations. Community feedback shows users resort to third-party utilities like EarTrumpet, SoundSwitch, or hardware toggles. (windowscentral.com, ricksdailytips.com, answers.microsoft.com)
Practical design: Add a compact audio dropdown to the taskbar that:
Why it matters: Default-on marketing interrupts the work day and reduces trust. Users who paid for Windows shouldn’t be coaxed into signups mid-task.
Evidence and concrete examples: Multiple outlets and user reports document lock-screen recommendations, widget board clickbait, and “suggested” app tiles. The Register and other commentators note the second-chance out-of-box and update-time experiences that push subscriptions, which many users find intrusive. Privacy and telemetry concerns with new features (Windows Recall taking snapshots) have also led to scrutiny; independent testing revealed Recall’s filters can miss sensitive info — a serious risk when recording snapshots automatically. Those privacy and overshare claims have been reported by multiple outlets. (tomsguide.com)
What to ask for: Default to quiet, enable user-visible toggles during OOBE (so people who want the widgets and promos can opt in), and make it easy to block all marketing at system level (Enterprise and Pro could have a “No Commercial Prompts” policy).
Risks: Microsoft monetizes services; striking the right balance requires business decisions as much as engineering. But making promotional features opt-in or off-by-default would maintain revenue pipelines while respecting user attention at scale.
Source: theregister.com 10 Windows features that would actually help productivity
Background / Overview
Windows has historically been both the workplace’s backbone and its annoyance: powerful, ubiquitous, and full of legacy cruft. In recent years Microsoft has invested heavily in AI-first experiences, Copilot integrations, and tighter ecosystem hooks, while also experimenting with UI changes that have sometimes removed long-favored conveniences. That strategic tilt — toward ambient AI, subscription nudges, and premium hardware features — has produced new capabilities, but it has also prompted a backlash: users ask for tools that help them work faster, not more in-OS marketing and ephemeral flashy features. The tension between marketing-driven product placement and productivity-first design is now visible across the OS. Recent public comments from Microsoft executives show Windows is leaning further into “agentic” and multimodal interfaces, which only sharpens the complaint that Microsoft is evolving input metaphors rather than polishing the basics. (windowscentral.com, techradar.com)This article summarizes the Register’s ten requests, examines existing Windows capabilities and third-party workarounds, validates technical claims against official documentation and reputable tech coverage, and offers a pragmatic roadmap for what Microsoft could ship that would actually improve productivity for millions of users.
The ten requests, one by one — analysis, feasibility, and implementation notes
1. Multiple clipboards (two or three permanents)
The ask: Windows should support multiple named clipboards (not just history) — e.g., primary, secondary, tertiary — each with its own copy/paste hotkeys so you can move text, images, or files between apps without shuffling through a long history.Why it matters: Copy/paste is the single most-repeated micro-interaction for knowledge workers. Clipboard history (Win+V) helps, but it’s still linear and transient. Dedicated clipboards would let users reserve slots for a code snippet, a citation, and an image simultaneously, cutting switching friction.
Current reality and validation: Windows includes a clipboard history that you can enable with Windows+V and sync across devices, with a 25-item limit and pinning features documented by Microsoft. That feature is helpful, but it’s not the same as multiple persistent clipboards with their own hotkeys. (support.microsoft.com)
Workarounds: Power users use clipboard managers (third-party) or AutoHotkey scripts to simulate multiple clipboards; but there’s no first-party, system-level “named clipboards” API. A Microsoft implementation could expose a small set of named slots (Clipboard A/B/C), provide keyboard defaults (e.g., Ctrl+Win+1 copy to slot 1, Ctrl+Win+Shift+1 paste slot 1), and integrate with clipboard history.
Risks & considerations: Syncing named slots across devices raises privacy questions (should those be cloud-synced by default?), and the UI should avoid cluttering Win+V. Default off plus clear privacy settings would mitigate concerns.
2. Two or three clocks in the Taskbar (visible without hovering)
The ask: Show extra clocks directly on the taskbar (UTC, local, other timezone) rather than hiding them behind a hover or click.Why it matters: Remote teams and publication workflows (UTC deadlines) require constant, glanceable time references. Clicking the tray steals attention.
Current reality: Windows supports Additional clocks in Settings → Time & language, but those clocks only appear in the tooltip or flyout — not persistently on the taskbar itself. Microsoft’s settings pages confirm the additional-clock mechanism but also its hover-only presentation. (support.microsoft.com)
Feasibility: Low risk. Microsoft already tracks multiple timezones; exposing a second clock label in the system tray (configurable) is a quality-of-life tweak that would be trivial compared with larger UI overhauls.
User impact: Immediate day-zero benefit for journalists, sysadmins, dev teams working across timezones.
3. Add a fourth modifier key and reserve it for user-defined shortcuts
The ask: A dedicated “MOD” key (beyond Ctrl/Alt/Win) for user-assigned shortcuts so power users can create more mnemonic, nonconflicting bindings.Why it matters: Hotkey collisions are real; adding a reserved modifier would let users build large, consistent personal shortcut layers (e.g., MOD+C / MOD+V for second clipboard).
Reality & alternatives: Hardware changes require OEM cooperation; but Microsoft has precedent (the Windows key, later the Copilot key). In software-only terms, PowerToys Keyboard Manager already lets you remap keys and create complex chords and “start app” actions; it demonstrates the OS-level value of this approach and how Microsoft could standardize it. PowerToys documentation shows full shortcut remapping exists already, but a native extra modifier would simplify cross-app consistency and hardware-key mapping. (learn.microsoft.com)
Risks: Adding a new physical key across billions of keyboards is a long effort; but Microsoft could emulate a logical modifier (mapping an unused Android/keyboard scancode) and champion it through PC manufacturers.
4. Allow remapping of all keyboard shortcuts (OS and apps)
The ask: Let users remap every operating-system and common-app shortcut so personal workflows can be enforced globally.Why it matters: Muscle memory differs and migrations (e.g., Emacs users, Vim users, or those switching OSes) are painful when shortcuts are hardwired.
Current options: PowerToys Keyboard Manager supports remapping of keys and shortcuts, includes app-specific mappings, and can trigger apps — but it has limitations (reserved system combos like Ctrl+Alt+Del cannot be remapped). The official docs make clear some keys/shortcuts remain reserved. (learn.microsoft.com)
Recommendation: Windows should surface an official keyboard mapping panel (Settings → Accessibility or Input) that uses PowerToys tech as its backend and explains reserved combos. That would give power users a polished, Microsoft-supported way to tune shortcuts and reduce reliance on third-party utilities.
Caveat: Remapping globally can break automation, accessibility gestures, and games. Any high-level remap UI must provide per-app scoping and easy “safe mode” to revert bad configs.
5. Bring back the movable, resizable taskbar
The ask: Restore the ability to move the taskbar to the top or sides and resize it (as in Windows 10), and make these options simple to toggle.Why it matters: Different workflows and multi-monitor setups often benefit from non-default taskbar placements. Windows 11’s locked, center-aligned taskbar removed long-standing flexibility and annoyed many users.
Context and evidence: Microsoft has iterated taskbar behaviors in preview builds, and some experimental changes have been rolled back based on tester feedback — showing the team is listening but cautious about default changes. Reports of taskbar adjustments and reverts are well-documented in tech coverage. (techradar.com)
Feasibility: High — earlier Windows offered this; the code paths exist. Reintroduce as an optional user preference, not the default.
6. Firewall for audio: permission model for app sound
The ask: Each app should ask for permission to play audio (or at least require explicit user grant) — plus include allow/deny lists and defaults, similar to UAC for admin privileges.Why it matters: Background tabs and apps suddenly playing audio disrupt meetings and focus. Users should be able to prevent unsolicited playback at the OS level.
Current state and workarounds: Browsers (Edge/Chrome/Firefox) offer site-level autoplay controls, but these act at the browser layer and often only mute after the sound occurs. Windows allows per-app audio output selection and a volume mixer, but there’s no system-wide “require audio permission” prompt. Third-party utilities like EarTrumpet help manage per-app output and volume quickly, but they don’t implement a permission dialog flow. Articles and community posts repeatedly call for better per-app audio controls and quicker device switching tools. (howtogeek.com, reddit.com)
Implementation idea: Introduce an “Audio Permission” policy that is off by default but can be enabled by power users or enterprise admins. When enabled, any app attempting audio playback initially prompts: “Allow [App] to play sound?” with allow/deny and remember choices. Include whitelists and a “do no ask” for signed/trusted system apps.
Trade-offs: This introduces friction for media apps and games; making it optional and granular (system defaults) will reduce false positives.
7. Pin apps to specific screens (multi-monitor persistence)
The ask: When an app is launched, it should be possible to force it to a chosen monitor (and optionally assign a layout) so it always opens in the right place.Why it matters: Multimonitor power users waste time dragging windows; saving placement preferences speeds task context switching.
What exists today: Windows remembers last known window positions in many cases; PowerToys FancyZones lets you create complex window layouts and can “move newly created windows to their last known zone.” Community knowledge (and the Microsoft community forum) shows users have long used shortcuts, display utilities, or PowerToys to approximate this. Display managers like DisplayFusion add per-app placement rules. Microsoft’s Dev/Beta builds are gradually reinstating multi-monitor conveniences (e.g., notification center on secondary displays). (superuser.com, windowscentral.com)
Recommended path: Native per-app monitor affinities in Settings → System → Display, plus a simple “Always open on this screen” checkbox on window context menus. For advanced users, integrate FancyZones-like zone recall into the OS (opt-in) so the OS can restore complex workspace configurations.
8. Program groups: launch related apps & tabs with a single shortcut
The ask: Create “program group” shortcuts that open a preconfigured set of apps and browser tabs for a particular 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.
Workarounds: AutoHotkey, AutoIT, and even PowerShell scripts are commonly used to script multi-app launches. PowerToys’s “Run” and third-party tools (or a simple batch file) can achieve this, but there’s no polished built-in solution that pairs apps with tabs and workspace layout.
Implementation approach: Add “Workspace” presets in Start/Taskbar/Settings that allow:
- A list of apps to start
- Browser bookmarks/tabs to open (Edge/Chrome via command-line flags)
- Window layout to apply (using built-in Snap/FancyZones)
- Optional delay and focus rules
9. Make audio device switching easy (taskbar quick switch + per-usecase routing)
The ask: Put a fast audio output/input switch in the taskbar/system tray with one-click device selection and allow per-use-case bindings (e.g., headphones → Zoom, speakers → browser).Why it matters: Silent video calls or accidental loudspeaker broadcasts are frequent, painful errors. The existing Settings flow requires too many clicks when you urgently need to switch.
Current reality and validation: Windows 11’s Quick Settings can change audio devices; Windows is testing a “shared audio” feature in Insider builds and Quick Settings improvements appear in Dev/Beta channels. There are also native per-app audio preferences (App volume and device preferences) that let you assign outputs to running apps, though they can be session-dependent and have UX limitations. Community feedback shows users resort to third-party utilities like EarTrumpet, SoundSwitch, or hardware toggles. (windowscentral.com, ricksdailytips.com, answers.microsoft.com)
Practical design: Add a compact audio dropdown to the taskbar that:
- Lists outputs and inputs with single-click switching
- Shows per-app assignments and a “switch all communication apps to” quick toggle
- Supports persistent “use case” profiles (e.g., Meeting, Gaming, Streaming)
- Integrates with Windows’ per-app device preferences so choices persist
10. Cut the Microsoft-induced distractions (disable ads & upsell noise by default)
The ask: Ship Windows with minimal promotional noise: default-off widgets/news pushes, no surprise second-chance OOBE upsells after updates, and no runtime push-notifications for Game Pass / Microsoft 365.Why it matters: Default-on marketing interrupts the work day and reduces trust. Users who paid for Windows shouldn’t be coaxed into signups mid-task.
Evidence and concrete examples: Multiple outlets and user reports document lock-screen recommendations, widget board clickbait, and “suggested” app tiles. The Register and other commentators note the second-chance out-of-box and update-time experiences that push subscriptions, which many users find intrusive. Privacy and telemetry concerns with new features (Windows Recall taking snapshots) have also led to scrutiny; independent testing revealed Recall’s filters can miss sensitive info — a serious risk when recording snapshots automatically. Those privacy and overshare claims have been reported by multiple outlets. (tomsguide.com)
What to ask for: Default to quiet, enable user-visible toggles during OOBE (so people who want the widgets and promos can opt in), and make it easy to block all marketing at system level (Enterprise and Pro could have a “No Commercial Prompts” policy).
Risks: Microsoft monetizes services; striking the right balance requires business decisions as much as engineering. But making promotional features opt-in or off-by-default would maintain revenue pipelines while respecting user attention at scale.
Cross-checks, feasibility and who already builds parts of this
- Clipboard & clocks: Microsoft docs confirm a clipboard history feature and the Additional clocks setting, but both fall short of the Register’s asks for multiple named clipboards and visible extra clocks. The official clipboard documentation shows how the current system works, including limits and sync behavior, proving the technical groundwork exists for an enhancement. (support.microsoft.com)
- Keyboard remapping: PowerToys’ Keyboard Manager already implements most remapping functionality the Register asks for, and Microsoft’s docs are explicit about reserved system shortcuts that can’t be changed — showing both that remapping is feasible and where the hard limits lie. Integrating PowerToys capabilities into Settings would close the gap. (learn.microsoft.com)
- Taskbar, multi-monitor: Microsoft is iterating on taskbar and multi-monitor UX in Insider builds; recent updates restore some capabilities and add better secondary-display behaviors, confirming the company can and will restore lost conveniences when there’s enough feedback. However, historic reverts illustrate Microsoft’s caution and the need to expose features as optional. (techradar.com)
- Audio device switching & permissions: Windows already provides per-app device preferences but lacks an easy one-click taskbar switch or a permission model for audio. Recent Insider discoveries (shared-audio in Quick Settings) and reporting indicate Microsoft is actively experimenting with richer audio controls; the Register’s complaint is that this work is slow, fragmented, and still inferior to third-party tools. (windowscentral.com, tomshardware.com)
- AI and privacy: Microsoft’s move toward agentic, multimodal AI will continue to change the OS, but features like Recall — which aim to snapshot screens — carry real privacy risks that have been demonstrated in testing; this raises the need for conservative defaults, stronger filtering, and transparent controls. (tomsguide.com, windowscentral.com)
A practical roadmap Windows could ship (short, medium, long term)
- Short-term (shipable in a quarterly feature update)
- Taskbar quick-audio switcher and persistent per-usecase audio profiles.
- Taskbar option to show a second clock (with one extra slot for UTC).
- Add “Workspace” shortcuts in the Start menu to launch program groups.
- Make PowerToys Keyboard Manager capabilities available in Settings as an opt-in UI.
- Medium-term (6–12 months)
- Native “named clipboards” (2–3 slots) with keyboard bindings and optional cloud sync.
- Native per-app monitor affinity settings and restore-on-launch options.
- Opt-in audio permission model (for users and enterprise).
- Long-term (Windows release / major update)
- Full keyboard-layer modifier support and optional Copilot-integration for spoken hotkeys.
- Deeper FancyZones-like layout manager integrated with OS windowing system.
- Clear, audited privacy model for Recall-style features with strict default disablement and local-only processing where possible.
Final verdict: small features, large returns
The Register’s list is not romantic; it’s practical. These ten requests are a plea for friction reduction. They aren’t about exotic AI miracles or hardware-locked features; they’re about making the OS behave. Microsoft has already built parts of many of these ideas — PowerToys shows remapping is possible, Clipboard History shows the plumbing exists, FancyZones proves advanced window management is practical — but the missing step is mainstreaming those capabilities into coherent, discoverable, and privacy-respecting OS features.- The strengths of Microsoft’s current approach are clear: the company iterates rapidly, invests in AI and ecosystem integration, and provides extensible tools (PowerToys) that can be standardized. Recent Insider builds returning multi-monitor conveniences prove the team listens and acts. (learn.microsoft.com, techradar.com)
- The risks are also systemic: prioritizing glossy AI and subscription pushes over small productivity wins risks alienating the core professional users who rely on Windows every day. Features that record or analyze user content must default to privacy-first settings; otherwise, the productivity gains are outweighed by trust loss. Independent reports show that features like Recall can accidentally capture sensitive data, reinforcing the need for conservative defaults and transparent filtering. (tomsguide.com)
Takeaways (quick)
- Multiple simple changes — named clipboards, taskbar clocks, per-app audio controls, and program groups — would produce outsized productivity wins.
- PowerToys shows the path: many “missing” features already exist as add-ons and could be folded into Settings as polished, supported capabilities. (learn.microsoft.com)
- Privacy-first defaults are essential for any feature that records or inspects user content; opt-in and local-only processing should be the default for Recall-like tools. (tomsguide.com)
- Microsoft can and should make these choices: small engineering investments, clear UX design, and conservative privacy defaults would make Windows far more useful at work than more intrusive marketing and half-baked AI features.
Source: theregister.com 10 Windows features that would actually help productivity
