01 Identity & wake

Authentication and wake should be instant and reliable. Often they are neither.

  • “Ongoing issue”: Windows Hello fingerprint takes 10–20 seconds to authenticate. Microsoft’s own Q&A has a long thread describing slow Hello fingerprint across multiple machines — not a one-off bad sensor, but a pattern that burns time on every unlock. Microsoft Q&A — slow Hello fingerprint
  • “Login with fingerprint no longer working after the latest update.” Feature updates routinely break enrolled biometrics; the fix thread is reinstall drivers, clear containers, re-register — your afternoon, not theirs. Microsoft Q&A — fingerprint after update

02 Shell & input

The shell and pointer layer should stay responsive. Explorer regularly blocks that.

03 Power & portability

Marketing promises range; actual unplugged time and thermals often fall short.

  • “New Windows 11 update killed battery life.” Q&A pattern after upgrades: runtime drops sharply with the same workload — you discover it on a flight, not in a review. Microsoft Q&A — update killed battery life
  • “Severe battery drain after Windows 11 25H2 update.” Users tie regression to specific builds; the official answer path is troubleshooters and Feedback Hub while unplugged time stays gone. Microsoft Q&A — battery drain after 25H2

04 Stability

Hard freezes and blue screens belong in the past — yet people still hit them after upgrades and in daily use.

  • “Persistent BSODs after Windows version upgrade.” Microsoft Q&A threads where the machine loops or crashes after a feature update — not a single bad image, but a recognizable post-upgrade failure mode. Microsoft Q&A — persistent BSODs after upgrade
  • “Memory leak issue in explorer.exe” (build called out in Q&A). Explorer’s RAM climbs and does not release; Task Manager shows the shell eating gigabytes. That is full-system pressure with a first-party process name on the label. Microsoft Q&A — explorer.exe memory leak

05 Apps & platform APIs

Application crashes often trace to fragile platform APIs and resource handling.

  • “Display driver stopped responding and has recovered.” Microsoft documents Timeout Detection and Recovery (TDR): the GPU misses its deadline, Windows resets the stack, and your game or video session is the collateral damage — classic platform-level failure dressed up as a polite balloon. Microsoft Learn — TDR (WDDM) · Microsoft Q&A — display driver recovered
  • “GPU stops outputting video, Win11 keeps running, but reboot required.” Another Q&A-shaped failure: the desktop session pretends everything is fine while the panel stays black until a full restart — indistinguishable from “the app broke.” Microsoft Q&A — GPU black screen, session alive

06 Camera & media

Camera and encoding pipelines should be stable across apps. They are not.

07 Multitasking

Task switching and mixed workloads should remain smooth. They frequently stutter or fail.

  • explorer.exe spikes CPU and RAM while you are simply “using the PC.” Documented resource spikes and leaks in the shell mean the desktop competes with your actual work for cores and memory — not a niche developer-only scenario. Microsoft Q&A — Explorer.exe resource spikes

08 When recovery fails

When the system is failing, recovery tools should always be reachable. Often they are not.

09 VMs & remote

RDS works from Windows App on Mac but not on Windows (per Learn), two apps to juggle, and a client transition — remote work, Redmond edition.

  • Remote Desktop Services in Windows App: supported on Mac, not on Windows — per Microsoft Learn. The official “what connects where” table lists Remote Desktop Services as supported in Windows App on macOS, iOS, Android, and more, but not on Windows. The documented path on Windows is to keep using the separate Remote Desktop app — the same family of client Microsoft is replacing with Windows App for Azure Virtual Desktop, Windows 365, and Dev Box. You are steered off the old app while the new one, on your own OS, does not carry RDS at all. Microsoft Learn — Windows App connectivity matrix · Tech Community — Windows App replaces Store Remote Desktop
  • Mac walkthrough: Devices tab → “+” → Add Workspace. Windows: no equivalent affordance here. Microsoft’s macOS instructions foreground the plus control and workspace URL flow. On my Windows machines Windows App never surfaces that same add-device entry point — only feeds the tenant already pushed down — while Remote PC via Windows App on Windows remains preview and the “generally available” remote-PC client is still the old Remote Desktop Connection (mstsc). Three surfaces, none of them the single obvious home the Mac side gets. Microsoft Learn — same article (matrix + Remote PC / mstsc notes)
  • “RDC: blurry fonts” meets “DPI scaling behavior on remote connections.” Same Q&A staples as ever: fuzzy type until you chase DPI, smart sizing, color depth, and per-monitor scaling — before you even get to the app-shuffle above. Microsoft Q&A — RDP blurry fonts · Microsoft Q&A — DPI scaling on remote connections

10 Updates & bloat

Preinstalled software and the update pipeline still treat your machine and your time as cheap.

Sources & grounding

The gripes on this page are personal. These links are third-party reporting and Microsoft community or product documentation where similar patterns show up — not proof of your exact machine, but evidence that the themes are widely discussed.