A Retired Microsoft Engineer's Vision: How to Fix Windows Annoyances for Power Users

Dave's Garage

Windows' Current State and the Power User Dilemma [0:00]

The speaker, a retired Microsoft Windows engineer, acknowledges the common sentiment that "Windows sucks" but aims to explain why and offer solutions. He asserts that the Windows kernel is as powerful and robust as the Linux kernel, but the user-facing software prioritizes a broad audience.

• Windows' design strategy: Over the past two decades, Windows has "rounded off the edges" to make the OS accessible to the widest possible audience.
  • This approach is compared to highway exit ramps: long, gentle, and forgiving curves designed for ease of use at slower speeds.
• The Power User's Frustration:
  • Power users, who "live in the OS all day," find these novice-protecting features (hidden tools, guardrails, balloon tips) to be friction.
  • Features designed to protect novices, like hiding "sharp tools" and "narrating every step with a balloon tip," become frustrating for experienced users.
  • These users, often developers or IT professionals, are influential opinion leaders who can either praise Windows as a "universal adapter" or defect to Linux or macOS if they feel "patronized."
  • The past focus on "developers, developers" has shifted to a need to empower "power users, power users" because they shape the narrative and influence others.

    

Proposed Solution: Introducing "Professional Mode" [2:57]

The speaker proposes a "professional mode" (or "clutch pedal") as a system-wide setting to switch the OS's characteristics from "safe and chatty" to "deterministic and terse."

• 1. Reduced Verbosity and Nudging [3:16]
  • No app suggestions.
  • No unsolicited Microsoft product recommendations.
  • No web search results in local search unless explicitly requested.
• 2. Centralized Control [3:27]
  • All system settings should reside in a single, authoritative location.
  • Parity between "Settings" and the "Control Panel" should be achieved to eliminate "scavenger hunting" for options.
• 3. Enhanced Tooling [3:38]
  • Windows Terminal should become the default console.
  • WinGet (Windows Package Manager) should be first-party and complete.
  • Essential Unix-like tools (OpenSSH, tar, curl, grep) should be unambiguously available and on the system path by default.
  • WSL (Windows Subsystem for Linux) should be treated as a "peer, not a pet," indicating a higher level of integration and respect.

Addressing Key User Gripes [4:03]

The video addresses several major pain points that generate significant user complaints.

• 1. Privacy and Telemetry [4:10]
  • Problem: The tension between the legitimate need for telemetry data to improve a complex OS and user concerns about privacy and data collection.
  • Solution: Radical Transparency and Control via a "Privacy Ledger" [5:16]
  • An always-available system log for outbound telemetry.
  • Each packet sent would be recorded with a plain English explanation, schema version, and documentation link.
  • Users could mute specific telemetry categories globally or per app with immediate effect.
  • The ledger would be exportable, diffable across releases, and auditable like firewall rules.
  • A "nuclear airplane mode" for analytics would be available.
  • Settings would be lockable so future updates cannot re-enable muted categories without user consent.
  • Microsoft should be transparent about non-negotiable data streams and accept public feedback.
• 2. Microsoft Account Requirement [6:06]
  • Problem: Users are often forced or heavily nudged into creating a Microsoft account during setup, even if they prefer a local account.
  • Solution: Offer a clear, simple choice during setup.
  • Present "Continue with a Microsoft account" and "Continue with a local account" on the same screen.
  • No "tricks" or requirements to connect to the internet to see options.
  • No "dark patterns" in UI design.
  • If a local account is chosen, the OS should explain the implications once and then stop asking.
  • The principle of not confusing policy with preferences should be reinstated.
• 3. Windows Updates [6:44]
  • Problem: Updates often surprise users, causing unexpected reboots and disruptions, especially for power users and small businesses.
  • Solution: A New Social Contract for Updates in Pro Mode [7:09]
  • Scheduled, deterministic Windows maintenance by default.
  • The OS should never reboot the user out of ongoing work.
  • Feature experience packs should not change UI behavior outside of the scheduled maintenance window.
  • The OS should surface the "dependency graph" of an update in plain language (e.g., "this update modifies the graphics stack and will reset your graphics driver") before commitment.
  • One-click, complete rollback functionality.
  • Updates should be staged with two kernels and two user lands, ready to boot. If a new one fails health checks, the loader automatically pivots to the last known good version. This discipline, learned from data centers, should apply to client OS.
