"Everything" is a filename search engine for Windows

Original Article ↗ Hacker News Discussion ↗

Windows users praise the third-party tool “Everything” as a fast, minimalist, filename search engine that dramatically outperforms built‑in Windows Search, often becoming a must‑have utility and even a lightweight file manager. Many comments frame its speed and simplicity—achieved by reading NTFS structures like the MFT directly—as an indictment of how slow, bloated, and ad-driven official search has become, especially in recent versions of Windows. Participants also explore why comparable tools are rarer on macOS and Linux, touch on security and permissions trade‑offs, and highlight integrations with launchers, PowerToys, and network search setups.

Overall sentiment on “Everything”

  • Widely praised as a must‑have Windows tool; many have used it for a decade+.
  • Seen as “peak software”: simple UI, live index, and effectively instant results.
  • Often doubles as a minimalist file manager and a core part of people’s workflow.
  • Some say it’s the best program they’ve ever used and makes Windows bearable.

Critique of Windows Search and Windows UX

  • Windows search is described as slow, inaccurate, and worse than older versions (e.g., Windows 7 / XP).
  • Start-menu search is criticized for irrelevant “Best match” results, web/Bing clutter, and ads.
  • File Explorer struggles with sorting and large folders; indexing is seen as disk‑hammering bloat.
  • Some argue search quality reflects broader Microsoft priorities: telemetry, ads, and “app‑first” design over core usability.

How “Everything” Works and Technical Notes

  • Uses NTFS metadata (MFT and USN journal) for instant, live filename indexing without relying on Windows Search.
  • Maintains its own index file; can be run in portable mode but then loses background indexing service.
  • Very fast but can consume multiple GB of RAM and have performance impact on systems with huge datasets.

Security, ACLs, and Why It’s Not Built‑In

  • One argument: it bypasses NTFS ACLs by reading the raw MFT, conflicting with Windows’ security model.
  • Others counter this is solvable by storing permissions in the index or filtering results via a service.
  • Debate over whether Microsoft avoids this mainly due to complexity, support burden, or business incentives.

Cross‑Platform and Filesystem Considerations

  • NTFS journaling is seen as key to Everything’s live, low‑overhead model.
  • On macOS and Linux, equivalents rely on APIs like FSEvents/inotify or their own indexes and can’t fully match its speed.
  • APFS tradeoffs: modern features (copy‑on‑write, snapshots) vs. potentially large index sizes for Everything‑style search; unclear how much is a design choice vs. technical limit.

Integrations, Alternatives, and Complements

  • Integrations: PowerToys Run, Flow Launcher, Directory Opus, custom toolbar, and HTTP server mode for LAN‑wide search.
  • Alternatives / complements mentioned: WizTree, UltraSearch, FSearch, Agent Ransack/FileLocator, Find Any File, Alfred, Spotlight.
  • Alpha 1.5 of Everything is reported as very stable and adds more powerful features; used successfully in small‑business SMB environments.

Deployment Constraints and Corporate Environments

  • Some can’t install it at work due to whitelisting or endpoint protection; portable mode sometimes bypasses this.
  • Seen as a major productivity boost where allowed; lack of it in locked‑down environments is a recurring frustration.

Broader Reflections

  • Thread frequently uses Everything as a contrast case for how small focused tools can outperform large vendors.
  • Some blame “enshittification” and ad‑driven design; others emphasize technical debt, backward compatibility, and brain drain at big companies.