If this sounds like your week
When Windows Search gets in the way
endpoint images accumulate vendor utilities in HKLM and HKCU App Paths, Start Menu .lnk files, and per-user WindowsApps shims. Windows Search often ranks documents before executable targets and gives no explicit view into App Paths registry entries. during a support call, every Start Menu retry competes with remote-control software, Event Viewer, and antivirus I/O.
Where tooling usually breaks
Why local-first matters
index.db, config.json, and logs stay under %APPDATA%\SearchSentinel instead of a vendor-hosted workspace. Search queries are not uploaded for AI enhancement, analytics, or ad targeting. You buy the app once and keep the search index as a local workstation asset.
Technical proof points
- HKLM/HKCU App Paths - COM IShellLinkW - ShellExecuteW - SQLite FTS5 - Windows app enumeration - COM shortcut resolution