• 4. Ads, Nags, and Suggestions [7:57]
  • Problem: The operating system increasingly feels like a sales channel for Microsoft's other properties, displaying sponsored apps and recommending its own services over user-chosen defaults.
  • Solution: A simple switch in pro mode to disable the entire suggestion pipeline.
  • This is easy to implement technically but hard internally due to product management metrics.
  • Trust is more valuable than click-through metrics, and the current approach is "corrosive."
  • Users "detest the experience of being sold to by your own computer that you already own."

Further Specific Fixes for User Experience [8:54]

• 1. Native Archiver Support & sudo Command [9:01]
  • Recent additions like native support for popular archive formats and a proper sudo command are positive "baby steps."
  • More "obvious tools" should be made first-class, stopping users from "scavenger hunts."
  • If a console is shipped, it should be the one users "actually want to live in."
• 2. Kernel vs. User Mode Drivers [9:32]
  • Problem: Third-party drivers operating in kernel mode can cause system-wide failures due to their high privilege level ("Ring Zero").
  • Solution: Move more rich functionality (e.g., security scanning, anti-cheat, exotic device mediation) to user mode whenever possible.
  • Harden the kernel's contracts where its involvement is unavoidable.
  • This shrinks the "surface area for catastrophic failure," making the system more stable.
• 3. Settings and Control Panel Fragmentation [11:08]
  • Problem: The duplication and inconsistency of settings spread across both the modern "Settings" app and the legacy "Control Panel."
  • Solution: Declare "bankruptcy on duplication."
  • Establish a canonical location for each capability.
  • Implement ruthless redirects from old locations to the new canonical ones, with the list shortening with each new release.
  • Pro mode search should only return canonical locations.
  • Display the actual registry key or group policy behind each setting toggle (or make it available on right-click) to aid scripting and advanced configuration.
• 4. File Associations and Default Apps [11:55]
  • Problem: Windows sometimes changes user-set default applications (e.g., web browser) or file associations without explicit consent.
  • Solution: The OS must respect user choices. If an update must touch a default for a legitimate reason, it should clearly explain why and ask for permission, rather than celebratory animations (e.g., "Yay, Edge!").
• 5. Search Functionality [12:16]
  • Problem: Local search results are often polluted with web searches, ads, and irrelevant "suggestions" instead of prioritizing local files and applications.
  • Solution: Local search should be local by default, fast, and predictable.
  • It should rely on the local indexer, not a web service.
  • Provide an opt-in for federating results to the web.
• 6. Clean Install Experience [12:47]
  • Problem: New Windows installations, especially on OEM machines, come with excessive bloatware, third-party trials, and unsolicited suggestions.
  • Solution: A clean install should only include the OS and essentials.
  • OEMs can include bundles in a single, obvious "manufacturer add-ons" folder, preventing new PC owners from having to uninstall gigabytes of unwanted software.

Windows' Undeniable Strengths [13:18]

Despite the criticisms, the speaker emphasizes that Windows has many exceptional qualities.

• Core Strengths:
  • Mature and high-performance kernel.
  • World-class storage stack.
  • Unmatched driver ecosystem.
  • DirectX makes it the premier platform for gaming.
  • Active Directory and Group Policy provide robust management for corporate fleets.
  • WSL and Windows Terminal have significantly improved the developer experience, allowing developers to "straddle worlds without straddling hardware."
  • Remarkable backward compatibility (e.g., the smooth 32-bit to 64-bit transition).

Conclusion: The Core Issue and a Path Forward [13:52]

Windows doesn't inherently "suck"; its issues stem from trying to be "a friendly town for everybody" and neglecting the specific needs of advanced users.

• The core problem: The "zoning board forgot to include a neighborhood for the weirdos who build their own furniture."
• The request: Power users want a "workshop with sharp chisels and permission to make a mess," not to take over the whole town.
• The solution: Give power users a "switch" (pro mode) and "respect," then "get out of the way."
• Monetization: Implementing a "Pro Windows" with no monetization would likely require an annual or monthly fee to offset the lost revenue from ads and suggestions.
• The ultimate goal: A product that is "not afraid to say, 'We trust you.'" This will make others want the same experience.